This article will cover:
- Requirements For Integration
- How To Integrate CAKE To An Advertiser On Everflow
- How To Integrate An Affiliate On Everflow to CAKE
Requirements For Integration
There are two primary pieces to create a tracking integration between CAKE and a 3rd party attribution platform. These two pieces allow you to track clicks and conversions in real-time.
The first item is a tracking link and the second is a Postback URL, which facilitates server-to-server tracking.
If you are the affiliate, you will be receiving a tracking link and providing the CAKE Postback URL to your advertiser.
If you are the advertiser, you will be receiving a postback URL and providing a tracking link to your affiliate.
How To Integrate CAKE To An Advertiser On Everflow
As the affiliate in this situation, you will need your advertiser's tracking link. This is also referred to as the redirect link.
This link will be configured within the Offer as the Landing Page within CAKE.
Before you place the Everflow tracking link, it will need to be configured to include CAKE's session ID token.
Everflow provides 5 Sub ID parameters for their affiliates to use. In the example above, we used sub1. You can choose to use Sub1, Sub2, Sub3, Sub4 or Sub 5.
Before the CAKE postback can be placed in Everflow, update it to include the appropriate Everflow Sub ID token.
How To Integrate An Affiliate On Everflow to CAKE
As the advertiser in this situation, you will need to provide a tracking link and request a Postback URL from your affiliate.
Before the CAKE tracking link can be placed as the landing page in Everflow, update it to include Everflow's transaction ID token.
Before the Everflow postback can be placed in CAKE, update it to include CAKE's s2 token.
To place the affiliate's postback URL within CAKE, follow these steps:
- Open the affiliate's Campaign Card
- Within the Home Tab, click the Pixels tab
- Paste the Postback URL into the Postback URL field
- Click Save
CAKE has five open parameters in it's tracking link structure which are s1-s5. The s1= parameter is strictly reserved for SubAffiliate IDs and should never be used when passing HasOffer's transaction id to CAKE. Alternatively, s2=, s3=, s4= or s5= can be used along with it's corresponding token of #s2#, #s3#,#s4#, or #s5# respectively.
Is CAKE's Transaction ID the same thing as Everflow's transaction id?
No, CAKE's Transaction ID (t=) is an optional parameter for the postback url that can be used by your Advertiser when they want to pass their own conversion identifier back to CAKE. Ev's Transaction ID is their uniuqe click ID value that is needed for their postback url to have attribution. It is essentially the same as CAKE's request session ID.