Check that tracking works, and fix it when it does not
Where to see that data arrives from your site, a two-minute test in the browser, and the usual reasons nothing arrives — with the fix for each.
M
Monfri TeamUpdated ·3 min read
Three screens in CDP tell you whether data arrives from your site:
- Settings → Tracking & SDK → Verify installation — checks every 5 seconds and says Tracking is working at the first events.
- Configure → Sites — the site's card turns Active once events arrived in the last 24 hours. See Sites in CDP: the domains that send you data.
- Audience → Events — every event as it arrives. See What CDP collects: events.
A two-minute test
- Open your site in a normal browser window — not a private window with a blocker, not a test robot.
- If a consent banner appears, click Accept.
- Open three or four pages. On a store, open a product and add it to the cart.
- In CDP, open Audience → Events: your page views appear within seconds, your cart a moment later.
Look in the browser
When the test shows nothing, look at your site in the browser:
- The tag is there. Open the page source (right click → View page source) and search for
monfri.global.js. If it is not there, the tag is not on the live site. With Google Tag Manager the tag is added later and is not in the source — go to step 3. - The script has no complaint. Open the developer tools → Console. A warning or an error that starts with
[CDP]says what is wrong; no[CDP]line at all is normal when everything works. - Events leave. In the developer tools → Network, filter by
cdp.monfri.net. You should see a request to/v1/configand, as you click, requests to/v1/events.
The usual reasons, and the fix
| What you see | Why | What to do |
|---|---|---|
| The tag is not in the page source | It was never published, or a theme update removed it | Add it again; with Google Tag Manager, publish the container. |
| The tag is in your theme, not in the page source | A cache plugin or a CDN serves old pages | Clear the cache of the site and of the CDN. |
Requests to /v1/events only after Accept |
The consent mode is Strict opt-in, or your consent manager has not said yes | That is how the mode works. See Consent and cookies on your site. |
No request to cdp.monfri.net at all |
A blocker in your own browser, or your site's Content Security Policy | Test without the blocker. If the console reports a Content Security Policy, allow https://cdp.monfri.net in script-src and connect-src. |
| Requests fail with 401 | The key in the tag was revoked or belongs to another workspace | Copy the tag again from Tracking & SDK. |
| Page views arrive, store events do not | The store is not recognised | Set Site type to E-commerce and choose the Platform, then Update script. |
| Nothing when you test with a robot or PageSpeed | Automated browsers are ignored on purpose | Test as a person, in a normal browser. |
When the numbers look low
CDP counts people who reached your site with the script running. Compared with another analytics tool, the numbers differ because of the consent mode, blockers and filtered bots, and because each tool defines a visit and a visitor in its own way. Compare trends, not exact numbers.
Still nothing
Write to [email protected] with your site's address, the time you tested and what the Console and Network tabs show. A screenshot helps.