A-ADS traffic,measured by ad unit

ClickFlare's A-ADS template reads the partner value, which identifies the campaign and ad unit, plus device, browser, OS, country and language on every click. With a CPA deal, ClickFlare calls the A-ADS Goal Tracking API on each paid conversion, and A-ADS pays the publisher behind that ad unit.

AA
A-ADS
Crypto advertising network (AADS)
At a glance
How it connects
Goal tracking suffix + Goal Tracking API call
What syncs
Ad unit (partner), device, browser, OS, country, language
Sync schedule
Real time, per conversion
Key parameters
partner, device_type, os_name, http_country_code, browser_name
Works with
Text ads, graphic banners, responsive teasers
Good to know
The API call is for CPA advertisers with an A-ADS agreement.
Crypto ad network
Goal Tracking API
9 macros captured

Know which A-ADS ad units are worth paying for

Ad unit reports

The partner value joins campaign ID and ad unit ID, so grouping by External ID shows which publisher's ad unit converts. A-ADS recommends dropping the weak ones.

Useful without a CPA deal

Goal tracking can run for analysis alone. CPD buyers still get ad unit, device and country data in ClickFlare, with the postback left off.

Pay only for the agreed action

Every Goal API call pays a publisher. Map the postback to one custom conversion, such as deposit, and earlier funnel steps cost you nothing there.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversion

01
Your ad
Visitor clicks
Ad on A-ADS
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to A-ADS
Through the Conversion API or postback
05
Cost API
Spend pulled in
A-ADS cost matched to each campaign
01
Your ad
A-ADS click
Macros fill the tracking URL
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to A-ADS
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
A-ADS API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
cf_click_id passed to the offer
03
A-ADS
Offer or call
The network tracks the action
04
A-ADS
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
A unique cf_click_id is created
03
A-ADS
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
Crypto ad network

From A-ADS ad unit to publisher reward

A-ADS appends a goal tracking suffix with {{partner}} and its other macros to your ad link. ClickFlare stores partner as the External ID. On the agreed conversion, it calls the Goal Tracking API with a unique ID, your password and the reward in satoshi.
  • Ad link and goal tracking suffix are set separately
  • Reward is a whole number of satoshi
  • A-ADS adds its fee on top of the reward
Today, one campaign
example
Spend pulled from A-ADS
cost
$412.30
Conversions recorded
today
38
Sent back to A-ADS
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
Captured on every A-ADS click
key macros
partner, device_type, os_name, http_country_code, browser_name
captured
From the A-ADS 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 A-ADS 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.
9
Macros in the template
2
Extra macros worth adding
2.3B
Events tracked
Setup

Connected in four steps

You need an A-ADS campaign, a ClickFlare account with your own tracking domain and, for the postback, a CPA agreement and API password from A-ADS.
  1. Add the A-ADS traffic source In the campaign editor, click + New Traffic Source and pick the A-ADS template. It maps {{partner}} to the External ID and fills eight tracking fields.
  2. Fill in the Goal API call, if you have CPA terms Turn on Traffic source postback URL. Replace password=REPLACE with your A-ADS password and amount=REPLACE with a whole number of satoshi. Edit or remove comment=OPTIONAL. Map it to the paid action.
  3. Pick the cost model and copy the URL For CPD buying, choose Not Tracked and upload daily spend. Add your lander and offer, save, and copy the campaign URL from your own tracking domain.
  4. Split the URL in A-ADS Set the ad link to the campaign URL without the ? part. Turn on Goal tracking and paste the ? part, starting with ?partner={{partner}}, as the suffix.
A-ADS Goal Tracking API call, filled in
https://a-ads.com/api/v1/goals/create.json?unique_id={cf_click_id}&password=YOUR_PASSWORD&amount=5000&partner={external_id}&duration=259200
app.clickflare.com/integrations
AA
A-ADS
Crypto ad network
Connected
A-ADS account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
A-ADS template selected
Macros pre-filled
Tracking URL in A-ADS
Click ID captured
Conversions reported
Payout included where supported
A-ADS connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
A-ADS added
Offer URL carries the click ID
Postback set in A-ADS
Payout and event included
Conversions arriving
Matched to the click
A-ADS connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Ready to track
Don't put {payout} in amount. ClickFlare's payout is a decimal in your currency, and A-ADS reads amount as satoshi. Every accepted call spends real money from your A-ADS balance.
A-ADS postback setup guide
Open the guide
In your reports

What you see once it's connected

  • Conversions by ad unit
  • ROI by publisher
  • Device type breakdown
  • Browser and OS splits
  • Country code reports
  • Browser language reports
Use cases

How media buyers run it

Crypto banners → exchange offer

Run A-ADS banners to a crypto offer on CPA terms, reward publishers only on deposit, and keep signups as an internal step in ClickFlare.

CPD buying with ad unit analysis

Buy A-ADS on cost per day, leave the postback off, upload daily spend, and ask A-ADS for more traffic from the ad units that convert.

Banner size testing

Add the banner_size macro and compare 728x90 against other sizes by conversions before producing more creatives.
Frequently asked questions

Questions about A-ADS

No items found.
Setup guides
A-ADS postback setup guide
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with A-ADS?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare has an A-ADS traffic source template that captures A-ADS's goal tracking macros and can call the A-ADS Goal Tracking API on conversions."}}, {"@type": "Question", "name": "Does A-ADS have a postback URL?", "acceptedAnswer": {"@type": "Answer", "text": "A-ADS uses a Goal Tracking API call to a-ads.com/api/v1/goals/create.json. It is open to CPA advertisers who have agreed terms with an A-ADS manager."}}, {"@type": "Question", "name": "Is the A-ADS partner value a click ID?", "acceptedAnswer": {"@type": "Answer", "text": "No. It is the campaign ID and ad unit ID, for example 12345_67890, and many visits share it. ClickFlare stores it as the External ID because A-ADS needs it to know which publisher to reward."}}, {"@type": "Question", "name": "Can I send my payout as the A-ADS amount?", "acceptedAnswer": {"@type": "Answer", "text": "No. The amount is the reward A-ADS pays the publisher, in satoshi, charged to you. It comes from your CPA agreement, not your payout."}}, {"@type": "Question", "name": "Do I need the postback if I only buy on CPD?", "acceptedAnswer": {"@type": "Answer", "text": "No. Turn on Goal tracking in A-ADS so the macros reach ClickFlare, leave Traffic source postback URL off, and analyze ad units in ClickFlare."}}, {"@type": "Question", "name": "Why do A-ADS macros use double braces?", "acceptedAnswer": {"@type": "Answer", "text": "That is A-ADS's macro format, such as {{partner}}. ClickFlare tokens use single braces, such as {external_id}. Use double braces in the campaign URL and single braces in the postback."}}]}