Troubleshooting story tracking

Almost everything that goes wrong with story tracking has one of about nine causes, and most of them look like something else. This article is a list of symptoms and what's actually behind them, so you don't lose an afternoon to it.

I published my container but nothing fires

Almost always the cache. Tag Manager serves your container with a 15-minute cache lifetime, so after publishing your own browser can keep using the previous version for up to a quarter of an hour.

The confusing part: tags that existed in the old version keep working normally, so it looks like "Analytics is fine, Meta is broken" when in fact nothing is broken at all.

Fix: hard refresh the story page (Cmd+Shift+R on Mac, Ctrl+Shift+R on Windows), or simply wait fifteen minutes. Real visitors arriving for the first time always get the current version, so this only ever affects whoever is testing.

Preview mode says it can't connect

Tag Manager's Preview needs a two-way handshake between Tag Assistant and the story tab. When that handshake fails, Tag Manager doesn't fail gracefully — it holds every tag back and queues the page's own events.

The symptom is deceptive: the debug badge appears, the container loads, and yet no tags fire and the story's events don't show up either. That looks exactly like a broken setup when the setup is fine.

Two things to know:

• Never reload the debug tab by hand. A manual refresh kills the handshake. Use Open again inside Tag Assistant instead.
• If it still won't connect, allow third-party cookies for tagassistant.google.com, or try a clean browser profile with extensions disabled. Ad blockers and privacy extensions are a common cause.

If Preview simply won't work for you, publish and verify in Analytics Realtime and DebugView instead.

My story link says "Page not found"

Share links are case-sensitive. A code like aBcD1eF is not the same as ABCD1EF.

This bites most often when you copy a link out of a place that displays URLs in capitals — Meta's Ad Library does exactly this, showing every destination in upper case. Retyping what you see gives you a dead link.

Fix: always copy the link from the Share dialog in Intractive, or copy the actual link target rather than the displayed text.

I imported a container and nothing changed

Container imports can fail quietly. The preview screen shows the changes correctly, you confirm, and the workspace still shows zero pending changes.

Fix: after every import, open Tags and confirm the new tags are actually listed. Don't rely on the confirmation screen. If they're missing, run the import again.

Variables show as undefined when testing

A capitalisation mismatch, nine times out of ten. Data layer variable names must match the story's field names exactly: storyId, not storyid or StoryId.

Check the variable's Data Layer Variable Name field against the event names in Story events with Google Tag Manager.

The completion event fires several times per visitor

The Once per page setting is missing. Milestone triggers use conditions like "progress is greater than or equal to 50", which keep matching on every later progress message from the same visitor.

Fix: on that tag, Advanced Settings → Tag firing options → Once per page. A story is one page load, so once per page means once per story.

This one matters because it inflates conversions rather than losing them, so nothing looks broken — the numbers just quietly flatter you, and any campaign optimising on that event is being trained on bad data.

My Analytics parameters aren't in any report

They haven't been registered. Analytics collects event parameters happily but won't report on them until each one is declared by hand.
Fix: Analytics → Admin → Custom definitions, and add each parameter as an event-scoped custom dimension or metric. See step 5 of Sending story events to Google Analytics 4.

Realtime shows event names whether or not you've done this, which makes it easy to assume everything is finished.

Meta's Test events tab is empty

This is how it's designed to work. Test events only lists events carrying a test code, and for a website that means you have to open the page from that panel — select channel Website, paste the story link, and use Meta's own button.

Browsing to the story yourself will never appear there, even with a perfectly working pixel. Those events show up under Overview instead.

For instant feedback, use the Meta Pixel Helper Chrome extension. It lists every pixel call with its parameters as they fire, and it's the closest thing Meta has to Tag Manager's Preview.

Events Manager Overview shows no activity

Two usual causes, and it's worth ruling out both before concluding anything:

• The date range excludes today. Overview often opens on a range ending yesterday. Set it to Today.
• Processing delay. Meta states events can take up to 30 minutes to appear. Overview is confirmation, not a live debugger.

Nothing at all is being sent from a story

Work down this list:

1. Is a Tag Manager ID filled in under Project settings → Tracking & scripts?
2. Is the story published? An unpublished story has no public page to track.
3. Is the container published, not just saved? Check that the live version has the tags in it.
4. Does the story have variables? If not, intractiveVariablesUpdated will never fire — progress and outbound events will still work.
5. Are the tags gated on consent that hasn't been granted in your test session?

A quick way to split "didn't load" from "didn't engage". Compare the ad platform's landing page views against your intractive_story_start count in Analytics. Story start fires as soon as the story renders, so if the platform reports many more landings than you have starts, people are leaving before the story appears — a loading or connection problem. If the two roughly match, they saw the story and chose not to engage — a content or message problem. Same symptom, completely different fix.

✅ Quick checklist

• Published container, hard refresh, wait 15 minutes.
• Never manually reload a Preview tab.
• Share links are case-sensitive.
• Verify tags after any container import.
• undefined variables mean a capitalisation mismatch.
• Repeated conversions mean a missing Once per page.
• Missing Analytics dimensions mean unregistered custom definitions.
• Meta Test events only shows events launched from that panel.

Updated on: 24/09/2026