Panel | ||||||
---|---|---|---|---|---|---|
Table of Contents
|
Introduction
Our most successful advertisers use the post back URL to track conversions in our platform. Once you add in our click ID macro, you will have the insight to be able to optimize your campaign by traffic source.
Info |
---|
Please Note: Postback conversions must be fired within 2 weeks of the click, otherwise they will be ignored. |
Before installing your postback URL, you'll need to edit your tracking URL. When you edit your tracking URL, append our {clickid} macro using the parameter that your affiliate company's receiving ad server accepts. When a user lands on your URL, SourceKnowledge will replace the {clickid} macro in your URL with the actual click ID value.
This implementation assumes the following:
- Attribution is done through the tracking system of the advertiser or affiliate.
- For every postback URL fired, a conversion is counted.
- Our system will only discard duplicate fires if "order IDs" were provided with every pixel fire.
Tracking Url Instructions
You will need to add our {clickid}
macro to your click tracker, so that we can pass you our click id.
If your tracking url currently looks like this:
Code Block |
---|
https://example.com/?oid=344532083&pid=4269944841 |
and if your click id parameter is called clkid
, then you'd end up with the following:
Code Block |
---|
https://example.com/?oid=344532083&pid=4269944841&clkid={clickid} |
Info |
---|
|
Postback Url Instructions
SoureKnowledge's Postback URL looks like this:
Code Block |
---|
https://upx.provenpixel.com/postback.php?clk=CLICK_ID |
Info |
---|
The only change required is to replace |
We also strongly recommend adding more parameters to help you see more stats in our dashboard, for example to provide order amount/value, order ID and/or unique user ID, you can do the following:
Code Block |
---|
https://upx.provenpixel.com/postback.php?clk=CLICK_ID&order_amount=ORDER_AMOUNT&order_id=ORDER_ID&uid=USER_ID |
Info |
---|
Everything that is in all caps, such as |
Optional: Firing multiple event types for the same campaign
If we want to fire multiple event types for the same campaign (e.g. leads, sales, etc), then the tracker ID should be added to the URL. Just like our regular pixels. To do that, the ID should be added using the "upx" parameter as follows:
Code Block |
---|
https://upx.provenpixel.com/postback.php?upx=UPX_ID&clk=CLICK_ID |
Info |
---|
URLs with the tracker ID included will use that tracker ID directly. If the tracker ID is not included in the URL, then the ID to be used would default to the sales/conversion pixel mapped to that campaign. |
Response
With every pixel fire, a JSON response is returned letting you know whether your request was processed successfully or not. You must always check that response to make sure that any error is caught early on.
When contacting our team, please provide the error message you receive in the response.
Tracking clickId (clickData, clk parameter)The clickId is built by the delivery system. It's part of the ad-click delivery process. The value is encrypted and contains all necessary information for identification / lookup the ad-event.
Example, format explained:
clickId passed to 3rd party
Code Block | ||
---|---|---|
| ||
clk=c6jt8RiyE/twzZJiPQIOq1jm/cljUz7tIJdGmZ51Uzbw2W3fGGdzfBhkvgRWI048wjo7neZ/dJKstH92+IXo23Ia87EEAwQ5b77 |
clickId decrypted
Code Block | ||
---|---|---|
| ||
echo "c6jt8RiyE/twzZJiPQIOq1jm/cljUz7tIJdGmZ51Uzbw2W3fGGdzfBhkvgRWI048wjo7neZ/dJKstH92+IXo23Ia87EEAwQ5b77" | ~projx/local/logutil/decrypt.php
a99080;z7795;pv-3482292;b657b2f69-3cae-43c3-be83-cc6df52c79db072 |
clickId includes
\ \ \ \_ b657b... = "b<bidId>", unique ad-click identifier bidId
\ \ \_ pv-34822... is "p<pid3>", pid3 or publisher subId
\ \_ z7795 is "z<zoneId>", publisher zone Id
\_ a99080 is "a<adId>", ad Id
Where bidId
b657b2f69-3cae-43c3-be83-cc6df52c79db072
\ \ \ \ \ \_ 072 is ad-server code
\ \ \ \ \_ random
\ \ \ \ _ random
\ \ \_ random
\ \ _ random
\_ 657b2f69 = 2023-12-14 16:38:01 timestamp