Event exports to Amplitude

You can easily export events data from Blueshift with other systems. Events data is associated with customer activities based on unique profile identifiers. Use this data to further analyze the user behavior and make decisions about your product.

Prerequisites

You have set up your Amplitude adapter.

Setup

You can export data from Blueshift to Amplitude in JSON format.

To export data, go to Customer Data > Events in the left navigation.
Click the Export Events icon in the top right corner and click Export Events.
In the Select a Destination page, select Amplitude.
Add an Event Feed Name for the task, and click OK. The export task form opens.
The Source section on the left rail displays the type of data you are exporting, events in this case.
The Destination section displays the destination app where you intend to forward the data. Example, Amplitude.
In the Destination Configuration section, select the desired adapter you want to connect to and click Continue to proceed to the next step.
Note: You can setup multiple tasks with same adapter, but only one task can be active at a time.
In the Configuration section, you can either select specific user events or select the main Standard and Custom check boxes on top to export all the standard and custom events at once. Click Continue to move to the next step.
In the Additional Configuration section, in the User ID field, choose which customer identifier you want to send to Amplitude as User ID. The other available options are Email, Customer ID and any other customer identifiers configured for your account. Note: Device ID and Cookie ID are not available for this selection.
The Select Fields to Suppress field shows all the user attributes based on the events you've selected in the previous step. Select the attributes that you want to suppress in the exports to Amplitude.
Click Launch to launch the export task.
Note that it might take a few minutes for the data to be seen on the Event Exports Index page.

Editing an export task

You can pause and edit a launched task from the Event Exports index page. You can only review and edit the current events that are being sent to Amplitude and modify list of suppressed attributes and User ID selection. The changes will take effect once you launch the paused task.

View Event Exports

You can view and manage export tasks from Event Exports Index page.

To view export events, go to Customer Data > Events in the left navigation.
Click the Export Events icon in the top right corner and click View Exports.
The Event Exports index page displays a list of event export tasks.
To edit, pause/unpause or archive a task, click on the three-dot menu on the task as shown in the image above.

The Event Exports index table has the columns as follows:

Field	Description
Name	Name of the export feed.
Destination	Where the event data is being exported to (Amplitude).
Status	Whether the export is currently running, paused, archived, or in draft status.
Author	Who created the export.
Events Synced	Number of events successfully synced to Amplitude within a date range. The synced and errored event stats automatically updates based on the date range that you need.
Events Errored	Number of events that failed to sync to Amplitude, if any.

Task statuses

Keep track of your event export tasks in Blueshift. The different statuses you might see are:

Event status	Description
Draft	The export task has been created but not yet launched. All fields in the export form are open for configuration.
Launched	The export task is actively sending event data to Amplitude in real-time.
Paused	The export is temporarily halted. No new events data are sent until you resume it.

Rate limits

Amplitude limits event volume to 30 events per second per device or per user (measured as an average over a recent time window). When this threshold limit is reached, Amplitude will throttle the events.
By default, Blueshift honors Amplitude's starter plan rate limit which is 1000 events per second. If your rate exceeds this limit, you may experience delay in events getting synced with Amplitude.

Considerations for Amplitude Event exports

Amplitude mandates presence of either user_id or device_id field in the event payload. If value for neither fields is present in the payload, events will not get ingested into Amplitude. When you map a customer identifier to user_id at the time of setup, please make sure that the customer identifier is present in the incoming events
Blueshift maps the device_id that has been setup as part of Blueshift’s mobile SDK implementation by the customers, to the device_id attribute sent to Amplitude. The list of device identifiers that Blueshift SDK supports can be found here for Android and here for iOS.
Blueshift sends events to Amplitude in batches of five events. Amplitude rejects the entire batch, if any one event in the batch fails validation(eg. user_id value not present). Amplitude presents error reason only for the first event in the batch for which error is encountered. You can access the success and error responses from Amplitude using the Debug Event export API.
There may be delay of up to 1 minute in any configuration change to take effect.