Problem with certain tags loading on iPad Safari

[redfuel318]

Hallelujah, I may have found the origin of a problem that's been plaguing us for a number of months in drips and drabs.

We've been comparing order confirmation tag fires from a couple of our partners (VisualIQ, Marin, etc.) with actual orders and have been seeing a growing discrepancy over the last few months, coming to a head with missing a number of orders in large batches. I noticed in one of our campaigns, *every* order to a particular landing page was missing in the vendor counts but was showing up with our fulfillment partner. There was something amiss.

This particular landing page was used by folks carrying around iPad Airs for a particular campaign to sign people up - so I started remote debugging an iPad - and lo-and-behold, the vendor tag (many of them) were not firing - even though they were firing fine on my desktop (on Chrome) and my Android phone (on Chrome) - so this may not be a problem limited to the iPad/Safari. Here's a screencap:

Certain tags that are implemented through the Tealium Pixel (or iframe) container are not firing as the matching utagXXX.js number is showing the error above: "Attempted to assign to readonly property". However there are other tags firing without a problem in this container, also of type "Image", but these are causing errors. 

Help! Is this a bug with the pixel container? (I'm going to continue tracing the JS to see if I can tell what's happening).

-Steve

[redfuel318]

More info: This is happening on desktop Safari (Version 9.1 (11601.5.17.1)) also, not just iPad limited.

[meng_lim · Accepted solution]

@redfuel318,

There was a bug in the Tealium Pixel (or Iframe) Container a while back.  I believe you may be running this version still.  Please drop the template and get the latest version or you can use the Tealium Generic Tag instead if you are only firing one pixel.

Steps to drop the old template:

1. Go to your Tealium Pixel (or Iframe) Container

2. Go to Tag Configurations > Advanced Settings > Edit Template

3. Click the Trashcan icon

4. Click "Save Profile Template"

5. Save/Publish to target environment (i.e. DEV/QA/PROD)

[redfuel318]

Thanks I'll try updating the templates now. Is there a version anywhere I can see the template at to know which ones I'll need to update (it may be 30 tags or so).

[redfuel318]

Thanks, that did it! Best I could tell, it affected the builds before March 9.

I'm appreciative; but is there somewhere these kinds of bugs/fixes are published? This was a fairly big one that has affected all of our company's attribution across the globe for at least the last 3 months. No small thing.

[meng_lim]

hi @redfuel318,

Unfortunately at this point in time, we only have release notes for the Tealium Collect Tag and utag.js.  Generally, we recommend to run the "Tag Status Checker" on a regular basis to make sure all your tag templates are up-to-date.  This can be found by clicking on your name located in the upper-right corner and clicking on "Tag Status Checker" within the drop-down menu.

Also, within the tag templates itself, there are comments that say what was changed since the last version including a date stamp.

Let me know if this helps.

In the future, if you ever experience a similar issue, please feel free to reach out to your Account Manager directly to get it looked at immediately.

[redfuel318]

Thanks @meng_lim, that's super useful. 

Now I'm just having the issue where it's still loading the old templates for the updated tags (minus the first one I tried which happened right away). Is there some kind of CDN caching going on? It's been about 15-20 mins. Maybe I should ask for the loader tag to be updated to the newest version? I'm on 4.36!

[meng_lim]

@redfuel318,

Generally, our multi-CDN edge nodes will grab the latest published tag templates every 5-10 minutes if there was a change.  I think at this point you may need to reach out to your Account Manager to investigate your issue a bit deeper.

In regards to getting your utag.js upgraded, you will also have to consult with our Account Manager to ensure a smooth transition.  There may be significant changes in the latest version (4.40) that could affect your profile when migrating over.  We'll need an engineer to review your profile altogether and make any adjustments (if needed), plus a thorough QA before going live.