The above diagram illustrates how the flow of visits and postbacks is intended to work when you integrate Opticks Firewall into your flow.
- Visit - a user coming from your traffic source is redirected to a Opticks campaign URL (read more about creating campaigns).
- Redirect to Advertiser - Once Opticks collects and analyzes information about the user (this happens in a matter of milliseconds), it then redirects the user to you, the Advertiser.
- Advertiser's Postback - If the user converts, we expect to receive a postback from you letting us know the user has converted and the monetary value of said conversion. This is necessary so we can calculate your revenues as well as report the payout to your traffic source.
- Postback forward to Publisher - Once we receive a postback from you, we calculate the traffic source's payout according to what you configured in the campaign, and send a postback to your traffic source.
In each one of these 4 steps of the flow, you are expected to send some mandatory information in the URL parameters and can optionally send some other information which helps you analyze or process information on your own platform.
The following illustration shows all the different URL parameters each step of the flow can accept. Bear in mind that apart from these URL parameters, you can send any arbitrary key and value through a URL to Opticks and we will store that and be able to pass it along the flow. This is useful if you want to send something from your Traffic Source to your own platform.
The following table summarizes what URL parameters you are expected to pass through each step, and where you need to go to configure them:
The following parameters are used internally by Opticks: