Skip to main content

How to Configure Axon (Formerly AppLovin) Conversion API (CAPI)

Updated over 2 weeks ago

WorkMagic's Conversion API Enhancer lets you send enriched, WorkMagic-attributed events directly to your connected ad platforms — including Axon (formerly AppLovin). This helps improve event match quality and campaign optimization by using more precise, incrementality-calibrated conversion data.


Use Cases

Here's what you can do once Axon is connected:

Use Case

Description

Send WorkMagic-attributed purchase events

Push high-quality conversion events to Axon CAPI for performance optimization.

Improve match quality with enriched data

Use enriched customer PII (e.g., email, phone) to increase event match rates.


Step-by-Step: How to Set Up Axon CAPI

Follow the steps below to configure Axon CAPI inside WorkMagic.

Step 1 — Enable Axon Integration

  • Go to Settings > Conversion API Enhancer.

  • Find the Axon card.

  • Click Set up in Platform Integration to start the integration process.

Step 2 — Configure Settings

After enabling, fill out the configuration form:

Field

Required

Description

Account

Yes

Select your Axon account from the dropdown.

Events to send

Yes

Choose which events to send — Order and/or New customer order.

Attribution models

Yes

Select one or more WorkMagic attribution models to use for the conversion signals sent to Axon.

Subscription orders

Optional

If you offer subscriptions, choose whether to exclude recurring subscription orders.

Supported Attribution Models: WorkMagic supports multiple attribution models for Axon CAPI, including Last paid click, Last click,, Data-driven attribution, First click, and more. You can select one or multiple models depending on your optimization strategy.

Click Save and enable to activate the connection.

Step 3 — Delivery Insights

Once Axon CAPI is active, you can monitor event flow via the Delivery status tab:

  • Event Delivery Overview — Visual chart of events sent over time. Hover to see exact event counts and timestamps.

  • Event Delivery Summary — Breakdown of each event type, total events sent, errors, and last event timestamp.

Step 4 — After Successful Setup

Make sure your feed is stable for at least 2 weeks before initiating testing.

Once your data flow is stable:

  1. Wait at least 2 weeks for consistent event delivery.

  2. Compare performance and observe ROAS, CPA improves overtime

Did this answer your question?