To optimize prospecting campaigns (which acquire new customers), Axon highly recommends 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.
transaction_id.
Axon ignores any data row with a transaction_id that already exists in its system.
If rows with duplicate transaction_ids exist in a single file, Axon keeps the one with the earliest event_timestamp and discards the rest.Your CSV file must include all the required headers listed below, though certain fields are optional to populate.
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 | No | 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 |
idfv | No | String | The user’s identifier for vendors. | f325g3gb-12fc-352f-c6c3-dz52f0f690d8 |
ifa | No | String | The user’s identifier for advertisers. This is either IDFA or GAID. | 918f1d4f-d195-4a8b-af47-44683fe11db9 |
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 |
user_id and email.
Axon rejects rows that are missing values for those columns.event_name column must exist and its value must be purchase.value column must contain a non-negative number (≥0).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 KingdomHere is an example of a valid CSV file:
Providing customer data to Axon is subject to your own privacy compliance requirements, including any necessary notices and consents.
Axon hashes plaintext email addresses and phone numbers that you provide.
If you would prefer to perform your own hashing, do so by carefully following these guidelines:
email
: Remove any leading or trailing whitespace.
Convert any uppercase characters to lowercase.
Then hash via SHA256.
phone
: Remove any leading or trailing whitespace.
Also remove any leading zeros.
Remove any dashes, plus-signs, or other symbols.
Convert any letters to their numerical counterparts.
Always include the country code (for example, 1 for United States phone numbers).
Then hash via SHA256.
For example (for email addresses):