Enhanced Ecommerce Checkout Funnel Implementation

[crystal_ashby]

Does anyone have any advice on how to setup the "Measuring the Checkout Funnel" thru Tealium-implemented GUA for enhanced ecommerce? Ecommerce extension does not map the checkout funnel? How to use the ec:add mapped source in the tag? https://developers.google.com/analytics/devguides/collection/analyticsjs/enhanced-ecommerce#checkout...

[Seth]

Hey Crystal, As best as I understand it, the feature you linked to is a front-end configuration for Google Universal Analytics reports that allows you to give custom names to the steps in your checkout funnel; it doesn't require any code changes or configurations in Tealium iQ. The E-Commerce extension automatically sends product data through. Are you not seeing product data associated with the checkout come through to your report?

[nicholas_dureau]

I'm still unsure how to have it fire using tealium. I know I need these to define the enhanced ecommerce funnel but I'm completely in the dark on what I need to do to make it fire using an extension or something???

If so, which?

----------------

ga('ec:setAction','checkout', {'step': 1})

and

ga('ec:setAction','checkout', {'step': 2})

etc....

[Seth]

You should be able to find what you need in order to use GUA's Enhanced E-Commerce through Tealium iQ in this article Google-Universal-Analytics-Tag-Enhanced-E-Commerce

Essentially you need a data source that identifies which checkout step the visitor is on. You also need to make sure that the data source is mapped to Checkout Step (enh_checkout_step) in the Tag's configuration. Keep in mind this values needs to be a number (1, 2, etc.). Whenever a checkout action occurs, the checkout step value will get passed to your GUA report along with the other data points mentioned in the article.

Let me know if you have additional questions.

Thanks,

Seth

[nicholas_dureau]

I have unique objects to define, but what you're saying is that have to have something with numbers in it like if I defined a new UDO variable (something else to include in onboarding???):

First Step - 'var1': '1'

Second Step - 'var1': '2'

Third Step - 'var1': '3'

etc....

and map it out to (enh_checkout_step), which will fire the below for me on each step?

First Step - ga('ec:setAction','checkout', {'step': 1})

Second Step - ga('ec:setAction','checkout', {'step': 2})

Third Step - ga('ec:setAction','checkout', {'step': 3})

Please clarify if I've got this wrong or is there another way?

[Seth]

If you don't already have a data source that identifies the step, then you do have to add it to your UDO. I you're not able to alter your page source code, you could set up a data source for this purpose through an extension. I'd recommend talking to your Account Manager for help with this.

It looks to me like you understand what's needed for a checkout step, but just populating the checkout step is not enough to fire a checkout event.

An enhanced e-commerce event can be fired by mapping the E-Commerce Action (enh_action) destination with a data source that contains the appropriate value (For a checkout event, this value is 'checkout'). When an event fires it sends a set of data to GUA. What data is sent depends on the event fired. The data sent for each event is listed in the article I linked above. The checkout step is one of the pieces of data sent with the checkout event. The tag template we've created for integrating with GUA essentially runs this code for you. You just have to make sure the proper data is mapped.

As for the checkout step requiring a number, that's a requirement of Google's. Your checkout steps won't show up properly otherwise.

[nicholas_dureau]

Not to be flippant, but I just need an solution... not vagueness.

My Problem Is:

I do not have a proper variable that the Google ecommerce plugin will like on my pages so...

My Proposed Solution Is:

1) Define a new DATA LAYER var called "OSP_Checkout_Step1" (this won't be included in the on-page UDO) - also what type should I use (UDO var (or) JavaScript var?).

2) Create a new 'SET DATA VALUES' extention using "OSP_Checkout_Step1" and transform it to "JS Code" using: ga('ec:setAction','checkout', {'step': 1})

3) Use a CONDITION based on dom.url (or some other UNIQUE ELEMENT to that 'step one' page) to load the extension.

----------------------

Will this work? If not, why? Is there a better solution?

----------------------

PS, we also use Webtrends and I would like to do the same with this code:

<meta name="WT.si_n"

content="OSP_Sponsorship;SponsorshipCheckoutFunnel" />

<meta name="WT.si_x" content="1;1" />

<meta name="WT.si_p" content="ChildSelection;ChildSelection" />

Normally this is supposed to be on page but I'm guessing I can probably define a data object called "WT.si_n" and pass along as text "OSP_Sponsorship;SponsorshipCheckoutFunnel"

[Seth]

You don't need to set the var that identifies the checkout step to any code at all. Since adding the var directly to your UDO is not an option, you can set this var using the Set Data Value extension. Create OSP_Checkout_Step as a UDO variable, and set it to "1". Map this data source to Checkout Step (enh_checkout_step) in the mapping for Google Universal Analytics. I don't have experience with Webtrends, so I can't help you there. We'll reach out to you for a working session, and hopefully address all of your questions and concerns directly.

[Michael_Kim_shc]

Hi @nicholas_dureau- was this ever resolved for you?  I'm having similar trouble.  We've got a data layer object that we're setting using a set values extension to hold a number (1,2,3, etc).

We' mapping that to the enh_checkout_step value in the GA tag - but nothing comes through on the GA event call when we're browsing!

This is frustrating.

[GavinAttard]

HI All

not sure if this is still an issue, but dealing with the problem at the moment in our implementation.

Here is what i did:

1) Created lookup table to match on page name and then populate a var call ga_checkout_step with the corresponding step value (1, 2, etc...)
2) In the mapping i then mapped the page name to trigger the checkout, when those pages are loaded.

W Hat i am not 100% sure about, is whether need to send the cart product data with each step or not. The google implementation seems to insinuate it does, but its not explicit...

[craig_rouse]

@GavinAttard @Michael_Kim_shc please take a look at this document: https://community.tealiumiq.com/t5/Tags/Google-Universal-Analytics-Tag-Enhanced-E-Commerce/ta-p/279#...

To send checkout steps (required for the funnel), you need to set "enh_action" to "checkout" and then pass supplemental cart info. The documentation has examples of what you could send. This will automatically send the commands in the format required by Google Analytics. Let me know if you have any issues setting it up.