03-10-2016 08:14 AM - last edited on 03-10-2016 09:34 AM by kathleen_jo
Hello @vicente_peris. We use a web-standard session. A session comprises a series of actions taken on a website where there is not a gap of more than 30 minutes between any two actions. The session ends when more than 30 minutes of inactivity has occurred since the last action taken by the user.'
I would look at the 'condition' you set in the extension. Is that condition met on the first page on your return? Anytime the condition is met, the cookie will be placed.
Just to expand on @robert_sabec answer, modern browsers these days also try to be "helpful" and persist session defined cookies. Hence it is always best to define a time frame as to the expiration period.
In the utag.js file we use the defined session time out stored in
This is defaulted to 30 mins, or what has been set in the publish settings in TiQ.
What you can do set the duration to "hours" and set the value to "0.5" which will explicitly define the cookie to be killed after 30 mins.
Hi @robert_sabec and @adrian_browning,
Thank you for your response.
I have the cookie configuration as default: 1800000.
But the behaviour is odd.
After the cookie is created, I have deactivated the extensions which are saving the cookie and if I close the tab with my site and open it a new one, after more than one hour, the cookie exist yet. I check it in the resource console.
Before close the tab I checked if the new version of my environment, with the extensions deactivated, is ready.
What i'm doing wrong?
So the utag_main cookie itself has a life of a year. Which means it and the contents will be present for up to a year if the user never revisits.
Above we have an example utag_main cookie. You will see that some of the items have ";exp-session" these, are limited to the session timeout value. This is got from the property "_st", set initially from the utag.cfg.session_timeout value. These values will be removed, once the utag has updated the contents at some point. However, you may see them in the cookie, but they will not be passed to the utag, as they have been deemed to be expired.
This is the process I'm following.
When the user do login on site, the value in the login variable from the utag_data is "logado".
I have a persist extension for the login value when its value is different than "no logado".
Then I check the cookie in the resources console.
After this, I deactivate the extension and I close the site more than one hour.
But the cookie does not disappear.
I can see the utag_main cookie in Resources, but I don't understand the relationship with my cookie.
Your images haven't come through I'm afraid.
I think what would be best at this point is if you could either email myself, or one of my colleagues at firstname.lastname@example.org or raise a case at https://community.tealiumiq.com/t5/custom/page/page-id/support-contact-form.
That way we can setup a GoTo meeting and walk through your specfic issue.