Tealium Learning Center

LeroyPijlman · ‎11-02-2018

@dan_george Woah, I'm glad that it's possible the way I had anticipated this to work. I'm using utag loader template 4.46. I'm unable to post more details right now, I'll get back to this on monday with my setup and some steps. Thank you for your help thus so far!

LeroyPijlman · ‎10-31-2018

@dan_george Thank you for your reply! I had tried this before, but for good measure I've tried it again. I've mapped tealium_timestamp_epoch to a custom dimension. And it is sent with each event, as expected. However, the value of this timestamp is always the same. (The time at which the variable was set, not the time at which the event was triggered.) So when I load a page, each event I trigger has the same timestamp. Rather than incremnetal timestamps of at which they were fired at. Did I miss something?

LeroyPijlman · ‎10-31-2018

One of the wacky things I have tried was: Unfortunately b.UnixTime did not seem to be the correct reference to the UDO variable that I declared in my DataLayer.

LeroyPijlman · ‎10-31-2018

We send specific events to Google Analytics using gtag based on certain triggers we have set up. (Some through extensions, some through embedded Javascript throughout the website.) Because variables are set once during the loading of a tag, the timestamp always contains the time the tag was loaded. I want to send an event with a Custom dimension, containing the timestamp the event occurred. So we can analyze the order in which the events occurred. 4:00 PM - User opened page 4:01 PM - User visited an article 4:05 PM - User initiated a chat I am aware that I can just add it as custom dimension in the Javascript function/Tealium Extension where I register the event. like; gtag.event(x, y, z, custom-dimension-i-->timestamp) But it would be much easier for us to maintain by having this set up through one extension in Tealium IQ. Otherwise we would have to continuously change each event trigger function, everytime we wanted to change the way timestamps are registered. I spend a lot of time, and have attempted a lot of hacks to try and get the occurrence timestamp. But I have given up. There has to be an easier way. I hope someone here can assist me. Cheers, Leroy

LeroyPijlman · ‎06-07-2018

Thank you for your positive feedback @kathleen_jo! @jason_paddock I learned a lot from this article, thank you. I followed the instructions ... and ... The id is consistent between all the domains now! However - one strange thing I do want to point out is; In my current scenario, if I follow the following path; Domain A -> Domain B -> Domain C Where domain A and C are within the same parent domain and B is not. The debugger shows the same id across all these hops. However, _ga is not appended in the url of Domain B. But when hopping from B to C, _ga IS appended in the url. Note; B is opened through an 'iframe'. Could this be the cause? I'm strictly asking this out of curiosity - the original issue is now resolved, as I can track users across different domains within a session. Thank you kindly. :)

LeroyPijlman · ‎06-05-2018

@mitchelltLast night I learned about 'gtag.js', as opposed to 'analytics.js'. I completely gave up and decided to migrate to gtag. Upgrading seems to have worked, and the warning message no longer appears. The only issue I'm facing, is that one of the domains that does not fall under the same parent domain is not properly being 'cross-domain-tracked'. But the second link you just posted seems to answer this! I'm going to try this out and report back. Though my initial problem is now solved. Thank you a lot for your input @mitchellt! :) edit: gtag does not appear to have the 'domain' field for specifying domains that have a different top level domain. Do you happen to know how I can configure CDT in this scenario in gtag?

LeroyPijlman · ‎06-05-2018

@mitchellt Thank you for your reply. My tag was actually out of date. I was not familiar with the tag status checker yet, but I read up on it just now, and managed to update it. Unfortunately did this not solve the problem.

LeroyPijlman · ‎06-05-2018

Hello, We're having issues setting up Crossdomain tracking in our Google Analytics tags. We've consulted numerous threads and ofcourse the documentation, but the '_ga' is not appended to any of the cross domain addresses. - Cross domain tracking is set to On - The domains are comma separated and do contain any spaces - The domains are all subdomains of one parent domain I do want to point out one thing I spotted while I was trying to debug this using the "Google Analytics debugger" chrome extension. It returns the warning message; "Expected a boolean value for the field "allowLinker". But found "string"". I do know that the variable allowLinker is related to the GA cross domain tracking. Could this be breaking it, and how can I resolve this? Any help is greatly appreciated.

Date Registered	‎01-16-2018 01:47 AM
Date Last Visited	‎03-06-2019 07:11 AM
Total Messages Posted	10
Total Kudos Received	4

Tealium Learning Center

Re: Send timestamp of event occurrence with JS Ext...

Re: Send timestamp of event occurrence with JS Ext...

Re: Send timestamp of event occurrence with JS Ext...

Send timestamp of event occurrence with JS Extensi...

Re: Google Analytics Crossdomain tracking

Re: Google Analytics Crossdomain tracking

Re: Google Analytics Crossdomain tracking

Google Analytics Crossdomain tracking

Products

Company