How to pass google analytics custom metrics using Tealium data layer from page. As per my understaing this should also pass with utag_data or utag.link/view
metric1: "1" // defined as Integer - counter of 1 with every page load or event
metric2: "20.1" // defined as currency
Hi @ani2012. I was wondering the same thing. I found this post in search.
Hope it helps.
With the example you have posted, you would simply need to map "metric1" to metric 1 and "metric2" to metric2 using the mapping toolbox in the tag.
Here's a brief explanation of the different "scope" options available when you use the GA mapping toolsbox:
I hope this helps.
How to pass custom dimensions with Google Analytics Event (click/mousedown). All custom dimension already available under utag_data with load page. Do i still need to pass those dimensions with click event in code or only map those dimensions with event type "link" in Tealium?
i setup a product idea, it's easier to track progress on those. I have given updates to be made in the past and they have been acted upon.
Suggest you vote up and if we can get others to do so, it will raise the urgency.
Wondering if there is another solution to this in the mean time. a way to trick it into sending a an updated set command...
OK, so after reverting a few versions and armed with the knowledge of what each event type actually reflects i can state as follows:
If you use the optional naming in 'All hits' it will work for the link, but wont work for all pages
So - you need to not use the optional naming at all for it to work in all circumstance.
This means i didn't have to go through and re-map all my custom dimension or metric vars and have double setting for view and link instead of the 'All hits' . From an implemenation point it works, however documentation still needs to be updated and will try and get a fresh post up to sign post this.
well thanks, but this is a bug or a glaring error in the documentation or lack of consistency.
Should we raise product ideas for typos as well?
Thanks for your feedback. The mapping options can be confusing and we are now reviewing the documents. In the future, you can submit documentation feedback using the feedback form at the bottom of each documentation page: