- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
01-14-2014 08:03 AM
01-14-2014 08:06 AM - last edited on 12-04-2015 10:43 AM by kathleen_jo
There is a post on this - worked like a charm for me.
01-14-2014 08:11 AM
01-14-2014 09:24 AM - last edited on 12-04-2015 10:45 AM by kathleen_jo
I have a further question about this.
The link above mentioned the data that would be captured, but it doesn't seem like the variables listed in the code to capture these items match up in sequence. Is the following correct?
* get visit number = _visit_number ??
* get new repeat = _visit_type ??
* get visit start = _visit_start ??
* get action depth = _visit_page_num ??
* days since last visit = _visit_return ??
01-14-2014 10:13 AM
01-14-2014 11:01 AM
01-14-2014 11:19 AM - last edited on 12-04-2015 10:45 AM by kathleen_jo
Not really sure. I would look to the Tealium folks on this.
Do you have any other extensions running that would be collecting it?
In our case - we had some custom plugins from Omniture in some of our Tealium extensions from our initial implementation that would have otherwise been included in our s_code. These extensions were collecting our visit details.
With the recent visits details extension we were able to replace that. I don't recall the visits number ever populating on its own.
08-28-2019 04:55 AM
This post helped me even today and was just implemented to check the functionality. Few stuff are workign fine as mentioned and two data layer (Variables ) are not capturing data.
Therefore, what could it cause to fire the above mentioned variable. Was trying to change all stuff and still I dont see the respective data.
Could you please assit me to fire the above mentioned visits for us. Thanks much!
Copyright All Rights Reserved © 2008-2023