Skip to content

Commit 4819ec3

Browse files
authored
Merge pull request #7668 from segmentio/DOC-1134
hide Amazon S3 destination
2 parents 5296fc4 + 17c20cd commit 4819ec3

File tree

4 files changed

+15
-5
lines changed
  • src
    • connections
      • destinations/catalog/actions-braze-web
      • sources/catalog/libraries/server/http-api
      • storage/catalog/amazon-s3
    • segment-app/extensions

4 files changed

+15
-5
lines changed

src/connections/destinations/catalog/actions-braze-web/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,8 @@ Braze Web Mode (Actions) provides the following benefits over Braze Classic:
2828
2. Search for "Braze" in the Catalog, select **Braze Web Mode (Actions)**, and choose which of your sources to connect the destination to.
2929
3. Configure the Connection Settings. **API Key** and **SDK Endpoint** are required settings.
3030

31+
After setting up your Braze Web Mode (Action) destination in the Segment app, Segment's Analytics.js library starts asynchronously loading the Braze SDK on your page and sending data. Data appears in the Segment CDN in about 45 minutes.
32+
3133
> info ""
3234
> If you're using a device-mode connection, Braze's SDK assigns a `device_id` and a backend identifier, `braze_id`, to every user. This allows Braze to capture anonymous activity from the device by matching on those identifiers instead of `userId`. This applies to _device-mode connections_.
3335

src/connections/sources/catalog/libraries/server/http-api/index.md

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,15 +3,18 @@ title: HTTP API Source
33
redirect_from: '/connections/sources/catalog/libraries/server/http/'
44
id: iUM16Md8P2
55
---
6-
The Segment HTTP Tracking API lets you record analytics data from any website or application. The requests hit Segment servers, Segment routes your data to any destination you want.
6+
The Segment HTTP Tracking API lets you record analytics data from any website or application. The requests hit Segment servers then Segment routes your data to your destination.
77

8-
Segment has native [sources](/docs/connections/sources/) for most use cases (like JavaScript and iOS) that are all built for high-performance and are open-source. But sometimes you may want to send to the HTTP API directly—that's what this reference is for.
8+
Segment has native [sources](/docs/connections/sources/) for most use cases (like JavaScript and iOS) that are open-source and built for high-performance. But for unsupported use cases, [blocked event forwarding](/docs/protocols/enforce/forward-blocked-events/) or when you're using [Segment-Managed Custom Domain](/docs/connections/sources/custom-domain/), you may want to send data to Segment's HTTP API directly.
99

1010
> info "HTTP API sources in EU workspaces should use the `events.eu1.segmentapis.com` endpoint"
1111
> If you are located in the EU and use the `https://api.segment.io/v1/` endpoint, you might not see any errors, but your events will not appear in the Segment app. For more information about regional support, see the [Source Regional support](/docs/guides/regional-segment/#source-regional-support) documentation.
1212
1313
## Headers
1414

15+
> warning "HTTP API public IP addresses are subject to change"
16+
> The public IP addresses of the HTTP API service are not static and may change without notice. If you are caching the resolved IP address or directly using the IP for submission, you must implement a DNS refresh at least once every 24 hours. Failing to do so may result in submission failures if the underlying IPs change. To ensure long-term reliability, Segment **strongly recommends** using the DNS hostname rather than hardcoding IPs.
17+
1518
### Authentication
1619

1720
Choose between [writeKey authentication](#writeKey-authentication), [basic authentication](#basic-authentication) and [OAuth](#oauth) to authenticate requests.
@@ -284,7 +287,7 @@ Find more details about Group including the **Group payload** in the [Segment Sp
284287

285288
## Alias
286289

287-
`Alias is how you associate one identity with another. This is an advanced method, but it is required to manage user identities successfully in *some* of Segment's destinations.
290+
Alias is how you associate one identity with another. This is an advanced method, but it is required to manage user identities successfully in *some* of Segment's destinations.
288291

289292
In [Mixpanel](/docs/connections/destinations/catalog/mixpanel/#alias) it's used to associate an anonymous user with an identified user once they sign up. For [Kissmetrics](/docs/connections/destinations/catalog/kissmetrics/#alias), if your user switches IDs, you can use 'alias' to rename the 'userId'.
290293

@@ -481,4 +484,8 @@ Segment welcomes feedback on API responses and error messages. [Reach out to sup
481484

482485
1. Double check that you've set up the library correctly.
483486

484-
2. Make sure that you're calling a Segment API method after the library is successfully installed—[Identify](#identify), [Track](#track), and so on.
487+
2. Make sure that you're calling a Segment API method after the library is successfully installed: [Identify](#identify), [Track](#track), and so on.
488+
489+
### Experiencing `5xx` errors
490+
491+
If you're experiencing `5xx` errors, refresh the IP address you use to invoke Segment's HTTP API.

src/connections/storage/catalog/amazon-s3/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ redirect_from:
44
- '/connections/destinations/catalog/amazon-s3/'
55
- '/connections/waser/catalog/amazon-s3/'
66
hide-personas-partial: true
7+
hidden: true
78
---
89

910
> warning "The Amazon S3 destination will enter Limited Access on February 8, 2022"

src/segment-app/extensions/git.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,5 +158,5 @@ This error can occur if there are issues with your Git connection settings or pe
158158
159159
- Your credentials have write access to the Git repository, as Segment requires this to sync changes.
160160
- Your repository is hosted by GitHub, GitLab, or Bitbucket (Segment doesn't support self-hosted repositories).
161-
- Branch protections are disabled on the repository.
161+
- Branch protections are disabled on the repository, or you're using the Segment GitHub app integration and have allowlisted the integration to bypass your branch protection rules.
162162

0 commit comments

Comments
 (0)