Traffic Source Postbacks in CPV tracker (CPV Lab or CPV One) are the reverse of affiliate network postbacks. Instead of receiving conversions from a network, CPV tracker (CPV Lab or CPV One) sends conversion data back to your traffic source. This is often called “conversion tracking” or “pixel firing” inside ad platforms. It allows ad networks to optimize automatically based on real performance data.
Why It Matters
- Auto-Optimization: Many ad platforms use conversion data to adjust bidding algorithms. Without sending back conversions, platforms only optimize on clicks, not results.
- Smart Bidding: Features like Facebook’s “Conversion Campaigns” or Google Ads’ “Target CPA” require conversion feedback.
- Transparency: Networks can verify that campaigns are delivering results.
How It Works in CPV tracker (CPV Lab or CPV One)
- Generate Traffic Source Postback URL: CPV tracker (CPV Lab or CPV One) provides a template for each traffic source (Google Ads, Facebook Ads, Taboola, PropellerAds, etc.).
- Configure Tokens: The postback must include the traffic source’s unique click or impression ID (e.g., {adid}, {clickid}) so conversions can be tied to the right click.
- Add Postback in Traffic Source: You paste the CPV tracker (CPV Lab or CPV One)-generated URL into the traffic source’s conversion tracking settings.
- Conversion Occurs: When CPV tracker (CPV Lab or CPV One) receives a conversion from the affiliate network, it also fires the postback to the traffic source.
- Optimization Enabled: The traffic source adjusts bids, placements, or audiences using conversion data.
Example
You run a campaign on PropellerAds, which requires conversion postbacks with the {zoneid} and {clickid} tokens. CPV tracker (CPV Lab or CPV One), you configure the traffic source template and generate the following:
https://propellerads.com/postback?cid={clickid}&payout={payout}
When a user converts, CPV tracker (CPV Lab or CPV One) fires this postback, passing the PropellerAds Click ID and payout. PropellerAds then knows which zone and placement delivered the conversion and can optimize your traffic automatically.
Benefits
- Improved ROI: Letting traffic sources optimize based on real conversions reduces wasted spend.
- Automation: Eliminates manual blacklisting of poor placements.
- Accuracy: Ensures traffic source algorithms work with the same conversion data you see in CPV tracker (CPV Lab or CPV One).
Reporting in CPV tracker (CPV Lab or CPV One)
Conversions remain visible in CPV tracker (CPV Lab or CPV One) reports regardless of whether they are sent back to the traffic source. The postback simply mirrors this data externally.
Best Practices
- Always test postbacks to ensure data flows correctly.
- Match CPV tracker (CPV Lab or CPV One) Click IDs with the correct traffic source tokens (mistakes here break reporting).
- Avoid sending “test conversions” to traffic sources, as this can skew optimization.
- Use postbacks only for traffic sources that support them—some require API-based integrations instead.
Common Issues
- Duplicate Conversions: Can occur if multiple postbacks are configured incorrectly.
- Discrepancies: Traffic source reports may not always match CPV tracker (CPV Lab or CPV One) 1:1 due to attribution models.
- Missing Tokens: If the traffic source click ID isn’t captured in the Campaign URL, CPV tracker (CPV Lab or CPV One) cannot return conversions correctly.
In summary, Traffic Source Postbacks in CPV tracker (CPV Lab or CPV One) are essential for running campaigns on platforms that depend on conversion data for optimization. They ensure that both you and the traffic source have consistent performance data, enabling smarter, automated scaling.
See also: Campaign URL, S2S Postback, Token, Traffic Source
« Back to Glossary Index