Skip to main content
EvaDav traffic source template EvaDav is a self-serve ad network selling push notification, popunder, native and in-page traffic, on mobile and desktop. This guide sets up EvaDav as a traffic source in ClickFlare. It covers passing EvaDav’s click data into your reports and sending conversions, with payout, back to EvaDav so its automated rules and your stats agree. You do everything from the campaign editor. The EvaDav traffic source is created inline, without leaving the campaign.

​
At a glance

​
How it works

1

EvaDav sends the click

A visitor clicks your ad. EvaDav opens your ClickFlare campaign URL and fills in its macros: the click ID in click_id, the price in cost, plus the source, zone, campaign, creative, format and other details.
2

ClickFlare stores the EvaDav click ID

ClickFlare saves the value of click_id as the visit’s External ID, records the cost, and redirects the visitor to your lander or offer.
3

The conversion reaches ClickFlare

Your affiliate network or store posts the conversion back to ClickFlare, matched on the ClickFlare click ID.
4

ClickFlare posts it back to EvaDav

ClickFlare fires the EvaDav postback, replacing {external_id} with the stored EvaDav click ID and {payout} with the revenue. EvaDav matches it to the original click.
The mirror to keep straight: in the campaign URL you write ClickFlare’s parameter (click_id) and EvaDav’s macro ({CLICKID}). The template does this for you. In the postback URL you write EvaDav’s parameter (click_id) and ClickFlare’s token ({external_id}). Both sides use the same parameter name, but the values on each side are different: EvaDav’s macro in one, ClickFlare’s token in the other.

​
Before you start

  • Set up your own tracking domain. Run the campaign and the postback on your own custom domain. Shared domains get flagged by networks and blocked by browsers. See Custom Domains.
  • Have an offer ready in ClickFlare, and its affiliate network set up to post conversions back to ClickFlare. See Creating an Offer and Adding an Affiliate Network.
  • Set up the postback while you create the campaign. EvaDav’s automated rules can blacklist sources by leads, cost per lead, ROI and profit. If EvaDav receives no leads, those rules don’t work.
  • Decide which conversion EvaDav should receive. EvaDav optimizes on what you send it. If your funnel has several steps (lead, then sale), choose the one that matters most.

​
Step 1 – Create the campaign and the EvaDav traffic source

  1. Go to Campaigns and click New.
  2. In Traffic Source, open the dropdown and click + New Traffic Source.
  3. Type evadav in the search box and select the EvaDav template.
  4. Enter a Name, for example EvaDav.
  5. Leave Cost currency on USD unless your EvaDav account is billed in another currency.
The template fills in the Parameters table for you: The EvaDav template's Parameters table in ClickFlare, with EvaDav's macros pre-filled Each tracking field becomes a column you can group reports by. source_id and zone_id are the ones you will use most. A zone (s123) is the publisher. A source (s123_abc) is one traffic source inside that publisher. Group by zone to find the publishers that convert, and by source to blacklist the exact sources that don’t.
Don’t change or remove the externalId row. EvaDav’s click ID macro is {CLICKID}, with no underscore. {CLICK_ID} is not an EvaDav macro and arrives as literal text. Without a real click ID in the campaign URL, EvaDav cannot match conversions.
To pass more EvaDav data, click Add Parameter, give it a name and parameter, and enter the EvaDav macro as the TS Token. ClickFlare assigns the next free tracking field. EvaDav also offers {BROWSER_VERSION}, {OS_VERSION}, {CITY}, {CONNECTION_TYPE} and {SUB_PERIOD}, the subscriber’s age in days on push traffic. {SUB_PERIOD} is useful for push: fresh subscribers often convert differently from old ones. EvaDav lists all its macros in the Tracking section of your advertiser account.

​
Step 2 – Set up the postback

The postback is what sends conversions to EvaDav. It lives on the traffic source, so every campaign that uses this EvaDav traffic source sends conversions the same way.

​
Add it to the traffic source in ClickFlare

  1. In the New Traffic Source form, scroll to Passing conversion info to traffic source.
  2. Turn on Traffic source postback URL. The template’s postback appears:
The Traffic source postback URL switched on, showing the EvaDav template's postback It already sends the click ID ({external_id}) and the payout ({payout}), both as ClickFlare tokens. There is nothing to replace. EvaDav’s own format is https://evadav.com/phpb?click_id={CLICKID}&payout={PAYOUT}. The template swaps EvaDav’s placeholders for ClickFlare’s tokens.
  1. In the dropdown on the left, choose the ClickFlare event that should fire the postback. Keep Conversions to send every conversion. If your final action is a custom conversion (for example purchase), choose that instead.
  2. Click Save. You are back in the campaign editor with the EvaDav traffic source selected.
Don’t paste EvaDav’s postback with {CLICKID} and {PAYOUT} into ClickFlare. Those are EvaDav’s placeholders, not ClickFlare tokens, and ClickFlare sends them as literal text. Keep {external_id} and {payout}.
EvaDav shows the payout in its statistics and uses it for ROI and profit in automated rules. Send it in the same currency your EvaDav account uses. See Multicurrency in ClickFlare. To learn what each postback token does, see How to Configure a Traffic Source S2S Postback URL.

​
Step 3 – Finish the campaign and copy its URL

  1. Name the campaign.
  2. Set the Cost Model to Not Tracked, so ClickFlare uses the cost EvaDav passes. See Cost.
  3. Choose Redirect or Direct tracking. Redirect is the usual choice for push and popunder traffic.
  4. Click Next and, on Destination, add your lander (optional) and your offer.
  5. Save, open Tracking, select your own tracking domain and copy the campaign URL.
