Amazon EventBridge Destination
Amazon EventBridge quick info
Amazon EventBridge is in beta, and accepts Track, Page, Identify, Group, and Alias calls. If you reference it in the Integrations object, call it “Amazon EventBridge”.
Amazon EventBridge accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.
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 | ✅ | ✅ | ✅ |
- 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.
- 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.
- 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.
Page
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:
analytics.page();
Identify
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: 'gibbons@example.com',
name: 'John Gibbons'
});
Track
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",
});
FAQ
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.
Personas
You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for 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, Personas 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), Personas sets that value to false
.
When you first create an audience, Personas 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.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
AWS Account ID
The ID of the AWS Account you’d like us to send data to.
Region
The EventBridge Firehose AWS region key.
This page was last modified: 09 Jun 2020
Need support?
Questions? Problems? Need more info? Contact us, and we can help!