There are a few different areas that you can place a pixel from your traffic source. We'll take a look into each of those below. We'll also go through some additional information that should help when setting up your postback or pixel.
Placing The Postback or Pixel on the Traffic Source Level
You can place your pixel or postback url to fire across the entire traffic source, by going into your traffic source in Thrive and placing it in the Pixel field in the below screenshot.
Please make sure to choose the corresponding pixel type in the right hand dropdown menu. We can accept Postback url, Iframe, Image, Javascript or Raw Code (great for Facebook pixels).
Important to note: If choosing to use a format other than Postback url, you will need to be set up with your Thrive iframe pixel on the offer level. If you are set up with a Thrive postback url on the offer, only 3rd party postback urls will fire.
We also provide you with a few tokens that you can use in your postback/pixel.
- {externalid} - This is required for postbacks. This will pass the unique external ID that is needed to fire the postback.
- {subid} - Allows you to pass your traffic source the unique subID for each conversion.
- {cost} - Passes back the cost to your source.
- {amount} - Passes back the conversion amount to your source.
- {var:param-name} - Can pass back specific variables of a traffic source by parameter name. Just replace "param-name" with the actual parameter.
- Example: {var:target}
Placing The Postback or Pixel on the Campaign Level
Want to fire your traffic source pixel on a specific campaign only? Not a problem.
Any pixel you place here will fire the postback/pixel on this campaign level only.
Please make sure to choose the corresponding pixel type in the right hand dropdown menu. We can accept Postback, Iframe, Image, Javascript or Raw Code (great for Facebook pixels).
Important to note: If choosing to use a format other than Postback, you will need to be set up with your Thrive iframe pixel on the offer level. If you are set up with postback on the offer, only 3rd party postback urls will fire.
You have the below tokens also available for use:
- {externalid} - This is required for postback urls. This will pass the unique external ID that is needed to fire the postback.
- {subid} - Allows you to pass your traffic source the unique subID for each conversion.
- {cost} - Passes back the cost to your source.
- {amount} - Passes back the conversion amount to your source.
- {var:param-name} - Can pass back specific variables of a traffic source by parameter name. Just replace "param-name" with the actual parameter.
- Example: {var:target}
If placing the pixel while setting up a new campaign:
If you are setting up a fresh campaign, once inside "Create Campaign", scroll down on the General Information tab to the Pixels section.
If placing the pixel on an existing campaign:
Inside of the general information tab of your campaign, find the Postback section and click the Edit icon.
Placing The Postback or Pixel on the Global Level
You can also place your 3rd party pixel on the Global Level. This will fire the 3rd party postback/pixel every time your Thrive pixel is fired. This can be set up under the Tracking Section --> Pixels & Postbacks --> Additional 3rd Party Post-Back pixels.
Please make sure to choose the corresponding pixel type in the right hand dropdown menu. We can accept Postback, Iframe, Image, Javascript or Raw Code (great for Facebook pixels).
Important to note: If choosing to use a format other than Postback, you will need to be set up with your Thrive iframe pixel on the offer level. If you are set up with postback on the offer, only 3rd party postback urls will fire.
You have the below tokens also available for use:
- {externalid} - This is required for postback urls. This will pass the unique external ID that is needed to fire the postback.
- {subid} - Allows you to pass your traffic source the unique subID for each conversion.
- {cost} - Passes back the cost to your source.
- {amount} - Passes back the conversion amount to your source.
- {var:param-name} - Can pass back specific variables of a traffic source by parameter name. Just replace "param-name" with the actual parameter.
- Example: {var:target}
Now that I have my pixel placed, do I need to do anything specific with my campaign URL?
If you are using a postback with your traffic source, it's important that you have the External ID appended to your campaign URL. The reason for this is that postback urls are server based and rely on the External ID to be placed in BOTH the postback and the URL in order to properly fire.
Let's look at an example.
Say our Traffic Source is Adcash.
We are given this pixel from them, that we place inside of our traffic source in Thrive:
http://win.crwd.io/convert/{externalid}
Notice how we appended {externalid} to the postback.
Now we need to make sure we also pass this through to our campaign URL. To do so, scroll down to the parameter section and you can see we have an External ID row with the Parameter, Placeholder, and Name.
If you are choosing a pre-defined source, these will prepopulate in for you. If setting up a unique source, you will need to get the specific placeholder from your traffic source (this token MUST come from the traffic source themselves). The parameter can be anything you wish. The Name column is how this will show up in reports.
You can see in this case, the Adcash template uses:
&extid={{{bidhash}}}
Go ahead and "Add New Source". You will then go into your campaign and select Adcash as the traffic source, which will automatically add this parameter and token/placeholder to your campaign URL.
Our campaign URL will show up as this once assigned to Adcash as the Traffic Source:
https://demo.thrivetracker.com/path/lp.php?trvid=10192&trvx=e6ccd704&extid={{{bidhash}}}
If you have any questions on set up or need assistance, please contact Support anytime and we would be happy to help you out.
Comments
0 comments
Please sign in to leave a comment.