Offline sales can only be attributed if the shopper identifier you send matches one you already collect on your site or app. Before you start, make sure your onsite tracking is live and note which identifier you send with it.
Choose an integration method
You can also pass offline sales through a data partner you already work with, such as a CRM, loyalty, digital receipt, integration platform or point-of-sale provider. Contact your Criteo representative to discuss this option.
Whichever method you choose, contact your Criteo representative first. They will give you your Criteo account ID and SFTP location, or the API access you need, and will agree the setup with you.
What you need to send
Every offline sale must contain:- A shopper identifier that matches your onsite integration (see Shopper identifiers).
- A transaction ID, shared by all the products in the same purchase.
- A timestamp, accurate to the minute.
- The products purchased, each with its product ID, unit price and quantity.
- A currency, unless all your sales are in the account’s default currency.
Shopper identifiers
Criteo supports three identifiers. Send at least one, and use the same one you already send with your onsite tracking so offline sales can be matched to ad exposure.Hashing emails
Criteo expects emails hashed as a SHA-256 hash of an MD5 hash. If you cannot produce that format, you can send a raw or MD5-hashed email and Criteo will hash it on ingestion. Before hashing:- Trim all spaces before and after the address.
- Clean it by removing commas, semicolons, quotes and double quotes.
- Convert it to lowercase.
- Encode it in UTF-8.
Product IDs
Product IDs must match the IDs in your online product catalog. Offline sales for products that are not in the catalog cannot be attributed to the matching ads.Option 1: Flat file over SFTP
File format
- Use CSV, TSV or TXT, with the header in the first row.
- Use lowercase headers with no spaces. If you use custom header names, they must also be lowercase. Criteo maps them to the fields below during setup.
- Send one row per product. Rows that belong to the same purchase must share the same
event_id. Criteo groups the rows byevent_idand calculates the transaction total from price and quantity.
Fields
Example
Delivery
- Upload your files to the SFTP folder Criteo gives you, or let Criteo download them from your own SFTP server.
- Send files at least once a day. Criteo can process files as often as every hour.
- Use a file name that includes the date, for example
retailername_offline_sales_2026_06_23.csv. - If your security policy requires the file to be encrypted before upload, tell your Criteo representative. Criteo can share a public key for you to encrypt with.
Option 2: Offline sales API
The API accepts one shopper per request, with all of that shopper’s transactions in anevents array. Contact your Criteo representative to get access.
unique_name_logs is used for logging only. Use the format clientname_offlinesales.
Request body
Account and shopper
If you hold several identifiers for the same shopper, you can add them in
alternate_ids, each with a type, a value and, for hashed values, a hash_method.
Events
Example
When do sales appear in reporting?
The maximum ingestion delay is 48 hours, so any transaction older than that is rejected.
Test and validate
Before going live:- Send a small sample (a few transactions) through your chosen method and ask your Criteo representative to confirm it was received and parsed correctly.
- Check that the shopper identifier, product IDs and transaction IDs in the sample match what your onsite integration sends.
- Confirm the currency and timestamps are correct, including time zones.
- Once sales are flowing, wait up to 30 days after the last data fix before judging results. Sales cannot be attributed to ad events older than 30 days.