Articles on: Platform Features

Search Arbitrage Settings

Search arbitrage means buying traffic from ad networks and sending visitors to search feed platforms. Platforms like Tonic, System1, Sedo, and Ads.com display keyword-driven search results. They pay you a share of the revenue from clicks.


Data passing complexity

Search arbitrage platforms have more complex URL structures than typical affiliate networks. You often need to pass keywords, site IDs, ad titles, and other parameters through multiple tracking layers.


Revenue reporting from these platforms is also delayed. Initial conversion events may show estimated revenue in near real-time. However, the final accurate figures can arrive hours or days later through a separate callback.


This delay creates a problem. If both the initial and updated events reach your traffic source, it may double-count revenue. That distorts its optimization algorithms.


The Disable Postbacks Feature

FunnelFlux provides a disable_postbacks parameter to handle this. Add it to a postback URL to prevent FunnelFlux from forwarding that event to the traffic source.


How it works

Append &disable_postbacks=true to the end of any postback URL:

https://your-tracking-domain.com/postback?hit={hit_id}&revenue={revenue}&disable_postbacks=true

When FunnelFlux receives a postback with this parameter:

  • The conversion or revenue update is recorded in FunnelFlux as normal
  • The event is not forwarded to the traffic source


You keep full control over which events reach the traffic source.


For search arbitrage campaigns, use a two-postback approach:

  1. Initial postback (real-time, estimated revenue)
  • The search platform fires this when a conversion occurs
  • FunnelFlux records the estimated revenue and forwards it to the traffic source
  • The traffic source gets timely data for optimization
  1. Delayed update postback (accurate revenue, postbacks disabled)
  • The platform fires this when final revenue is ready
  • Append &disable_postbacks=true to this postback URL
  • FunnelFlux records the updated revenue but does not forward it


This approach ensures:

  • The traffic source gets one timely revenue signal for optimization
  • FunnelFlux keeps accurate, final revenue data
  • No double-counting occurs at the traffic source level


Offer source guides

For platform-specific setup instructions, see the dedicated guides in Offer Source Guides:


These guides cover URL config, data passing, token mappings, and postback setup.

Updated on: 05/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!