This article will cover:
- What Does Standardizing Events Mean?
- How To Set An Event Third Party Name
- Example Of Standardizing Events Across Multiple Advertisers
- What Is The Event Third Party Name (en=) Parameter?
- Example Postback With Event Third Party Name Parameter
What Does Standardizing Events Mean?
When you work with multiple Advertisers in similar industries, you may notice that they tend to track the same user actions across their funnels (even though they may use slightly different naming conventions). Standardizing events is the process of creating a single set of events with the same third party names for each Advertiser in your CAKE account. This creates uniformity in reporting and allows you to measure the same KPIs across your Advertisers.
How To Set An Event Third Party Name
When you first create an event, you are required to specify a name and optionally specify a third party name. Click here for more details on how to create events. Otherwise, to add a third party name to an existing event, follow these steps:
- Navigate to the Advertiser Card
- Click the Events Tab
- Click on the Third Party Event Name field
- Add a new name
- click save
Example Of Standardizing Events Across Multiple Advertisers
Use the same exact event third party name, including capitalization, on each Advertiser card.
In the image above, the first Advertiser has event ID 9 as their Upsell and the second Advertiser has event ID 11 as their upsell. Since both use the same exact name of "Upsell" CAKE can properly attribute to each of their events, regardless of the ID, so long as the Advertiser uses the en= parameter.
What Is The Event Third Party Name (en=) Parameter?
The event third party name parameter (en=) is a new parameter that is recommended once you've standardized your events in CAKE. This parameter can be substituted for the standard event ID parameter (e=) on the CAKE postback. Advertisers will pass the event third party name instead of the event ID for CAKE to know which event took place. The added benefit is that your Advertiser now only needs 1 postback structure per Offer.
Example Postback With Event Third Party Name Parameter
Can I create one postback structure that works across all my Advertisers and all their events?
Yes, by combining a Dynamic Offer Postback with the Event Third Party Name parameter, you can create a global advertiser postback.
You may also be interested in:
How to Manage Event Visibility in the Affiliate Portal Using Publish Events