diff --git a/src/connections/destinations/catalog/actions-webhook/index.md b/src/connections/destinations/catalog/actions-webhook/index.md index f6fce98374..3975e32d9f 100644 --- a/src/connections/destinations/catalog/actions-webhook/index.md +++ b/src/connections/destinations/catalog/actions-webhook/index.md @@ -39,7 +39,7 @@ The easiest way to test whether a source's events are sending through the Segmen #### Connect a Webhook Actions destination to your workspace 1. [Add a new Webhook (Actions) destination](https://app.segment.com/goto-my-workspace/destinations/catalog/actions-webhook) to your source. Make sure you select the intended source to connect this destination to. -2. Visit the webhook's site, and copy the endpoint to your clipboard. An example site you can use is [https://webhook.site/#!/]([url](https://webhook.site/#!/)), but use whichever webhooks site you prefer. +2. Visit the webhook's site, and copy the endpoint to your clipboard. An example site you can use is [https://webhook.site/#!/](https://webhook.site/#!/), but use whichever webhooks site you prefer. 3. Add a mapping to the Webhook Actions destination, and configure Step 1's conditions to allow for all types of events that you're currently sending through that source. 4. Add the endpoint you copied from Step 2 to the Webhook Actions Mapping's URL in Step 3. 5. Enable the Mapping. diff --git a/src/connections/destinations/catalog/facebook-app-events/index.md b/src/connections/destinations/catalog/facebook-app-events/index.md index b8248a4f02..7a4c936bda 100644 --- a/src/connections/destinations/catalog/facebook-app-events/index.md +++ b/src/connections/destinations/catalog/facebook-app-events/index.md @@ -6,7 +6,7 @@ id: 56fc7e4680412f644ff12fb9 --- > warning "" -> For new implementations, [Facebook no longer recommends using App Events]([url](https://developers.facebook.com/docs/marketing-api/app-event-api/)). Instead, they suggest switching to [Facebook Conversions API (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-facebook-conversions-api/) for all server-side data tracking needs. +> For new implementations, [Facebook no longer recommends using App Events](https://developers.facebook.com/docs/marketing-api/app-event-api/). Instead, they suggest switching to [Facebook Conversions API (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-facebook-conversions-api/) for all server-side data tracking needs. [Facebook App Events](https://developers.facebook.com/docs/app-events){:target="_blank"} collects required information from one of Segment's mobile SDKs ([iOS](/docs/connections/sources/catalog/libraries/mobile/ios/){:target="_blank"}, [Android](/docs/connections/sources/catalog/libraries/mobile/android/){:target="_blank"}, or [Swift](/docs/connections/sources/catalog/libraries/mobile/apple/){:target="_blank"}) and sends it from Segment's servers to Facebook App Events servers. diff --git a/src/connections/functions/source-functions.md b/src/connections/functions/source-functions.md index 47664be5f8..30fb43d3ba 100644 --- a/src/connections/functions/source-functions.md +++ b/src/connections/functions/source-functions.md @@ -304,7 +304,7 @@ The advantage of testing your source function with webhooks is that all incoming Note: Segment has updated the webhook URL to `api.segmentapis.com/functions`. To use webhooks with your function, you must: - [Generate a public API token](https://docs.segmentapis.com/tag/Getting-Started/#section/Get-an-API-token){:target="_blank"}. -- [Create a Public API Token]([url](https://app.segment.com/goto-my-workspace/settings/access-management/tokens)), or follow these steps: +- [Create a Public API Token](https://app.segment.com/goto-my-workspace/settings/access-management/tokens), or follow these steps: In your Segment Workspace, navigate to **Settings** > **Workspace settings** > **Access Management** > **Token**. Click **+ Create Token**. Create a description for the token and assign access. Click **Create** and save the access token before clicking **Done**. - For POST calls, use this Public API token in the Authorization Header, as `Bearer Token : public_api_token` diff --git a/src/connections/spec/ab-testing.md b/src/connections/spec/ab-testing.md index 0ce8c8f50c..91c1c32e71 100644 --- a/src/connections/spec/ab-testing.md +++ b/src/connections/spec/ab-testing.md @@ -35,7 +35,7 @@ Property | Type | Description **This implementation strategy requires a Business Tier plan, as it requires the use of Destination Filters.** -Connect two destinations (A & B) to the same Segment Source. Destination A to receive events related to user events for group-A. Destination B to receive events related to user events for group-B. Configure the destinations as you normally would, and navigate to the Destinations Filter tab on each destination. Referencing the [Destination Filters]([url](https://segment.com/docs/connections/destinations/destination-filters/)) doc and [FQL]([url](https://segment.com/docs/api/public-api/fql/)) doc, create a Destination Filter for each destination to either Allow or Block the events you want sent to each destination. +Connect two destinations (A & B) to the same Segment Source. Destination A to receive events related to user events for group-A. Destination B to receive events related to user events for group-B. Configure the destinations as you normally would, and navigate to the Destinations Filter tab on each destination. Referencing the [Destination Filters](https://segment.com/docs/connections/destinations/destination-filters/) doc and [FQL](https://segment.com/docs/api/public-api/fql/) doc, create a Destination Filter for each destination to either Allow or Block the events you want sent to each destination. For example, Destination A's filter could be built to Allow all events where `context.page.url` has a specific value, and Destination B could be built to Block all events where the `context.page.url` has a specific value. You could also configure them to only Allow/Block events by other fields that can be referenced within the event payloads. Please note that when using Destination Filters, an event must pass all filters in order to be sent to the destination. @@ -51,8 +51,8 @@ To route data to Destination A, modify the integrations object like this `integr You can use either a source function or a destination function, depending on whether you'd like to modify the `integrations` object or simply add logic to route the events that you want sent to the destination. -[Source Function]([url](https://segment.com/docs/connections/functions/source-functions/)) : Create a Source Function in your [workspace]([url](https://app.segment.com/goto-my-workspace/functions/catalog/new)) and select Source for a Source Function. Build out the source function's code to handle the logic for modifying the integrations object as explained in the second implementation strategy above for Destination A and Destination B. Functions require you to build out event handlers for each event type (track/identify/page/screen/group/alias), so make sure all events you want sent to the source are configured appropriately. +[Source Function](https://segment.com/docs/connections/functions/source-functions/) : Create a Source Function in your [workspace](https://app.segment.com/goto-my-workspace/functions/catalog/new) and select Source for a Source Function. Build out the source function's code to handle the logic for modifying the integrations object as explained in the second implementation strategy above for Destination A and Destination B. Functions require you to build out event handlers for each event type (track/identify/page/screen/group/alias), so make sure all events you want sent to the source are configured appropriately. *Note* If you want both Destination A and Destination B to be the same integration, such as two Mixpanel destinations, then modifying the `integrations` wouldn't work, as the integrations object would set them both to true or false. See the destination function strategy below. -[Destination Function]([url](https://segment.com/docs/connections/functions/destination-functions/)) : Create a Destination Function in your [workspace]([url](https://app.segment.com/goto-my-workspace/functions/catalog/new)) and select Destination for a Destination Function. Build out the destination function's code to handle the logic to check whether the event should be sent to Destination A or Destination B. Set two endpoints, one for each destination, and route all events pertaining to group-A to use Destination A's endpoint and route all events pertaining to group-B to use Destination B's endpoint. Functions require you to build out event handlers for each event type (track/identify/page/screen/group/alias), so make sure all events you want sent to each destination are configured appropriately. +[Destination Function](https://segment.com/docs/connections/functions/destination-functions/) : Create a Destination Function in your [workspace](https://app.segment.com/goto-my-workspace/functions/catalog/new) and select Destination for a Destination Function. Build out the destination function's code to handle the logic to check whether the event should be sent to Destination A or Destination B. Set two endpoints, one for each destination, and route all events pertaining to group-A to use Destination A's endpoint and route all events pertaining to group-B to use Destination B's endpoint. Functions require you to build out event handlers for each event type (track/identify/page/screen/group/alias), so make sure all events you want sent to each destination are configured appropriately. diff --git a/src/engage/quickstart.md b/src/engage/quickstart.md index 7e61c32b0c..e33b23ad8b 100644 --- a/src/engage/quickstart.md +++ b/src/engage/quickstart.md @@ -46,7 +46,7 @@ Invite teammates to your Engage dev space and grant them access to the space. Na 3. Toggle the **Replay data** flag when connecting a new source : `enabled` vs. `disabled`. - **Enabled :** The **Replay data** flag is enabled by default when connecting a source to an Engage/Unify Space. Enable this flag to replay the last month of data into the Engage/Unify Space. - **Disabled :** You can disable this option by toggling it, which prevents the replaying of historical data from the source to the Space. This means that only data that the source has received after the point when the source was connected to the Space will be available within the Engage/Unify Space. -4. If you need more historical data available from this source, please fill out the form below for each replay and contact Segment Support at friends@segment.com or [create a ticket]([url](https://app.segment.com/goto-my-workspace/home?period=last-24-hours&v2=enabled&help=create-ticket)): +4. If you need more historical data available from this source, please fill out the form below for each replay and contact Segment Support at friends@segment.com or [create a ticket](https://app.segment.com/goto-my-workspace/home?period=last-24-hours&v2=enabled&help=create-ticket): ``` Segment Source Details: diff --git a/src/guides/what-is-replay.md b/src/guides/what-is-replay.md index ef3faba484..7db26b3e31 100644 --- a/src/guides/what-is-replay.md +++ b/src/guides/what-is-replay.md @@ -71,7 +71,7 @@ There are two types of replays with Engage. - When a new Profile Source is connected to an Engage Space, the default option to replay the source's data seen over the past 30 days can be selected. To request a source's additional historical data be replayed to the Engage Space, contact Segment Support at friends@segment.com or [create a ticket](https://segment.com/docs/engage/[url](https://app.segment.com/goto-my-workspace/home?period=last-24-hours&v2=enabled&help=create-ticket)). Please see [this documentation](https://segment.com/docs/engage/quickstart/#step-3-connect-production-sources:~:text=Step%203%3A%20Connect,production%20sources.) on further details of this process and what to include in your support request. **2. Replay from an Engage Space to its connected destination** -- Since each instance of a destination is connected to its own Engage "Output" source, that source contains events for all of the computations that destination is connected to received data from, _the list of output sources can be found under Unify > Unify Settings > Debugger_. Because of this, it's not possible to replay only a specific computation's data to the destination, you should instead consider reaching out to [Segment support]([url](https://segment.com/help/contact/)) to request a resync of that computation to its destination instead. However, if you would like to replay all failed events seen by that destination, which will encompass all connected computations, that can be achieved with a replay. +- Since each instance of a destination is connected to its own Engage "Output" source, that source contains events for all of the computations that destination is connected to received data from, _the list of output sources can be found under Unify > Unify Settings > Debugger_. Because of this, it's not possible to replay only a specific computation's data to the destination, you should instead consider reaching out to [Segment support](https://segment.com/help/contact/) to request a resync of that computation to its destination instead. However, if you would like to replay all failed events seen by that destination, which will encompass all connected computations, that can be achieved with a replay. - Note: The replay will be sending historical data to the destination, potentially overwriting the destination with outdated data if more recent data has been sent from the computation to the destination. In this case, a resync of the computation might also be more advantageous to get the most up-to-date data resent to the destination. - Rate limits for replays are configurable and can be increased or decreased upon request. However, there are some destinations which have strict rate limits and cannot be configured to send data at a higher rate than what's stated within the table on [Rate limits on Engage Event Destinations](https://segment.com/docs/engage/using-engage-data/#rate-limits-on-engage-event-destinations).