Order history data for prospecting campaigns
此内容尚不支持你的语言。
To optimize prospecting campaigns (which acquire new customers), it is critical that you provide Axon with order history data. This allows Axon to build an accurate model of your existing customers so it can find new, high-value users.
If you are a Shopify user who installed the Shopify Axon app and connected it to your Axon Ads Manager account, you’re ready!
Otherwise, follow the requirements below to upload this data in CSV form.
File upload requirements
- File format: CSV only.
- File size: Maximum file size of 200 MB per file.
- Upload method: You can upload files directly, via a public URL, or via SFTP.
- Multiple files: You can upload multiple files. The data from each new file are added to your existing backfilled data.
- Deduplication: Axon automatically deduplicates orders based on the
transaction_id. Axon ignores any data row with atransaction_idthat already exists in its system. If rows with duplicatetransaction_ids exist in a single file, Axon keeps the one with the earliestevent_timestampand discards the rest.
Field specifications
Your CSV file must include all the required headers listed below.
The column order does not matter, but the header names must match exactly.
Event window: Axon processes only those events that occurred in the past two years. Axon excludes events that are older than two years.
| Field | Value required? | Type | Description | Value |
|---|---|---|---|---|
country_code | Yes | String | An ISO 3166 country code | US |
currency | Yes | String | The currency of the transaction in ISO 4217 format (3-letter code) | USD |
email | Yes | String | The customer’s email address. Provide the plaintext email; Axon will hash it on its side. | customer@example.com |
event_name | Yes | String | Must be purchase | purchase |
event_timestamp | Yes | String | The time the purchase occurred
|
|
transaction_id | Yes | String | A unique identifier for the order (e.g., order ID, checkout ID). This is crucial for deduplication. | txn_12345 |
user_id | Yes | String | Your internal customer ID. | user_abc123 |
value | Yes | Double | The total value of the transaction. Must be a number greater than or equal to 0. Do not include currency symbols. | 99.99 |
zip | Yes | String | The customer’s zip code. This must be the billing zip code of the transaction. For U.S. zip-codes, only include the first five digits. | 12345 |
phone | No | String | The customer’s phone number. Must include the country code (e.g., +1). Provide the plaintext number; Axon will hash it on its side. | +14155551234 |
Key validation rules
- Headers: The file must contain all the required headers listed above.
- Identifier requirement: Each row must contain a
user_idandemail. Axon rejects rows that are missing values for those columns. - Event name: The
event_namecolumn must exist and its value must bepurchase. - Transaction value: The
valuecolumn must contain a non-negative number (≥0). - Country code: For privacy compliance reasons, Axon does not accept data from the following countries/regions:
AX— Åland IslandsAD— AndorraAT— AustriaBE— BelgiumDK— DenmarkFO— Faroe IslandsFI— FinlandFR— FranceDE— GermanyGI— GibraltarGR— GreeceGG— GuernseyIS— IcelandIE— IrelandIM— Isle of ManIT— ItalyJE— JerseyLI— LiechtensteinLU— LuxembourgMT— MaltaMC— MonacoNL— NetherlandsNO— NorwayPT— PortugalSM— San MarinoES— SpainSJ— Svalbard & Jan MayenSE— SwedenCH— SwitzerlandGB— United Kingdom
Example CSV file
Here is an example of a valid CSV file:
event_name,user_id,phone,email,event_timestamp,value,currency,transaction_id,country_code,zippurchase,user_abc123,+14155551234,user@example.com,2025-11-10T16:45:00Z,99.99,USD,txn_12345,US,12345purchase,user_def456,+14155555678,customer@example.com,2025-11-10T16:45:00Z,149.5,USD,txn_67890,US,12345purchase,user_ghi789,+14155559012,shopper@example.com,2025-11-10T17:20:00Z,75,EUR,txn_11223,US,12345