What are the best practices for offline events data
Your offline event data helps you understand how effectively your ads drive offline events. You can use this information to optimize your ad campaigns.
Below are best practices for preparing and uploading your offline event data.
- Upload your offline event data with precise timestamps and use actual transaction values: Precise timestamps, including minutes and seconds, ensure that each unique event is included, such as multiple purchases made by the same person in one day. Actual transaction values allow you to see the most accurate event values in your reporting. You can see aggregated monetary value of your uploaded, matched and attributed events to better understand the return on your ad spend.
- Include an order ID field and enter a unique identifier for each transaction: Order IDs help deduplicate your offline events and improve attribution. Remember that each order ID should have a unique event time and customer associated with it. If you want to split a transaction into multiple events, you can also use the item number field to provide unique item numbers for each event associated with the same order ID.
- Upload offline event data regularly and in the order that the events occurred (sequentially by date): Regular uploads help minimize gaps in your reporting. We recommend that you upload daily so that offline data can be effectively matched against the performance of any ads you're running. The data you upload is processed in real time, so you can view results as soon as you add it.
- Only upload new data from the time of your last upload: Data is matched against tracked impressions within the last 90 days for events that occurred within 1, 7 or 28 days of an impression. If you've created an offline event set, but haven't uploaded any data within 90 days, you will then only have 35 days to upload content. Once you've uploaded content within 35 days, you will then go back to having 90 days to upload content. It's important to note that we recommend you upload your data as frequently as possible – daily would be ideal. Events that you previously uploaded can't be deleted and our system can only deduplicate events uploaded within a set period of time.
- Assign an event set to an ad account before you begin a campaign: An events set will track an account from the time it's assigned. Remember to enable auto-tracking when creating your set so that any future ad campaigns in the account will automatically be associated. For a more automated process, you can also upload offline event data directly with the offline conversion API or partner integrations.
Related Articles
Setting up Data Source for Snapchat Offline Conversions API
Offline Conversions API can be set-up using any one of the below available data sources that can provide offline events or conversion data. The type of data sources enable reading of CSV files at regular frequency e.g. daily. Data automation can be ...
What are the best Practices for CAPI?
The following Conversions API best practices can help improve your ad performance on the Advertising Platform by lowering your cost per action. To get the most out of your Advertising Platform ads, we recommend using these Conversions API best ...
Overview of Snapchat Offline Conversions API
Overview: Snapchat’s Offline Conversions API is a privacy-focused solution that enables businesses to track offline conversions by directly syncing customer data from in-store purchases, phone orders, and other offline interactions with Snapchat’s ...
TikTok Offline Events API
Description: TikTok for Business offers tools that allow businesses to share the events on their website with TikTok. TikTok Events API is designed to give our advertisers a more reliable connection between TikTok and advertiser marketing data ...
Pre-requisites of Snap Offline Conversions API
Following are few pre-requisites required for Snap Offline CAPI: Access to offline datasource e.g. FTP, AWS, or GCP file source Access to Snapchat Business Manager to obtain Pixel ID and Access token Offline events enabled on the Pixel ID.