Pull events from Braze Currents¶
Braze is a leading marketing automation platform that allows users to create custom experiences based on sophisticated customer attributes and segments, then map those experiences to campaigns.
About Braze Currents¶
Response data from campaigns that are run in Braze Currents can be integrated using Braze Currents , which synchronizes response data into the following event catagories:
Pull events from Braze Currents¶
Your brand has the following options for pulling Braze Currents events to Amperity:
Amazon S3¶
Your brand can configure Braze Currents to send events to an Amazon S3 bucket , from which you can pull those events to Amperity.
To pull events using Amazon S3
![]() |
Open the Currents page Log in to Braze. From the left-side navigation choose Partner Integrations, and then Data Export. This opens the Currents page. |
![]() |
Create current Click the Create new current button, and then select Amazon S3 Data Export. |
![]() |
Configure credentials Give the integration a name and provide a contact email address. Use a secret access key or a role ARN. AES-256 encryption may be enabled. Provide the name of an Amazon S3 bucket that is managed by your brand, along with the folder to which Braze Currents will send events data. |
![]() |
Configure events data Under Data configuration a list of message engagement events is shown. Review the list of events that can be sent, and then choose which ones you want to send to Amperity. You can select all message events or can select individual events, such as “Email click”, “Email open”, “Email unsubscribe”, or “Push open”. |
![]() |
When finished configuring the current click Launch current. Allow up to 30 minutes for the current to start sending events data. |
![]() |
Log in to Amperity and configure a data source that uses Amazon S3 to pull the events data from the customer-managed Amazon S3 bucket to Amperity. |
Azure Blob Storage¶
Your brand can configure Braze Currents to send events to an Azure Blob Storage container , from which you can pull those events to Amperity.
To pull events using Azure Blob Storage
![]() |
Open the Currents page Log in to Braze. From the left-side navigation choose Partner Integrations, and then Data Export. This opens the Currents page. |
![]() |
Create current Click the Create new current button, and then select Azure Blob Data Export. |
![]() |
Configure credentials Give the integration a name and provide a contact email address. Add the Azure Blob Storage connection string, the name of an Azure Blob Storage container, along with the prefix to which Braze Currents will send events data. |
![]() |
Configure events data Under Data configuration a list of message engagement events is shown. Review the list of events that can be sent, and then choose which ones you want to send to Amperity. You can select all message events or can select individual events, such as “Email open”, “Email unsubscribe”, “SMS/MMS delivery”, or “Push open”. |
![]() |
When finished configuring the current click Launch current. Allow up to 30 minutes for the current to start sending events data. |
![]() |
Log in to Amperity and configure a data source that uses Azure Blob Storage to pull the events data from a customer-managed Azure Blob Storage bucket to Amperity. |
Google Cloud Storage¶
Your brand can configure Braze Currents to send events to a Google Cloud Storage bucket , from which you can pull those events to Amperity.
To pull events using Google Cloud Storage
![]() |
Open the Currents page Log in to Braze. From the left-side navigation choose Partner Integrations, and then Data Export. This opens the Currents page. |
![]() |
Create current Click the Create new current button, and then select Google Cloud Storage Data Export. |
![]() |
Configure credentials Give the integration a name and provide a contact email address. Provide JSON credentials for Google Cloud Storage. Provide the name of a Google Cloud Storage bucket that is managed by your brand, along with the prefix to which Braze Currents will send events data. |
![]() |
Configure events data Under Data configuration a list of message engagement events is shown. Review the list of events that can be sent, and then choose which ones you want to send to Amperity. You can select all message events or can select individual events, such as “Canvas step progression”, “Email open”, “Content card click”, or “In-app message click”. |
![]() |
When finished configuring the current click Launch current. Allow up to 30 minutes for the current to start sending events data. |
![]() |
Log in to Amperity and configure a data source that uses Google Cloud Storage to pull the events data from the customer-managed Google Cloud Storage bucket to Amperity. |
Streaming API¶
Your brand can configure Braze Currents to send events to an Amperity Streaming API endpoint using a custom currents export .
To collect events using the Amperity Streaming API
![]() |
Log in to Amperity and configure a Streaming API endpoint to send events data to Amperity using Braze Currents. You will need to add an API key and generate an access (bearer) token for Braze Currents. Configure a dedicated streaming API endpoint for Braze Currents. |
![]() |
Open the Currents page Log in to Braze. From the left-side navigation choose Partner Integrations, and then Data Export. This opens the Currents page. |
![]() |
Create current Click the Create new current button, and then select Custom Currents Export. |
![]() |
Configure credentials Give the integration a name and provide a contact email address. Add the Streaming API endpoint and bearer token that you created in Amperity for use with Braze Currents. |
![]() |
Configure events data Under Data configuration a list of message engagement events is shown. Review the list of events that can be sent, and then choose which ones you want to send to Amperity. You can select all message events or can select individual events, such as “Email click”, “Email open”, “Email unsubscribe”, or “Push open”. |
![]() |
When finished configuring the current click Launch current. Allow up to 30 minutes for the current to start sending events data. |