AdMaven sources,matched to the payout

The AdMaven template captures the click ID, the cost of each visit and five details: campaign name and ID, creative, source and sub-source. Its postback to xml.ad-maven.com is ready to use, with no placeholders, and sends each conversion back with its payout in value.

Start for free

Read the setup guide

AdMaven

Performance pop and push ad network

At a glance

How it connects

Campaign URL macros + S2S postback

What syncs

Click ID, visit cost, campaign, creative, source, sub-source

Sync schedule

Real time, per conversion

Key parameters

{:click_id}, {:cost}, {:source_id}, {:sub_source_id}

Works with

Pop, push, in-page push, interstitial, content locker

Good to know

AdMaven macros keep a colon inside the braces. Don't remove it.

Pop & push network

Ready-to-use postback

Source and sub-source

Find the AdMaven sub-sources worth keeping

Source and sub-source columns

source_id and sub_source_id land in their own columns, so you see which publishers convert and can block or bid up sources in AdMaven.

Nothing to fill in

The template's postback has no placeholders. Turn it on, pick the event, save. ClickFlare fills {external_id} and {payout} when it fires.

Cost per visit from the URL

{:cost} passes the cost of each click or view. With the Not Tracked cost model, ROI follows what AdMaven actually charged.

How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

Your ad

Visitor clicks

Ad on AdMaven

ClickFlare

Click recorded

A unique cf_click_id is created

Your offer

Conversion

Lead, sale or custom event

ClickFlare

Sent back to AdMaven

Through the Conversion API or postback

Cost API

Spend pulled in

AdMaven cost matched to each campaign

Your ad

AdMaven 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 AdMaven

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

AdMaven 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

AdMaven

Offer or call

The network tracks the action

AdMaven

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

AdMaven

Store or funnel

Click ID kept through checkout

Events

View, cart, checkout

Each step tracked

ClickFlare

Purchase recorded

Order value matched to the ad

Pop & push network

How an AdMaven click reaches the c parameter

AdMaven opens your campaign URL with its click ID in clickid and the cost in cost. ClickFlare stores the click ID as the External ID. On conversion, ClickFlare sends it back in c, with count=1 and the payout in value.

clickid in the URL, c in the postback
Five free tracking fields for country, OS, ISP
Test Conversion in AdMaven opens a valid test click

Today, one campaign

example

Spend pulled from AdMaven

cost

$412.30

Conversions recorded

today

Sent back to AdMaven

per event

38/38

Profit

campaign

$227.70

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

Captured on every AdMaven click

key macros

{:click_id}, {:cost}, {:source_id}, {:sub_source_id}

captured

From the AdMaven 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 AdMaven 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 macros captured

Free tracking fields

2.3B

Events tracked

Setup

Connected in four steps

You need an AdMaven advertiser panel, your own tracking domain and an offer in ClickFlare.

Add the AdMaven traffic source In the campaign editor, click + New Traffic Source and pick the AdMaven template. It fills in the click ID, cost and five tracking macros.
Turn on the postback as it is Switch on Traffic source postback URL and leave the template's URL unchanged. Choose the ClickFlare event AdMaven should optimize on and save.
Copy the campaign URL Set the cost model to Not Tracked so ClickFlare reads the cost from the URL. Add your offer, save and copy the campaign URL from your own domain.
Launch and test in AdMaven Turn on conversion tracking in the AdMaven campaign and paste the HTTPS URL, with no shortener. In Conversion Tracking, click Test Conversion, convert and click Refresh.

AdMaven postback, ready to use in ClickFlare

http://xml.ad-maven.com/conversion?c={external_id}&count=1&value={payout}

app.clickflare.com/integrations

AdMaven

Pop & push network

Connected

AdMaven account connected

Signed in from ClickFlare

Cost syncing

Spend matched to campaigns

Conversions sent back

Your chosen events

AdMaven template selected

Macros pre-filled

Tracking URL in AdMaven

Click ID captured

Conversions reported

Payout included where supported

AdMaven connected

Credentials saved in ClickFlare

Conversion event set

Click ID passed to the feed

Revenue syncing

On the feed's schedule

AdMaven added

Offer URL carries the click ID

Postback set in AdMaven

Payout and event included

Conversions arriving

Matched to the click

AdMaven connected

Click ID kept to checkout

Events mapped

View, cart, checkout, purchase

Purchases tracked

Order value in reports

Ready to track

If AdMaven's Tracking URL page shows an account value the template lacks, such as info, use AdMaven's URL with {external_id} and {payout} in its click ID and value parameters.

AdMaven postback setup guide

Open the guide

In your reports

What you see once it's connected

Conversions by source
ROI by sub-source
Revenue by AdMaven campaign
Creative comparison
Cost per visit

Use cases

How media buyers run it

AdMaven pop → offer

Pop to offer

Group by sub_source_id, then block the sites and widgets that spend without converting.

AdMaven content locker → lander → offer

Content locker funnels

Compare landers on the same sources and keep the one with the best ROI.

One event, clean counts

Map the postback to your final sale. Leads still show in ClickFlare, but AdMaven's conversion count stays true.

Frequently asked questions

Questions about AdMaven

No items found.

Related integrations

More templates that plug into the same ClickFlare account.

Clickadu

Self-serve popunder and banner network

Pop & push network

A-ADS

Crypto advertising network (AADS)

Crypto ad network

ActiveRevenue

Self-serve advertising platform (DSP)

Self-serve DSP

Adcash

Self-serve advertising platform

Pop & display network

Admixer

Programmatic DSP for display and video

Programmatic DSP

Adnium

Self-serve CPM ad network

Pop & banner network

Browse all integrations ->

Setup guides

AdMaven postback setup guide

{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with AdMaven?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The AdMaven template captures the click ID, visit cost and five tracking macros, and includes a ready-made S2S postback with payout."}}, {"@type": "Question", "name": "Do I need to edit the AdMaven postback?", "acceptedAnswer": {"@type": "Answer", "text": "No. It has no placeholders. ClickFlare fills {external_id} and {payout} when it fires. Only swap it if AdMaven's Tracking URL page shows an extra account value."}}, {"@type": "Question", "name": "Why do AdMaven macros have a colon?", "acceptedAnswer": {"@type": "Answer", "text": "That's AdMaven's macro format, for example {:click_id}. ClickFlare's own tokens have no colon. Keep each one exactly as the template writes it."}}, {"@type": "Question", "name": "Can I send several events to AdMaven?", "acceptedAnswer": {"@type": "Answer", "text": "AdMaven's postback carries no event name, so every postback counts as a conversion. Send only the event you want AdMaven to optimize on."}}, {"@type": "Question", "name": "Why is it clickid in the URL and c in the postback?", "acceptedAnswer": {"@type": "Answer", "text": "They are two halves of the same value. ClickFlare reads the click ID from clickid, and AdMaven expects it back in c. Keep both names."}}, {"@type": "Question", "name": "Does AdMaven accept any campaign URL?", "acceptedAnswer": {"@type": "Answer", "text": "The URL must be HTTPS and must not pass through a URL shortener, which can strip the parameters."}}]}

AdMaven sources,matched to the payout

Find the AdMaven sub-sources worth keeping

Source and sub-source columns

Nothing to fill in

Cost per visit from the URL

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

How an AdMaven click reaches the c parameter

Connected in four steps

What you see once it's connected

How media buyers run it

Pop to offer

Content locker funnels

One event, clean counts

Questions about AdMaven

Related integrations

Your AdMaven sources, tracked to the payout.