AppLovin cost and conversions,linked by two API keys

ClickFlare pulls AppLovin campaign cost with your Reporting API Key and sends the conversions it tracks back to AppLovin through the Conversion API, using your Event Key and Conversion API Key. Spend and conversion signals stay in sync without browser-based reporting.

Start for free

Read the setup guide

AppLovin

Ad platform with a Conversion API

At a glance

How it connects

Event Key + Conversion API Key; Reporting API Key for cost

What syncs

Conversion events out, campaign cost in

Sync schedule

Conversions per event; cost pulled automatically

Key parameters

aleid, campaign_id, creative_set_id, placement_id, ad_type

Works with

Campaigns with the CAPI integration connected

Good to know

Create the traffic source from the prebuilt AppLovin template

Ad platform

Reporting API cost

Conversion API

AppLovin signals that don't rely on the browser

Less data loss

API reporting avoids browser restrictions and blocked client-side tracking, so AppLovin gets more reliable conversion signals.

All keys in one place

The Event Key, Conversion API Key and Reporting API Key all sit under Keys in your AppLovin dashboard.

Creative and placement detail

The AppLovin template passes creative set, placement and ad size, so ROI breaks down by the units that convert.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Your ad

Visitor clicks

Ad on AppLovin

ClickFlare

Click recorded

A unique cf_click_id is created

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to AppLovin

Through the Conversion API or postback

Cost API

Spend pulled in

AppLovin cost matched to each campaign

Your ad

AppLovin click

Macros fill the tracking URL

ClickFlare

Click recorded

Zone, site and device data stored

Offer or lander

Visitor converts

On your page or the offer

ClickFlare

Conversion logged

With payout and event type

Postback

Reported to AppLovin

So its optimization sees the result

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

Your article

Keyword block

Click ID passed to the feed

Results page

Paid click

Conversion fired to ClickFlare

AppLovin API

Revenue matched

Pulled on a schedule and reconciled

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

cf_click_id passed to the offer

AppLovin

Offer or call

The network tracks the action

AppLovin

Conversion

Lead, sale, call or rebill

Postback

Payout in ClickFlare

Matched to the original click

Your ad

Visitor clicks

Any traffic source

ClickFlare

Click recorded

A unique cf_click_id is created

AppLovin

Store or funnel

Click ID kept through checkout

Events

View, cart, checkout

Each step tracked

ClickFlare

Purchase recorded

Order value matched to the ad

Ad platform

Keys in AppLovin, mapping in ClickFlare

Enter the Event Key and Conversion API Key, map ClickFlare events to AppLovin conversion events and add any extra event data. Connect the integration on a campaign, and ClickFlare sends that campaign's selected events to AppLovin.

Some event fields are sent by default
CAPI connected per campaign
Cost assigned through the traffic source

Today, one campaign

example

Spend pulled from AppLovin

cost

$412.30

Conversions recorded

today

Sent back to AppLovin

per event

38/38

Profit

campaign

$227.70

Example numbers. Cost and conversions sit in the same report row.

Captured on every AppLovin click

key macros

aleid, campaign_id, creative_set_id, placement_id, ad_type

captured

From the AppLovin template in ClickFlare. Use them as report columns and rules.

Revenue for one click

example

Paid click

day 0

$0.00

First revenue pull

+1h

$0.41

Scheduled updates

next days

$0.58

Final pull

last sync

$0.62

Example amounts. Sync timing for AppLovin is in the facts above.

Events for one click

example

Lead

day 0

$0.00

Sale

day 0

+$40.00

Upsell

day 1

+$15.00

Refund

day 9

−$15.00

Example events. Each one arrives by postback and is matched to the click.

One visitor's path

example

Product view

step 1

—

Add to cart

step 2

—

Checkout

step 3

—

Purchase

step 4

$68.00

Example order. Each event is tied to the ad that brought the visitor.

Tracking fields captured

2.3B

Events tracked

Setup

Connected in four steps

