I’m posting this because I’m hoping it will help other lead generators. There’s a lack of knowledge shared between lead tracking services (ie CAKE, Leadspedia, Everflow) that helps marketers track between platforms.
All of these examples use a Leadspedia Postback URL with Request IDs. In some cases, payout is included as well.
- Leadspedia Postback with CAKE
- Leadspedia Postback with Hasoffers
- Leadspedia Postback with Everflow
- Leadspedia Postback with Hitpath
Leadspedia Postback with CAKE (getCake.com)
CAKE is one of the most popular lead distribution/tracking systems in the world, and is one of the big reasons why I’m publishing this info.
Leadspedia Postback with Request ID for CAKE:
https://www.TRACKING_DOMAIN.com/pixel.do?amount=#price#&t=pb&request_id=#s2#| Leadspedia Sub IDs | CAKE Tokens |
|---|---|
| S1 | #s1# |
| S2 | #s2# |
| Payout (amount) | #price# |
Landing Page Tokens:
Landing page tokens are setup when you create an offer for the advertiser using CAKE. This is where you will set up the parameters to pass to the advertisers landing page, typically propagated in the URL of the landing page, for accurate tracking and reporting.
| Leadspedia Landing Page Token | Leadspedia Sub ID |
|---|---|
| Request ID | s2 |
| Affiliate ID | s1 |
| Campaign ID | s3 |
Leadspedia Postback with Hasoffers (Tune)
Hasoffers does provide a nice knowledge base, and their postback tracking is fairly easy to setup with a Leadspedia postback URL.
Here’s the format:
https://www.TRACKING_DOMAIN.com/pixel.do?amount={payout}&t=pb&request_id={aff_sub}| Leadspedia | Hasoffers Token |
|---|---|
| request_id | {aff_sub} |
| s2 | {aff_sub2} |
| s3 | {aff_sub3} |
| amount | {payout} |
Leadspedia Postback URL with Everflow
Everflow is another popular lead tracking/distribution system.
Leadspedia Postback with Request ID:
https://www.TRACKING_DOMAIN.com/pixel.do?amount={payout_amount}&t=pb&request_id={sub3}Tokens are fairly straightforward:
You can customize how you pass Request IDs based on the advertisers preferences. In the example above, we pass the Leadspedia request ID through sub3 in Everflow.
| Leadspedia Sub IDs | Everflow Tokens |
|---|---|
| S1 | {sub1} |
| S2 | {sub2} |
| Request ID (request_id=) | {sub3} |
| Sales Amount (amount=) | {payout_amount} |
Leadspedia Postback URL with Hitpath
This is a bit of a pain in the ass. Buckle up.
In order for Leadspedia to communicate with Hitpath properly, you will need your Hitpath administrator to update the link structure in your affiliate account.
The link structure should be “&subid” vs the “/” used out of the box.
Leadspedia Postback with Request ID:
https://www.TRACKING_DOMAIN.com/pixel.do?amount=xxPayoutxx&t=pb&request_id=xxC2xxLanding Page Tokens:
| Leadspedia Sub IDs | Hitpath Tokens |
|---|---|
| S1 | subid1 |
| S2 | subid2 |
We rarely run into Hitpath these days, so I don’t have as much of a robust library built out. Hopefully the link structure tip helps resolve most of your potential issues.
