Send track events

Overview

With this destination service, DinMo will send track events (purchases events, conversions, or any custom event) to Braze.

To do so, you will need to go through these three steps:

• Creating a Braze destination. Refer to the corresponding section for more info.

• Creating an event or custom model (or segment) composed of all the events you wish to send to Braze. All records of the segment correspond to a unique event type (for instance, purchase).

• Activating the model to the Braze destination to start sending data. Refer to the corresponding section for more info.

DinMo will only be inserting the newest events each time the activation will be running, without updating the previously inserted events.

Destination setup

Learn how to create such a destination in our step-by-step tutorial

To start sending track events, you are first required to create a Braze destination with the corresponding destination service.

Activation configuration

Learn how to activate a segment in our step-by-step tutorial

Once the destination has been setup, and your DinMo model containing all your events created, you can create an activation to start sending data to Braze right away.

Event name

When setting up a activation, you need to specify the related event name. All records of the model will be considered as events of this specific type (for instance, 'Drive to store', 'Purchase', etc.).

Make sure your segment only contains conversions of the specified type.

You must type the exact event type name, as it appears in Braze. Note that if no event type does with the specified name exists in Braze, DinMo will be creating it.

Fields mapping

In the Fields mapping section, you are asked to specify the meaning of the fields of your segment that you wish to send to Meta.

Braze will use the fields you send to identify the conversions and their values, and recognize each user behind the conversions.

You must map the following field:

• Event time (Required): The timestamp when the conversion took place

• External ID (Required): The external ID of the user at the origin of the event

Refer to this documentation if you want to learn more about Braze external user IDs.

Synchronized attributes

In this section, you can add as many attributes mapping as you would like. These attributes are meant to characterize with more details the events you are sending (for instance, what was the purchase price).

To map an attribute, please select in the left side the DinMo field containing the attribute's value, and in the right side, please type the exact name of the attribute as it appears in Braze.

Note that if the attribute you type does not exist in Braze, DinMo will create it.

Scheduling

In this section, specify how often the events should be sent to Braze.

All new events will be sent in batch to Meta at the specified time interval.