Send Offline Conversions
Learn how to use Offline Conversions Events to Snapchat CAPI
Overview
With this destination service, DinMo will send offline conversion events 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 Snapchat destination. Refer to the corresponding section for more info.
Creating an event segment composed of all the events you wish to send to Snapchat.
Activating the segment to the Snapchat destination to start sending data. Refer to the corresponding section for more info.
DinMo will be sending all the new conversion events each time the activation is running.
Destination setup
To start sending conversion events, you are first required to create a Snapchat destination with the corresponding destination service.
Refer to this documentation if necessary.
Activation configuration
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 Snapchat right away.
You will need to specify the pixel id to which your events will be sent to.
Event name
When setting up a activation, you need to specify the related event name.
You can select an Event name if all your events share the same name. If your event data contains the event name in a column, you can leave this field blank and set the Event name to the fields mapping.
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 Snapchat. Any non mapped fields in your segment will not be sent to Snapchat.
Snapchat 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
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 : 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 Snapchat will be able to identify the users.
Scheduling
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.
Warnings
In this section, specify if you want to receive warning for your Azure Storage activation.
Last updated