No data arrives from my site

Open the site with the browser's network tab:

tracker.js must load from your backend.
POST /api/marketing/collect must answer 200. Use the table below to diagnose other responses or dropped events.
The script tag must not use type="module": it defeats document.currentScript, and the tracker cannot read its attributes.

Collect response	Meaning and next step
403	The page's host is not the website's domain, one of its subdomains, or one of its extra hosts. Add it with Allow this host on the Websites page.
404	The website id is unknown or the site's Collect data switch is off.
Every event `dropped`	Collection is paused in Settings.

The install guide's step 3 runs the same checks for you. See Verify.

Every visitor looks like the same person

The backend runs behind a reverse proxy and the DMS does not trust it. Set the DMS auth.trustedProxies to the number of proxies in front of the backend. See Configuration.

The heatmap is empty

Heatmaps record a sample of page loads (10 % by default). Check the sampling in Settings or the site's data-heatmap-sample attribute, and give the page some traffic. See Pages & heatmaps.

The heatmap has no page behind it

The backdrop is a page snapshot, which is off by default because it stores page content. Turn on Page snapshots in the website's Capture tab, then wait for a sampled visit.

A setting change does not reach visitors

The served tracker embeds the settings and is cached for one hour. Returning visitors pick up the change within that window; resuming collection reaches them within a minute.

The module uses these privacy measures:

It sets no cookie and stores no IP, user agent or headers.
It counts visitors with a server-side hash salted every month.
It honours Do Not Track.

Whether that qualifies for a consent exemption depends on your jurisdiction and use. The design follows the shape audience-measurement exemptions ask for, but the compliance analysis stays yours, especially if you enable page snapshots or the GeoIP country dimension.

Can tenant users see these pages?

No. Module pages are reserved to the platform owner. Build a tenant-facing page in your project and read the data through the marketing interface.

I upgraded to 0.5: what changed?

Marketing 0.5 requires:

@antelopejs/dms 0.9.
@antelopejs/interface-dms 0.7.
The renderer @antelopejs/dms-frontend 0.6.

Upgrade those dependencies together first. Troubleshooting covers dependency resolution and frontend integration errors. Data, settings and the tracker tag are unchanged.

The tracker routes are now declared to the frontend server, so a tag pointing at the dashboard's origin keeps collecting. On renderer 0.6 with an older module, its beacons were refused with a 403.

Known issues

The defects found end-to-end and how each was closed are listed in KNOWN-ISSUES.md. None is open.

FAQ