Has anyone encountered problems of heavy caching when using the Tealium Profile Loader to load another profile? I have found that the sub profiles do not expire/update as quickly as when working with the profile directly. Can this be overcome using any Publish Settings (Session Timeout) or debug settings in browser (Firebug, Chrome Dev Tools, Fiddler, etc)?
We experienced caching issues in general, and often had to wait up to 5 minutes for the next uncached version. This was unacceptable for development. Jared gave us a tip of adding a cachebuster parameter to the main Tealium js call. After that, we always got a new version each page request. It was a great solution. You could try the same
Use params with caution when cache busting. There are alternatives that might be safer/reliable as described by Steve Souders (http://www.stevesouders.com/blog/2008/08/23/revving-filenames-dont-use-querystring/) - somewhat dated, but I think the suggestion still applies.
If you only use querystrings in development than it shouldn't be an issue, but if it's meant for production as well, I'd suggest alternatives, like versioning.
And I've heard too that Tealium sets a 5-minute cache expires, so that's where that wait comes from.
Sam, utag.js does have a 5 min TTL on our CDNs. From the end user perspective (your browser) 5 minutes is the maximum amount of time that you'd have to wait for an updated file but it often occurs more quickly.
The sub profile loader had a bug where the query string (cache busting timestamp of the published date) of the sub profiles didn't get refreshed if changes only specific to a tag (in the sub profile) were made.
I think this is the same solution that Robert is describing.
Simon, you are correct that the bug has been fixed. The problem was caused by the parent profile requesting a version of the sub profile with a cache buster param. When we published the sub profile, it updated the file on the CDN, but they retained the old version with the specific cache buster on it. That's resolved now, so it's not necessary to republish the parent profile any more.
Your browser settings also affect this. Although we have a max 5 mins time-to-live, it usually takes no more than 1 or 2 minutes maximum for the updated file to hit the CDN. If you routinely see the file not updating for 5 mins or more, then it's worth changing the "check for new versions of file" setting to Always rather than Automatically.
One year later - same problem?
I see a utv parameter attached to the subloaded profile. This does not get updated. The version I get is one from yesterday were there were some deployments today, which are more than 1hour old. So still some caching issues here.
Any ideas, why this happens and how to resolve it?
Possible solution would be to attach the session ID (utag_main_ses_id) to the request, so at least it would refresh for every session.