Submit a Ticket My Tickets
Welcome
Login  Sign up

Understanding the CAKE Transaction ID

This article will cover the following:


- What is the Transaction ID?


- Where does the Transaction ID show up in CAKE?


- What else the Transaction ID is used for


What is the Transaction ID?


As outlined in the Conversion Pixel Variables doc, the Transaction ID parameter in the pixel is your advertiser's opportunity to pass a unique value associated to the Conversion or Event to CAKE so that you can audit your conversions against theirs.


So if you recorded 10 Conversions, and your Advertiser recorded 8 - you could pinpoint which 2 conversions account for the discrepancy based on matching up our Transaction IDs with your Advertiser's reports.


Where does the Transaction ID show up in CAKE?


Reports > Conversions:


If you received this pixel from your Advertiser: http://demotrk.cakemarketing.com/p.ashx?o=1001083&t=a1b2c3


The a1b2c3 value displays in the conversion report under the "Transaction ID" column


Conversion Card


Conversion card > Home tab > Sale Info subtab:


The Conversion card would register that value as the Transaction ID.


Searching for Transaction ID


Search box:


If you know your Transaction ID, you can use the CAKE search box and the Transaction ID will be found under 'Conversions'.


What else is the Transaction ID used for?


Offer card > Home tab > Attribution subtab:

The Transaction ID can help you to limit unintended conversions by allowing you to dedupe conversions based on that value. However, this only works if the Transaction ID value is unique to that Conversion/Event

This is particularly important if you are allowing Duplicates on the Event (Advertiser Card > Events tab > select Event > Allow Duplicates), as if we receive the pixel twice we would add it in to the system twice. You may want allow Duplicates if the same user is, for instance, allowed to purchase multiple items or submit multiple leads.

However, once you allow Duplicates, the risk is that we would receive the same Conversion pixel twice. Receiving unintended duplicate Events is common where the Conversion Pixel is placed on a web page and that web page is reloaded by the user. So, we can dedupe on the Transaction ID instead. 


From the Offer Card > Home tab> Attribution tab, there is a setting to enable Transaction ID-based deduplication.


Note that this will not work if the passed value is the default "TRANSACTION_ID" value



Enabling this setting will also create another drop-down for enabling that deduplication setting advertiser-wide across all offers for that advertiser.


For this to work 2 ways (every offer dedupes across all other offers) it must be enabled across all relevant offers. Otherwise, it will only apply to the offer(s) the setting is enabled on.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.