Send conversion events
Last updated
Last updated
With this destination service, DinMo will send conversion events (online or offline) to optimize targeting (for instance: clicks, add to carts, purchase, etc.).
To do so, you will need to go through these three steps:
Creating a Meta destination. Refer to the for more info.
Creating an event segment composed of all the events you wish to send to Meta. All records of the segment correspond to a unique event type (for instance, purchase) and a unique action source (for instance, physical store), that was previously created in Meta. Refer to this to learn how to build segments without SQL in DinMo.
Activating the segment to the Meta destination to start sending data. Refer to the for more info.
DinMo will be sending all the new conversion events each time the activation is running.
To start sending conversion events, you are first required to create a Meta destination with the corresponding destination service.
You will need to specify the dataset id (previously named pixel id) to which your events will be sent.
Note: If the dataset id you seek is not listed, it means that the user who connected DinMo to Meta does not have the permissions for this account.
Once the destination has been setup, and your DinMo segment containing all your conversion events created, you can create an activation to start sending data to Meta right away.
When setting up a activation, you need to specify the related event type. All records of the segment will be considered as events of the selected type (for instance, 'Drive to store', 'Purchase', etc.).
Make sure your segment only contains conversions of the selected type.
You can choose to synchronize standard events, but you can also send custom events. In the last case, the custom event type you enter will be created in Meta. If an event type with the same name already exists in your Meta dataset, DinMo will simply be sending data to this event type.
DinMo will consider that all your segment's data correspond to one particular action source.
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. Any non mapped fields in your segment will not be sent to Meta.
Meta 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
If the conversion is transactional (i.e referring to a purchase), you must also map the two following fields:
Value: The price spent by the customer during the transaction
Currency: The currency of the transaction
It is highly recommended to map the Event Id or Order Id field, but it is not compulsory.
To increase the chance of identifying the user behind the conversion, you can also map the following fields:
Email: The email addresses of the users. It can be in clear text, or hashed (SHA-256)
Phone number: The phone numbers of the users. E164 format is preferred ('+49xxxxxxxx'). It can be in clear text, or hashed (SHA-256)
First Name: It can be in clear text, or hashed (SHA-256)
Last Name: It can be in clear text, or hashed (SHA-256)
Gender: Either 'm' or 'f'. It can be in clear text, or hashed (SHA-256)
Postal Code: It can be in clear text, or hashed (SHA-256)
Country Code: 2-letter country code in ISO-3166-1 alpha-2 of the user’s address. It can be in clear text, or hashed (SHA-256)
ZIP code: Use lower case characters, without space. For the US, only keep the first 5 digits. For the UK, use the region/constituency/sector format. It can be in clear text, or hashed (SHA-256)
City: It can be in clear text, or hashed (SHA-256)
The higher the number of fields you send, the most likely Meta will be able to identify the users.
In this section, specify how often the conversions should be sent to Meta.
All new conversions will be sent in batch to Meta at the specified time interval.
Note that Meta might reject conversions that are more than 7 days old.
Learn how to activate a segment in our