> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.intractive.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Meta - Tracking a story's performance

# Tracking a story's performance
There are two halves to measuring a story. **UTM tracking** tells the destination page where a visitor came from, so you can prove a story sent traffic somewhere. 

**Tag Manager** tells you what happened *inside* the story: how far people got, what they answered, whether they clicked through, and it feeds that back into advertising platforms so campaign targeting improves.

These articles cover the second half. Start at the top and work down; each one assumes the one before it.

| 💡 The one thing to understand before you start: Google Tag Manager is a delivery van, not a destination. It has no reports of its own. It sits on the story page and forwards what happens to Google Analytics, Meta, or anything else. A Tag Manager ID on its own produces nothing visible until you give it somewhere to send data.

# The articles
| Article | Read it when | What you'll get |
| ---- | ---- | ---- |
| Story events with Google Tag Manager | GTM is the most logical option | Where the Tag Manager ID goes, and exactly which three events a story sends |
| Sending story events to Google Analytics 4 | You want reporting and drop-off analysis | A working Analytics setup, step by step |
| Meta pixel and campaign tracking strategies | A paid campaign points at the story | The pixel setup, plus which events actually improve targeting |
| Adding a meta pixel without Google Tag Manager | You need a quick way to add a meta pixel | The pixel setup, plus which events actually improve targeting |
| Consent and tag gating | Before any campaign goes live | How to make tags respect a visitor's choice |
| Troubleshooting | Something isn't arriving | Nine symptoms and what's really behind them |
# Quick reference

## The two IDs people mix up
| ID | Looks like | What it does |
| ---- | ---- | ---- |
| Tag Manager container | `GTM-XXXXXXX` | Goes in **Project settings → Tracking & scripts**. Decides what fires and when. |
| Analytics measurement ID | `G-XXXXXXXXXX` | Goes inside Tag Manager. Decides where the data lands. |
## What a story sends
| Event | Fires when |
| ---- | ---- |
| `intractiveStoryProgress` | The story loads, and on every progress change |
| `intractiveVariablesUpdated` | A story variable changes — this is how answers get out |
| `intractiveOutboundLink` | Someone clicks a link out of the story |


|| ⚠️ The Tag Manager ID, Header scripts and Footer scripts fields are admin-only. If you can't see the Tracking & scripts section in project settings, ask an admin in your organisation.


✅ **The five mistakes that cost the most time**
* Expecting reports inside Tag Manager. It has none.
* Forgetting **Once per page** on milestone tags, which silently multiplies your conversions.
* Skipping the custom definitions step in Analytics, so parameters are collected but never reportable.
* Testing within 15 minutes of publishing and trusting what you see.
* Optimising a campaign toward story completion without checking what "complete" means in that story's shape.