You need an AppLovin account with its Event Key, Conversion API Key and Reporting API Key, and a ClickFlare account.

Copy your AppLovin keys In the AppLovin dashboard, go to Keys. Copy the Event Key (Pixel ID), the Conversion API Key and the Reporting API Key.
Add the AppLovin Conversion API In ClickFlare, open Integrations → Conversion API Integrations and select AppLovin. Enter the keys, map ClickFlare events to AppLovin events, set the event data and save.
Connect AppLovin cost Under Cost Integrations, select AppLovin, paste the Reporting API Key, pick the integration timezone and save. Optionally assign traffic source configurations.
Link it to your campaign Create the AppLovin traffic source from the prebuilt template and select the cost integration on it. Then connect the CAPI integration at campaign level.

app.clickflare.com/integrations

AppLovin

Ad platform

Connected

AppLovin account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

AppLovin template selected

Macros pre-filled

Tracking URL in AppLovin

Click ID captured

Conversions reported

Payout included where supported

AppLovin connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

AppLovin added

Offer URL carries the click ID

Postback set in AppLovin

Payout and event included

Conversions arriving

Matched to the click

AppLovin connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Ready to track

If the cost integration isn't assigned to the traffic source configuration, ClickFlare won't pull AppLovin cost.

AppLovin Conversion API setup guide

Open the guide

In your reports

What you see once it's connected

Cost per campaign
ROI by creative set
Results by placement ID
Placement type breakdown
Results by ad type and size
Ad creative type breakdown

Use cases

How media buyers run it

AppLovin → lander → offer

Send the final conversion back through CAPI so AppLovin optimizes on what pays, with cost pulled by the Reporting API.

Creative set testing

Compare ROI across creative sets and ad creative types from the template, then move budget to the winners.

Placement pruning

Group by placement ID and placement type to find the inventory that costs more than it returns.

Frequently asked questions

Questions about AppLovin

No items found.

Related integrations

More templates that plug into the same ClickFlare account.

Whop

Ads for Whop businesses

Ad platform

BIGO Ads

In-app ads on BIGO apps and network

In-app ad network

Google Ads

Search, display and YouTube ads

Search ad platform

LinkedIn Ads

LinkedIn Campaign Manager

Social ad platform

MGo

MediaGo

Baidu's native ad platform

Native ad network

Meta Ads

Facebook Ads platform

Social ad platform

Browse all integrations ->

Setup guides

AppLovin Conversion API setup guide

AppLovin cost integration guide

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with AppLovin?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare pulls AppLovin cost through the Reporting API and sends conversions back through the AppLovin Conversion API."}}, {"@type": "Question", "name": "Which AppLovin keys do I need?", "acceptedAnswer": {"@type": "Answer", "text": "The Event Key (Pixel ID) and Conversion API Key for conversions, and the Reporting API Key for cost. All three are under Keys in AppLovin."}}, {"@type": "Question", "name": "When does ClickFlare start sending events to AppLovin?", "acceptedAnswer": {"@type": "Answer", "text": "After you connect the CAPI integration at campaign level. ClickFlare then sends the selected events from that campaign."}}, {"@type": "Question", "name": "Why is my AppLovin cost missing?", "acceptedAnswer": {"@type": "Answer", "text": "The cost integration isn't assigned to the traffic source configuration. Select it under the traffic source's Cost Integration settings."}}, {"@type": "Question", "name": "Can I change the default event fields?", "acceptedAnswer": {"@type": "Answer", "text": "Some fields are sent by default and can't be changed or removed. You can add more data in the Event Data Configuration."}}]}

AppLovin cost and conversions,linked by two API keys

AppLovin signals that don't rely on the browser

Less data loss

All keys in one place

Creative and placement detail

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Keys in AppLovin, mapping in ClickFlare

Connected in four steps

What you see once it's connected

How media buyers run it

AppLovin → lander → offer

Creative set testing

Placement pruning

Questions about AppLovin

Related integrations

AppLovin spend and conversions, both by API.