Amazon EventBridge Destination

Destination Info
  • Server
Connection Modes
Device-mode Cloud-mode
Web Web
Mobile Mobile
Server Server

Amazon EventBridge is the easiest way to onboard your Segment data into the AWS ecosystem.

In addition to already supported destinations like Kinesis, S3, and Redshift, you can use EventBridge to selectively route streaming data into Amazon SQS, SNS, and any service supported by AWS CloudWatch Events.

Getting Started

Before you start, make sure Amazon EventBridge supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode ⬜️ ⬜️ ⬜️
☁️ Cloud-mode
  1. Provide Segment your AWS Account ID and the region you’d like us to configure the Segment Partner Event Source in. Ensure you’ve provided the same region in Segment where you’d like to configure your Event Bus.
  2. Once you send an event through with the destination enabled, we’ll create a Partner Event Source in Amazon EventBridge, which you can activate 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 your Source Settings page under API Keys.

We’ll forward all the messages in the source (pending any Destination Filters you’ve enabled) to the Segment Partner Event Source we create for you in EventBridge.


If you’re not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like:;


If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example identify call is shown below:

analytics.identify('97980cfea0085', {
  email: '',
  name: 'John Gibbons'


If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example identify call is shown below:

analytics.track("User Registered", {
  checkinDate: new Date(),
  myCoolProperty: "foobar",


Can I change my Account ID?

Currently you can only set up one Account ID per source, and once it is set it cannot be changed.

We recommend that you create a separate Segment source for testing if you use a test Account ID, because you cannot change it to a production Account ID at a later date.


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.

Real-time to batch destination sync frequency

Real-time audience syncs to Amazon EventBridge may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


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

Setting Description
AWS Account ID
string. The ID of the AWS Account you’d like us to send data to.
string, defaults to us-west-2 .

The EventBridge Firehose AWS region key.

This page was last modified: 08 Mar 2022

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account