Axon Ads
Destination - Vendo uploads conversion events to the Axon Ads Conversion API. Axon Ads does not currently accept audiences from Vendo.
Axon Ads is also available as a source for campaign, creative set, and attribution performance data.
What Vendo Sends
The Axon Ads destination sends conversion events in batches of up to 100 events.
| Output | Description |
|---|---|
| Conversion events | Purchases, signups, and other modeled conversion events |
| Event metadata | Event name, conversion timestamp, value, currency, transaction ID, and dedupe ID |
| User match data | Axon click ID, first-party IDs, hashed email/phone, IP, user agent, cookies, and mobile IDs where mapped |
| Measurement partner data | Claimable Axon attribution payload when an Axon click ID is present |
Required Credentials
The app connection asks for the Axon keys used by both source and destination flows.
| Credential | Used for |
|---|---|
| Axon Event Key | Sent as the pixel_id for conversion uploads |
| Axon Conversion API Key | Sent in the Authorization header for conversion uploads |
| Axon Reporting Key | Used by the Axon Ads source, not by conversion upload |
Required Event Fields
The destination schema requires these fields to be mapped for the conversion stream.
| Field | Purpose |
|---|---|
event_name | Conversion event name |
timestamp | Conversion timestamp |
aleid | Axon click ID from the original AppLovin ad click |
At send time, Vendo also requires a conversion time, an event source URL, browser IP, browser user agent, and at least one usable user identifier such as client_id, axwrt, alart, user_id, email, or phone.
Optional Match Fields
Map as many identifiers as you can to improve match quality.
| Field | Description |
|---|---|
email | User email, hashed before upload |
phone | User phone number, hashed before upload |
client_id | Stable first-party browser or customer identifier |
axwrt | Axon Pixel _axwrt cookie value |
alart | Axon app attribution query parameter |
client_ip | Browser IP address |
client_user_agent | Browser user agent |
country | Billing country code |
zip | Billing ZIP or postal code |
What Vendo Does Not Send
| Data / action | Status |
|---|---|
| Audiences | Not supported for Axon Ads |
| User profile updates | Not supported |
| Campaign changes | Not supported |
| Source performance import | Use the Axon Ads source |
Setup
- Navigate to Destinations in the Vendo app and select Axon Ads
- Enter the Axon Event Key and Axon Conversion API Key
- Choose the model or event table that contains the conversions to upload
- Map the required conversion fields and the strongest available match identifiers
- Save the destination and run a test export
Verify Setup
- Confirm the Axon Ads destination status is Active
- Run a small conversion export
- Check the export job for rows sent and rows failed
- Verify the uploaded events in Axon reporting
Troubleshooting
| Symptom | What to check |
|---|---|
| Destination validation fails | Confirm the Axon Event Key and Conversion API Key are present |
| Rows are skipped before upload | Confirm conversion time, event source URL, IP, user agent, and at least one user identifier are mapped |
| Click attribution is missing | Confirm aleid is populated from the Axon click ID |
| Events upload but values look wrong | Check value, currency, and transaction ID mappings |
Last updated on