Tealium Learning Center

Here is what we did, whcih seems to have resolved the issue: We created a data layer variable called "unique_order_id" We created a cookie variable called "previous_order_id" We created an extension to persist any incoming value in "purchase_id" (our existing variable for order ID) into the cookie, whenever it is populated and on the order confirmation page. We created another extension, with a condition that the already existing variable "purchase_id" is populated, to set the value of the unique_order_id to an empty string if it's the same as the cookied value of "previous_order_id", otherwise it sets it to the value of the "purchase_id". See code example below We changed the Ecommerce extension mapping to map only the "unique_order_id" to the order ID, which is what is subsequently mapped into the GA tag and whcih triggers the purchase event Here is the example of code from the extension to set the unique_order_id: // Set unique order id to empty string if order is same as previous cookied order id if (b.purchase_id){ b.unique_order_id = b.purchase_id; if(b.purchase_id === b['cp.previous_order_id']){ b.unique_order_id = ""; } else { b.unique_order_id = b.purchase_id; } } ... View more

To use this, you map from a data layer variable which contains one of several possible trigger values, and for each value you type the value in the input field called "trigger" and you select the appropriate event from the dropdown. In the example screenshot below, you'll see 3 different trigger values mapped. Tealium concatenates the two fields for each. So, for example, the first one has a trigger value of "productClick", and a dropdown selection of "product_click". And the second one has a trigger value of "productRemove" and a dropdown selection of "remove". In each case, the field containing the trigger value is "event_type" in my example (but can be any field you want. Of course, you need to also to put the trigger values into the data layer variable. So, you might do this directly in your application (when the event occurs) or else through an extension. Either way, you're just putting a value into the variable whcih later you'll use in the mapping as the "trigger" for one of several events. In the example below, the value in the data layer variable "event_type" has been populated by the application whenever the event occurs (in a utag.link function call). And finally, you'll want to make sure you're using the e-commerce extension (or else overriding all the standard mapping for e-commerce variables) so that the related data is also set. And in your utag_link calls (or in your extension) you need to supply the other e-commerce variable values like product ID, quantity, etc.   ... View more

@GavinAttard Thanks. So, now the part of this where I'm having difficulty is setting a condition on the extension to check whether one variable equals another variable. I can choose  avariable as the first part of a condition, but then after the expression like "equals" or "does not equal", it does not let me choose another variable. Only to enter a text value. How does one compare two variables in an extension condition? I'm trying to implement the condition in the "set data values" extension" to only set the is_order when the current order ID does not equal the one in the cookie. So, I need to compare two variables in this case. ... View more

@GavinAttard Thank you very much for the detailed instructions. These are very helpful. I do have one follow-up about where you wrote " Finally map the is_order to the GA order action to trigger on true". We are using Tealium's standard GA tag. And in this tag, there is logic built into its template to create the order action based on the presence of a value in the order_id field. So, we don't have any explicit extension or tag to fire the order event, but rather the Tealium tag does it by itself, based on whether there is an order_id or not.  I've pasted the relevant section fro the standard Tealium GA tag below, whcih controls whether the order action occurs. If I am following you, then what we would need to do is to customize this tag, by adding another IF, so that in addition to the presence of the u.data.order_id field, it also requires that is_order = true. Is that correct? Or is there a way to do this without customizing the tag template? Here is the relevant section from the standard tag template: //ENH: ORDER start else if (u.data.order_id) { if (u.data.order_id instanceof Array && u.data.order_id.length > 0) { u.data.order_id = u.data.order_id[0]; } u.addproduct("product_purchase", u.data.product_id.length, false); g = {}; g.id = u.data.order_id; g.affiliation = (u.data.affiliation ? u.data.affiliation : u.data.order_store); g.revenue = (u.data.revenue ? u.data.revenue : u.data.order_total); g.shipping = (u.data.shipping ? u.data.shipping : u.data.order_shipping); g.tax = (u.data.tax ? u.data.tax : u.data.order_tax); g.coupon = (u.data.coupon ? u.data.coupon : u.data.order_coupon_code); u.setHitData(g, "enhecom_events", "purchase"); u.all('ec:setAction', 'purchase', g); // ENH: ORDER end ... View more

@GavinAttard , after several attempts to solve this in our application and with Tealium, I believe I need some help here. I see quite a few posts on the internet on how to do this with Google Tag Manager, using a callback function of the GA tag. But I haven't been able to successfully translate those into how to do it with Tealium.  I do understand that the basic steps (copied from a post on Google Tag Manager method) are:  Create a user defined variable to extract the transaction id from the dataLayer Create a user defined variable to save the transaction id in a 1st party cookie Create a user defined variable to retrieve the contents of the 1st party cookie Create a user defined variable to check if the current transaction is already stored Update the event trigger [not sure of TiQ equivalent, since it is simply based on presence of a transaction ID in the e-commerce extension) for the GA Enhanced Ecommerce Purchase tag to stop it triggering if the current transaction id is in the cookie Update the GA Enhanced Ecommerce Purchase tag to ensure the transaction id is saved to the cookie. Would you be able to outline specifically how to make this work with the standard Tealium GA tag (we are using the "legacy" analytics.js tag). ... View more

Have you resolved this issue using Tealium? I see this is an issue that has some documented solutions in Google Tag Manager and also using server-side measurement protocol. But, if you've managed to solve this in TiQ, it would be very appreciated if you would share the solution. ... View more

Thanks! ... View more

Tony - also the Optimizely Events Connector link is a playground one too. Looking forward to checking that one out when available. ... View more

Update. Tealium Support was able to provide an interim solution using a javascript extension, very specific to our unique implementation, until this is addressed in a future product update. The javascript extension creates a new cookie, to keep track of whether users have visited our EU sites or not in the past, and then conditionally removes the CONSENTMGR cookie under certain circumstances. This ensures that visitors who access our non-EU sites don't get automatically opted-in when they go back to visiting one of our EU sites. This interim solution was very specific to our implementation, but hads addressed the problem for us now. ... View more

A quick update, for anyone else who may be having this same issue. Tealium support confirmed that indeed, Tealium adds a cookie with a consent value of TRUE whenever the load rules for the consent manager are not met. So, in our case, we are using load rules to only use the consent manager in the EU. But the cookie is being stored with consent of TRUE in the US, when the load rule of region=EU is not met. We are still working with Tealium support to identify resolution, and I will post here once resolved. In the interim, I would appreciate any create workarounds from the community. ... View more

We had a similar requirement around IP anonymization, @fedor_goossens, which is also a setting in the GA tag. In our case, we decided to clone the tag, with one version havig the setting on, and the other version with it off. And then we used a country-specific load rule to determine which tag to fire. So, we didn't base it on the consent prompt, strictly speaking, but the IP anonmized version we felt safe to omit from the consent prompt because we had also ensured we are not collecting PII into GA. And the non-anonimized version we load for our non-EU-based properties. So, this doesn't totally meet your requirement, because we do not load a different version if the consent prompt is accepted, but rather we just have one version we feel does not require consent. ... View more