The Destination Actions framework improves on classic destinations by enabling you to see and control how Segment sends the event data it receives from your sources, to actions-based destinations. Each Action in a destination lists the event data it requires, and the event data that is optional.
You can also choose which event types, event names, or event property values trigger an Action. These Triggers and mappings make it possible to send different versions of the Action, depending on the context from which it is triggered.
Each Actions-framework Destination you see in the Segment catalog represents a feature or capability of the destination which can consume data from your Segment source. The Action clearly lists which data from the events it requires, and which data is optional. For example, Amplitude requires that you always send a
LogEvent , or Slack always requires a
PostMessage. Each Action also includes a default mapping which you can modify.
Benefits of Destination Actions
- Easier setup: Users see fewer initial settings which can decrease the time spent configuring the destination.
- Increased transparency: Users can see the exact data that is sent to the destination, and when Segment sends it. For example, users can see exactly when Segment sends an IP address to FullStory or an AnonymousId to Amplitude.
- Improved customization: Users can determine how the events their sources trigger and map to actions supported by the destination. For example, define the exact events that are considered purchases by Braze.
- Partner ownership: Partners can own and contribute to any Actions-based destination that use cloud and device mode (web).
Available Actions-based Destinations
The following Actions-based Destinations are available:
Destination Actions compatibility
- Destination Actions are available to all customers on all Segment plans.
- Destination Actions do not require that you disable or change existing destinations. However, to prevent data duplication in the destination tool, you should make sure you aren’t sending the data through both a standard destination and the Actions destination at the same time.
- You can still use the Event Tester with Destination Actions, and event delivery metrics are still collected and available in the destination information pages.
- If you are using Protocols, Destination Actions actions are applied after schema filters and transformations. If you are using destination filters, Actions are applied after the filters - meaning that they are not applied to data that is filtered out.
- Destination Actions can not yet be accessed or modified using the Segment APIs.
Components of a Destination Action
A Destination Action contains a hierarchy of components, that work together to ensure the right data is sent to the destination.
|Define authentication and connection-related information like API and Secret keys.
|Handle the individual calls to the destination. In them, you define what type of call you want to make to the destination, and what Triggers that call. Individual Destination Actions may come enabled with some predefined mappings to handle common events like Screen calls, Identify calls, and Track calls. Mappings have two components that make this possible: Triggers and an Action.
|Enable you to define when the corresponding Action fires. As part of a Trigger, you can use condition-based filters to narrow the scope of the Trigger.
Self-service users can add a maximum of two conditions per Trigger.
|Determine the information sent to the destination. In the Configure action section, you map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected.
For example, in the Amplitude (Actions) destination, you define your API and Secret keys in the destination’s global settings. Then, the provided Page Calls mapping:
- Triggers the action on all incoming Page events.
- Runs the Log Event action, to map your incoming data to Amplitudes properties.
Set up a destination action
To set up a new Actions-framework destination for the first time:
- Log in to the Workspace where you want to add the new destination, go to the Catalog page, and click the Destinations tab. (You can also get to this screen by clicking Add Destination either from an existing Source, or from your list of existing destinations.)
- Click the Destination Actions category in the left navigation, then click the destination you want to add.
- From the preview screen that appears, click Configure.
- If prompted, select the source you want to connect to the new destination.
- Enter your credentials. This could be an API Key and secret key, or similar information that allows the destination to connect to your account.
- Next, choose how you want to set up the destination, and click Configure Actions. You can choose Quick Setup to use the default mappings, or choose Customized Setup (if available) to create new mappings and conditions from a blank state. You can always edit these mappings later.
- Once you’re satisfied with your mappings, click Create Destination.
You must configure and enable at least one mapping to handle a connected source’s event(s) in an Actions-framework destination in order for data to send downstream. Events send downstream in the order in which they appear in the mappings UI. There is no mechanism through which you can control the order of events that send to the downstream destinations outside of that.
Migrate a classic destination to an actions-based destination
Moving from a classic destination to an actions-based destination is a manual process. Segment recommends that you follow the procedure below:
- Create the actions-based destination with your development or test source.
- Copy API keys, connection details, and other settings from the classic destination to the actions-based destination.
- Refer to the actions-based destination’s documentation for information about migrating specific settings.
- Disable the classic version of the destination, and enable the actions-based version.
- Verify that data is flowing from the development or test source to the partner tool.
- Repeat the steps above with your production source.
Migrate to an actions-based destination using Destination Filters
For a more comprehensive migration from a classic destination to an actions-based destination, follow the steps outlined below. This implementation strategy is only available for customers on a Segment Business Tier plan with access to Destination Filters. By adding additional line of defense with Destination Filters, you remove the possibility of duplicate events or dropped events and ensure that events sent before/after a specified
received_at timestamp are sent to each destination.
This migration strategy involves configuring a destination filter on both the Classic destination and the Actions destination. Configure the classic destination filter to block events by the
received_at field with a certain value, and the Actions destination to drop events until the
received_at timestamp field reaches that same value. Destination Filters within the UI have a limitation where they cannot access any top-level fields, but this is not a limitation for Destination Filters created by the Public API using FQL. Because the
received_at is a top-level field in the payload, you’ll need to create a destination filter with the Public API and submit the request with that FQL information described below.
By combining these Filters, Segment sends events through the Classic integration up until a specified time and then blocks events after that time. Then the Actions integration blocks events until that specified time, and only allows events beginning at that specified time.
The following code samples show you how you can create filters for your destinations using the Create Filter for Destination Public API operation.
// JSON BODY :
"title": "drop event after (timestamp) received_at > value April 4, 2023 19:55pm",
"description": "drop event after (timestamp) received_at > value April 4, 2023 19:55pm",
"if": "(received_at >= '2023-04-21T19:55:00.933Z')",
// JSON BODY :
"title": "drop event before (timestamp) received_at < value April 4, 2023 19:55pm",
"description": "drop event before (timestamp) received_at < value April 4, 2023 19:55pm",
"if": "(received_at < '2023-04-21T19:55:00.933Z')",
After configuring the Destination Filter on both the Classic and Actions destination, see each destination’s Filters tab and enable the filters. After completing the migration, you can disable the Classic destination on the Settings page, and remove each of the filters from both destinations.
Edit a destination action
You can add or remove, disable and re-enable, and rename individual actions from the Actions tab on the destination’s information page in the Segment app. Click an individual action to edit it.
From the edit screen you can change the action’s name and mapping, and toggle it on or off. See Customizing mappings for more information.
When an Action is created, it’s disabled by default, to ensure that it’s only used after being fully configured. To begin sending data through an Action, enable it on the Actions page by selecting the toggle so that it appears blue.
Disable a destination action
If you find that you need to stop an action from running, but don’t want to delete it completely, you can click the action to select it, then click the toggle next to the action’s name to disable it. This takes effect within minutes, and disables the action until you reenable it.
Delete a destination action
To delete a destination action: click the action to select it, and click Delete (the trash can icon).
This takes effect within minutes, and removes the action completely. Any data that would have gone to the destination is not delivered. Once deleted, the saved action cannot be restored.
Test a destination action
To test a destination action, follow the instructions in Testing Connections. You must enable a mapping in order to test the destination. Otherwise, this error occurs: You may not have any subscriptions that match this event.
You can also test within the mapping itself. To test the mapping:
- Navigate to the Mappings tab of your destination.
- Select a mapping and click the … and select Edit Mapping.
- In step 2 of the mappings edit page, click Load Test Event from Source to add a test event from the source, or you can add your own sample event.
- Scroll to step 4 on the page, and click Test Mapping to test the mapping and view the response from the destination.
If you use the default mappings for a destination action, you don’t need to customize the mapping template for the action. You can edit the fields later if you find that the defaults no longer meet your needs.
Actions-based destinations have a limit of 50 individual mappings.
To create a custom destination action, start from the Actions tab. If necessary, click New Mapping to create a new, blank action.
- In the edit panel, define the conditions under which the action should run.
- Test those conditions to make sure that they correctly match an expected event. This step looks for events that match the criteria in the debugger queue, so you might need to Trigger some events with the expected criteria to test your conditions. You can skip the test step if needed, and re-try it at any time.
- Select data models to enrich your events with.
- Set up the data mapping from the Segment format to the destination tool format.
- You can click the Source field, then select the Enrichments tab to view and select Enrichments to use.
- Test the mapping with data from a sample event. The edit panel shows you the mapping output in the format for the destination tool. You can change your mapping as needed and re-test.
- When you’re satisfied with the mapping, click Save. Segment returns you to the Mappings table.
- In the Mappings table Status column, verify that the Enabled toggle is on for the mapping you just customized.
The required fields for a destination mapping appear automatically. Click the + sign to see optional fields.
The coalesce function takes a primary value and uses it if it is available. If the value isn’t available, the function uses the fallback value instead.
Self-service users can add a maximum of two conditions per Trigger.
Mapping fields are case-sensitive. The following type filters and operators are available to help you build conditions:
- Event type (
is not). This allows you to filter by the event types in the Segment Spec.
- Event name (
does not contain,
ends with). Use these filters to find events that match a specific name, regardless of the event type.
Event property (
less than or equal to,
greater than or equal to,
does not contain,
does not exist). Use these filters to trigger the action only when an event with a specific property occurs.
You can specify nested properties using dot notation, for example
context.app.name. If the property might appear in more than one format or location, you can use an ANY statement and add conditions for each of those formats. For example, you might filter for both
context.device.type = iosas well as
context.os.name = "iPhone OS
not existoperator matches both a
nullvalue or a missing property.
The available operators depend on the property’s data type:
does not contain,
|string or numeric
is less than,
is less than or equal to,
is greater than,
is greater than or equal to
You can combine criteria in a single group using ALL or ANY. Use an ANY to “subscribe” to multiple conditions. Use ALL when you need to filter for very specific conditions. You can only create one group condition per destination action. You cannot created nested conditions.
Unsupported Special Characters
Mappings do not support the use of double quotes “ or a tilde ~ in the trigger fields.
Mapping fields don’t support dot notation. For example, properties.amount.cost or properties_amount.cost aren’t supported.
Destination filters are compatible with Destination Actions. Consider a Destination Filter when:
- You need to remove properties from the data sent to the destination
- You need to filter data from multiple types of call (for example, Track, Page, and Identify calls)
If your use case does not match these criteria, you might benefit from using Mapping-level Triggers to match only certain events.
FAQ and troubleshooting
Validation error when using the Event Tester
When you send an event with an actions destination Event Tester that doesn’t match the trigger of any configured and enabled mappings, you’ll see an error message that states, You may not have any subscriptions that match this event. To resolve the error, create a mapping with a trigger to handle the event being tested, or update the test event’s payload to match the trigger of any existing mappings.
Data not sending downstream
If no mappings are enabled to trigger on an event that has been received from the connected source, the destination will not send any events. Ensure that at least one mapping has been configured and enabled in the destination mappings for an event that you would like to reach downstream.
Events without mappings enabled to handle them display as being discarded due to “No matching mapping” in a destination’s Delivery Overview.
Multiple mappings triggered by the same event
When the same event triggers multiple mappings, a request will be generated for each mapping that’s configured to trigger on an event. For example, for the Subscription Updated event, if two mappings are enabled and both have conditions defined to trigger on the Subscription Updated event, the two requests will be generated and sent to the destination for each Subscription Updated event.
Oauth “access token expired” message shown in Segment UI
Access Tokens that were generated from initial authorization, for example, when you connect a destination via Oauth, are always short-lived. Commonly, the token remains valid for 30 minutes to 1 hour. When Segment receives 401 error responses from the destination after a token has expired, it will automatically make another request to the destination for a new token and will then retry the event. Therefore, 401 responses are sometimes expected and do not indicate an event failure. There are three event flows when events are received and sent to a destination:
- through source
- through event tester
- through actions tester in mapping screen
The underlying systems for these flows have their own copy of the token, which can expire at different points in time. Threfore, if you see a 401 error in a sample response, it is likely that you’ll also see another request was made after it, to ask the downstream destination for a new token. Then one more request was made to actually send the data in your payload to the downstream destination.
This page was last modified: 16 Feb 2024
Questions? Problems? Need more info? Contact Segment Support for assistance!