The campaign URL already contains every EvaDav macro from the template, for example click_id={CLICKID} and zone_id={ZONE_ID}. If you use a lander, its call-to-action must link to the ClickFlare click URL, not to the offer directly. Otherwise the visit reaches the offer without a ClickFlare click ID, and the conversion cannot be traced back to EvaDav. See Creating a Campaign in ClickFlare.

​
Step 4 – Create the campaign in EvaDav

  1. In EvaDav, go to Campaigns and click Create.
  2. Enter a Campaign Name.
  3. Paste the ClickFlare campaign URL into the Target URL field.
  4. Upload your creative, add the ad details, choose the target country and set your bid.
  5. Click Create.
Paste the URL exactly as ClickFlare gives it. EvaDav replaces each {...} macro when the ad is clicked. EvaDav warns that wrong macros are the most common advertiser error, and that even an extra space can break tracking.

​
Step 5 – Test the integration

EvaDav can generate a test Click ID so you can check the postback before you spend anything.
  1. In EvaDav, open the Tracking section of your advertiser account and generate a test Click ID.
  2. Take your ClickFlare campaign URL and replace {CLICKID} after click_id= with the test Click ID. Leave the other macros as they are.
  3. Open that URL in a browser and complete the offer the way a real visitor would. ClickFlare stores the test Click ID as the visit’s External ID.
  4. In ClickFlare, go to Logs → Postback Status and filter by the campaign. A successful request to evadav.com/phpb, with your test Click ID in click_id, confirms ClickFlare sent the postback.
  5. In EvaDav’s Tracking section, check that the test conversion was received.
If your offer can’t be completed for a test, wait for the first real conversion and check Logs → Postback Status the same way.

​
Sending only one event

EvaDav’s postback format has one click ID and one payout, and no event parameter. Send EvaDav the conversion you want its rules to act on.
Map the postback to your final conversion, for example a purchase custom conversion. Earlier steps (leads, add to carts) still show in ClickFlare. They just don’t reach EvaDav.EvaDav’s automated rules count what you send as leads. If you send registrations, a rule on cost per lead acts on the cost per registration.
To send a postback only for some conversions, for example only those above a certain payout, use Event filter under the postback to add conditions.

​
Cost

The template passes cost per click. The cost row sends EvaDav’s {COST} macro, which EvaDav describes as your bid value, and ClickFlare records it as the visit’s cost. On the campaign, set the Cost Model to Not Tracked so ClickFlare uses the cost passed in the URL.
EvaDav’s help pages describe {COST} in different ways: as the bid, as the price, and once as the conversion payout. Compare the Cost column with your EvaDav spend after launch. If it doesn’t match, switch the Cost Model to CPC and enter your price per click. If you buy on CPM, enter your CPM bid divided by 1,000 as the cost value.
EvaDav ranks ads by bid times CTR, so a creative with a higher CTR can win at the same bid. The price you pay can therefore differ from creative to creative. The template has no cost integration attached. When the recorded spend differs from your EvaDav spend, correct it with a manual cost upload. See Cost Models.

​
Delayed revenue

If you run search arbitrage (RSOC or AFD) behind EvaDav, the feed reports revenue hours or days after the click. To pass that revenue to EvaDav once it arrives, see Sending Delayed Revenue to Traffic Sources.

​
Troubleshooting

  • Traffic source postback URL is off on the EvaDav traffic source.
  • Disable sending postbacks to traffic source is on in the campaign.
  • The postback contains EvaDav’s {CLICKID} instead of ClickFlare’s {external_id}.
  • The postback is mapped to a different event than the one the conversion logged. Check Logs → Event Logs to see which event was recorded.
  • Check Logs → Postback Status: a failed request shows the status code EvaDav returned.
EvaDav didn’t replace the click ID macro. Check that the campaign URL in EvaDav has click_id={CLICKID} exactly, with no underscore and no spaces. Copy the URL from ClickFlare again if in doubt.
The template sends payout={payout}, so it was removed or edited. Restore &payout={payout} at the end of the postback.Also check that the offer sends a payout to ClickFlare. If ClickFlare records the conversion with a payout of 0, EvaDav receives 0.
The macros were not replaced, usually because the URL was pasted somewhere EvaDav doesn’t process macros, or was edited. Paste the campaign URL from ClickFlare unchanged. See Traffic Source Tokens Arriving Empty.
For the general checklist, see Conversions not showing.
FREQUENTLY ASKED QUESTIONS
Q1: Can I use the same EvaDav traffic source for all my EvaDav campaigns?
A1: Yes. The postback is set once on the traffic source and every campaign using it sends conversions the same way, whatever the ad format. Create a second EvaDav traffic source only if a campaign needs a different postback, for example a different event.
Q2: Do I need to add my EvaDav account ID to the postback?
A2: No. EvaDav’s postback has no account placeholder. EvaDav matches the conversion through the click ID.
Q3: What’s the difference between source_id and zone_id?
A3: zone_id is the publisher, for example s123. source_id is the full source ID inside that publisher, for example s123_abc. Use source_id when you blacklist sources in EvaDav.
Q4: Should I use Redirect or Direct tracking with EvaDav?
A4: Redirect is the usual choice and works with every EvaDav format. Use Direct only if EvaDav must see your lander’s domain as the destination. See Direct Campaign Tracking.
Q5: Other trackers use {CPC} for cost. Should I change the template?
A5: No, not by default. {COST} is the cost macro in EvaDav’s own macro list. Change it only if your Cost column doesn’t match your EvaDav spend, and check EvaDav’s Tracking section for the current macro first.

Traffic source postbacks

Every token you can use in a postback.

Custom conversions

Split leads and sales into separate events.

Cost models

How CPC, CPA and RevShare costs are calculated.

Conversions not showing

The general checklist when postbacks don’t arrive.