What Are Postbacks?
Postbacks are HTTP notifications that OnlyTraffic sends to your server or tracking platform when specific events occur — like a new subscriber joining or a transaction happening. They let you track conversions in real time without manually checking the dashboard.Setup Levels
You can configure postbacks at two levels:
Campaign-level postbacks take priority over account-level settings when both are configured.
Campaign-level: on the CPL or RevShare campaigns page open the campaign’s actions menu (the … button in its row) and choose Postbacks. A campaign that already has a custom destination shows a Postback chip in its row; clicking the chip opens the same editor.
Account default: go to Tools → Postback Logs and click Default postback. There you can also push the default to campaigns you already run (active campaigns without a postback, all active, all without a postback, or all). Pushing to “all active” or “all” replaces whatever those campaigns have now, ad-platform pixel setups included.
Available Events
new_subscriber
Fired when a new fan subscribes through your campaign.
new_transaction
Fired when a fan makes a purchase (tip, paid message, paid post, subscription, resubscription, or stream).
new_dialog
Fired once per fan when they send the model three or more messages.
marketing_stop
Fired when a campaign or CPL order is stopped (completed, cancelled, or paused).
URL Template & Macros
Build your postback URL using macros that get replaced with actual values when the event fires.Event Macro
Campaign Macros
Subscriber Macros
Available fornew_subscriber, new_transaction and new_dialog events:
Transaction Macros
Available for thenew_transaction event:
Click Macros
Available when using OT Tracking Links or Smart Links:Click Param Macros
Any parameter you add to a tracking-link click asparams[NAME]=VALUE is readable back as {{click_params.NAME}}, for example {{click_params.fbp}} or {{click_params.uid}}. UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term), gclid and msclkid are captured automatically. Up to 30 params per click, name up to 64 and value up to 255 characters; a param that did not arrive on the click resolves to an empty string.
Modifiers
Append a modifier to any macro to transform its value before sending:HTTP Methods
Custom Headers
You can add custom HTTP headers to your postback requests. This is useful for:- Authentication tokens (e.g.,
Authorization: Bearer your_token) - Content type specification (e.g.,
Content-Type: application/json) - Any custom headers your tracking platform requires
Example Postback URLs
Testing Postbacks
You can test your postback configuration before going live:1
Set up your postback URL
Configure your postback URL with the desired macros.
2
Click Send test
Use the Send test button under the event in the postback editor. Every macro found in your URL, body or headers becomes a field prefilled with a sample value; edit the values if you like and click Send now. The request goes out from OnlyTraffic’s servers exactly like a real event, and the HTTP status and response body are shown right there. Test sends are not recorded in Postback Logs.
3
Verify receipt
Check that your server or tracking platform received the test postback and parsed the parameters correctly.
Postbacks work best with OT Tracking Links that support the
click_id parameter. This allows you to match each conversion back to the exact click in your external tracker.