Amplitude for Currents

Amplitude is a product analytics and business intelligence platform.

The Braze and Amplitude bi-directional integration allows you to sync your Amplitude Cohorts, user traits, and events into Braze as well as leverage Braze Currents to export your Braze events to Amplitude to perform deeper analytics of your product and marketing data.

Prerequisites

Data export integration

A full list of the events and event properties that can be exported from Braze to Amplitude can be found in the following sections. All events sent to Amplitude will include the user’s external_user_id as the Amplitude user ID. Braze-specific event properties will be sent under the event_properties key in the data sent to Amplitude.

Braze will only send event data for users who have their external_user_id set or anonymous users who have their device_id set. For the anonymous users, you will need to sync your Amplitude device ID with the Braze device ID in the SDK. For example:

1
amplitude.setDeviceId(Appboy.getInstance(context).getDeviceId();)

You can export two types of events to Amplitude: Message Engagement Events consisting of the Braze Events directly related to message sending, and Customer Behavior Events, including other app or website activity such as sessions, custom events, and purchases tracked through the platform. All regular events are prefixed with [Appboy], and all custom events are prefixed with [Appboy] [Custom Event]. Custom event and purchase event properties are prefixed with [Custom event property] and [Purchase property], respectively.

All cohorts named and imported into Braze will be prefixed with [Amplitude] and suffixed with their cohort_id. This means that a cohort named “TEST_COHORT” with the cohort_id “abcd1234” will be titled [Amplitude] TEST_COHORT: abcd1234 in Braze filters.

Contact your account manager or open a support ticket if you need access to additional event entitlements.

Step 1: Configure Amplitude Integration in Braze

In Amplitude, locate your Amplitude export API key.

Step 2: Create Braze Current

In Braze, navigate to Currents > + Create Current > Create Amplitude Export. Provide an integration name, contact email, Amplitude export API key, and Amplitude region in the listed fields. Next, select the events you want to track; a list of available events is provided. Lastly, click Launch Current

Rate limits

Currents connect to Amplitude’s HTTP API, which has a rate limit of 30 events/second per device and an undocumented limit of 500K events/day per device. If these thresholds are exceeded, Amplitude will throttle events logged through Currents. If a device in your integration exceeds this rate limit, you may experience a delay in when events from all devices will appear in Amplitude.

Devices should not report more than 30 events/second or 500K events/day under normal circumstances, and this event pattern should only occur due to a misconfigured integration. To avoid this type of delay, ensure that your SDK integration reports events at a normal rate as specified in our SDK integration instructions and refrain from running automated tests that generate many events for a single device.

Supported Currents events

Braze supports exporting the following data listed in the Currents user behavior and message engagement event glossaries to Amplitude:

Behaviors

• Custom event: users.behaviors.CustomEvent
• Install Attribution: users.behaviors.InstallAttribution
• Location: users.behaviors.Location
• Purchase: users.behaviors.Purchase
• Uninstall: users.behaviors.Uninstall
• App (first session, session end, session start)
  • users.behaviors.app.FirstSession
  • users.behaviors.app.SessionEnd
  • users.behaviors.app.SessionStart
• Subscription (global state change): users.behaviors.subscription.GlobalStateChange
• Subscription Group (state change): users.behaviors.subscriptiongroup.StateChange

Campaigns

• Abort: users_campaigns_abort
• Conversion: users.campaigns.Conversion
• EnrollinControl: users.campaigns.EnrollInControl

Canvas

• Abort: users_canvas_abort
• Conversion: users.canvas.Conversion
• Entry: users.canvas.Entry
• Exit (matched audience, performed event)
  • users.canvas.exit.MatchedAudience
  • users.canvas.exit.PerformedEvent
• Experiment Step (conversion, split entry)
  • users.canvas.experimentstep.Conversion
  • users.canvas.experimentstep.SplitEntry

Messages

• Content Card (abort, click, dismiss, impression, send)
  • users.messages.contentcard.Abort
  • users.messages.contentcard.Click
  • users.messages.contentcard.Dismiss
  • users.messages.contentcard.Impression
  • users.messages.contentcard.Send
• Email (abort, bounce, click, delivery, markasspam, open, send, softbounce, unsubscribe)
• In-app message (abort, click, impression)
  • users.messages.inappmessage.Abort
  • users.messages.inappmessage.Click
  • users.messages.inappmessage.Impression
• Push notification (abort, bounce, iOSforeground, open, send)
  • users.messages.pushnotification.Abort
  • users.messages.pushnotification.Bounce
  • users.messages.pushnotification.IosForeground
  • users.messages.pushnotification.Open
  • users.messages.pushnotification.Send
• SMS (abort, carrier send, delivery, delivery failure, inbound receive, rejection, send, short link click)
  • users.messages.sms.Abort
  • users.messages.sms.Delivery
  • users.messages.sms.DeliveryFailure
  • users.messages.sms.InboundReceive
  • users.messages.sms.Rejection
  • users.messages.sms.Send
  • users.messages.sms.ShortLinkClick
• Webhook (abort, send)
  • users.messages.webhook.Abort
  • users.messages.webhook.Send
• WhatsApp (abort, delivery, failure, inbound receive, read, send)
  • users.messages.whatsapp.Abort
  • users.messages.whatsapp.Delivery
  • users.messages.whatsapp.Failure
  • users.messages.whatsapp.InboundReceive
  • users.messages.whatsapp.Read
  • users.messages.whatsapp.Send