Amazon EventBridge Destination

To set up:

1. In Segment, provide your AWS Account ID and the region you'd like to configure the Segment Partner Event Source in. Ensure the same region is selected in both Segment and AWS.
2. Once you send an event through with the destination enabled, Segment creates a Partner Event Source in Amazon EventBridge. You can then activate this source in the AWS Console.
3. Use the AWS Console to configure rules and destinations for the events in your Segment Partner Event Source.

The Event Source will be denoted by your Segment Source ID, which you can find in Source Settings under API Keys.

All messages in the source (pending any Destination Filters you've enabled) are fowarded to the Segment Partner Event Source, created in EventBridge.

If you're not familiar with the Segment Specs, review the Page method docs for more detail. An example Page call is as follows:

  analytics.page();

If you're not familiar with the Segment Specs, review the Identify method docs for more detail. An example Identify call is as follows:

1
analytics.identify('97980cfea0085', {
2
  email: 'gibbons@example.com',
3
  name: 'John Gibbons'
4
});

If you're not familiar with the Segment Specs, review the Track method docs for more detail. An example Track call is as follows:

1
analytics.track("User Registered", {
2
  checkinDate: new Date(),
3
  myCoolProperty: "foobar",
4
});

You can only configure one AWS Account ID per source. Once you've configured your Amazon EventBridge destination with an AWS Account ID, you cannot modify it. If you need to change the AWS Account ID, you need to create a new Segment source and configure a new destination.

Alternatively, you can sync a Repeater destination to your existing source. It repeats the events through the new source you've created. This new source can then be connected to a new EventBridge destination which can be configured with a new Account ID in the settings.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Segment lets you change these destination settings from the Segment app without having to touch any code.