Send events (CEP)

PreviousSynchronize profiles (CEP)NextBraze

Last updated 1 month ago

Send events (CEP)

Overview

In this destination service, DinMo will export events in the profiles of your Customer Engagement Platform.

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

Creating a Batch destination. Refer to the for more info.
Creating a user segment composed of all the events and their attributes that will be sent in Batch. Refer to this to learn how to build segments without SQL in DinMo.
Activating the segment to the Batch destination to start sending data. Refer to the for more info.

Any records added to your model or segment are treated as new events and are sent to Batch when your sync runs.

Destination setup

To start updating attributes, you are first required to create a Batch destination with the corresponding destination service.

To connect DinMo to Batch, you will need an API Key. To get your API and project key, navigate to settings (in Batch) and copy your REST API Key and Project Key into DinMo.

Activation configuration

Once the destination has been setup, and your DinMo event segment (or model) created, you can create an activation to start sending data to Batch right away.

Fields mapping

In the Fields mapping section, you are asked to specify the field contained in your DinMo segment that Batch will use to link each segment's records to a Batch contact (Custom Profile ID). Depending on your Batch configuration, it may be the email address of the user, or another external ID.

You are also asked to specify the event name.

Event name values must be lowercase alphanumeric with underscores. It must be under 30 characters.

You can also map standard attributes linked to your event, especially the time of occurence and the event label.

Profile Attributes

In this section, any field you select will be exported as a custom attribute (of the event) in Batch. The associated field will have the same name in Batch and DinMo.

These values of the attributes selected here will then be updated at each activation.

Attribute names should be made of letters, numbers or underscores ([a-z0-9_]). They cannot be longer than 30 characters and cannot contain uppercase characters.

PreviousSynchronize profiles (CEP)NextBraze

Last updated 1 month ago

Overview

In this destination service, DinMo will export events in the profiles of your Customer Engagement Platform.

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

Creating a Batch destination. Refer to the for more info.
Creating a user segment composed of all the events and their attributes that will be sent in Batch. Refer to this to learn how to build segments without SQL in DinMo.
Activating the segment to the Batch destination to start sending data. Refer to the for more info.

Any records added to your model or segment are treated as new events and are sent to Batch when your sync runs.

Destination setup

To start updating attributes, you are first required to create a Batch destination with the corresponding destination service.

To connect DinMo to Batch, you will need an API Key. To get your API and project key, navigate to settings (in Batch) and copy your REST API Key and Project Key into DinMo.

Learn how to create such a destination in our

Activation configuration

Once the destination has been setup, and your DinMo event segment (or model) created, you can create an activation to start sending data to Batch right away.

Learn how to activate a segment in our

Fields mapping

You are also asked to specify the event name.

Event name values must be lowercase alphanumeric with underscores. It must be under 30 characters.

You can also map standard attributes linked to your event, especially the time of occurence and the event label.

Profile Attributes

In this section, any field you select will be exported as a custom attribute (of the event) in Batch. The associated field will have the same name in Batch and DinMo.

These values of the attributes selected here will then be updated at each activation.

Attribute names should be made of letters, numbers or underscores ([a-z0-9_]). They cannot be longer than 30 characters and cannot contain uppercase characters.