The script is installed but nothing is arriving
An empty submissions count has eight ordinary causes, and they look identical from a dashboard. This article puts them in the order that finds yours fastest, and tells you what to look at for each. If the tag is not on the site yet, read Install the tracking script first.
Before you start
Open Setup & diagnostics before you change anything. The Form capture card tells you whether MarqIQ has ever received a submission from this workspace, and prints the figure it read.
Tip
Test in a private browsing window with extensions turned off. An ad blocker on your own browser produces exactly the symptom you are chasing, and it costs nothing to rule out first.
Read the diagnosis first
Setup & diagnostics separates the causes it can tell apart, so you do not chase the wrong one.
- Blocked on Capture is running means MarqIQ is not recording new submissions: the subscription has lapsed, or the workspace is read-only or suspended. The card says so in as many words — this is not a problem with your website or your script.
- Not set up on Form submissions means nothing has ever arrived. Work through the causes below.
- Failing on Still receiving means submissions used to arrive and stopped. Something changed — a container republished without the tag, or a consent banner that stopped reporting.
- Ready on Form submissions with Nothing yet on First-touch attribution means capture works and the hidden fields do not. That is a different article.
Note
If the workspace waits for cookie consent, Setup & diagnostics says so rather than blaming the tag, and lists every way a banner can report consent.
The eight causes, in the order to check them
Work down the list. Each one is quicker to rule out than the one after it.
The script address itself does not return a script
Why: The key in your tag no longer matches a workspace, or capture is stopped at MarqIQ's end. In both cases MarqIQ answers with a one-line comment instead of the script, and your site loads nothing.
Fix: Open Script & Deploy and click the Script URL link. A healthy file starts `/ MarqIQ tracking · plan: ... /`. `/ MarqIQ: invalid token /` means re-copy the tag. A comment about the subscription, a read-only workspace or a suspended workspace means open Plan & billing.
Your test browser sends Do Not Track or Global Privacy Control
Why: The script treats either signal as an explicit opt-out. It writes no cookie and sends MarqIQ nothing for that visitor, whatever your consent setting says. With Wait for cookie consent on, it fills no form field for them either.
Fix: Turn the browser setting off for the test, or test in a browser that does not send it. Some privacy-focused browsers send Global Privacy Control by default.
An ad blocker or privacy extension is running on your test browser
Why: Blockers treat any script that reports form activity as a tracker and stop the request before it leaves the page.
Fix: Test in a private window with every extension disabled. If it works there and not otherwise, the install is fine and you were testing through a blocker.
The workspace waits for cookie consent and your banner never reports it
Why: With Wait for cookie consent on, the script sends nothing, writes no cookie and fills no form field until it is told consent was given. A banner that keeps its decision to itself looks exactly like a missing tag.
Fix: Open Script & Deploy and read the Wait for cookie consent card. The script accepts consent in four ways: Google Consent Mode granting `analytics_storage` in a `consent` update on the dataLayer, `window.marqiqConsentGranted()`, `window.MarqIQConsent = true`, or an `mp_consent=granted` cookie. Wire your banner to one of them, or turn the setting off.
Take care
Consent Mode defaults are not consent on their own. They count only when no default denies `analytics_storage` — so a default that denies in the UK and EU and grants elsewhere reads as no consent for every visitor, because the script cannot tell where a visitor is. The most recent update always decides, whichever way it goes.
Note
MarqIQ writes no consent cookie of its own. A banner that reports consent by calling `window.marqiqConsentGranted()`, by setting `window.MarqIQConsent = true`, or by pushing a Consent Mode update has to do it on every page, not only the page where the visitor accepted. An `mp_consent=granted` cookie your banner sets is read on every page, so that one path does carry over.
The page being served was built before you added the tag
Why: A caching or optimisation layer keeps serving the old HTML. This is the usual answer on WordPress with a caching plugin, and on any site behind a CDN.
Fix: Clear the cache at every layer — the plugin, the host, and the CDN — then load the page again and view its source. The tag is either in the HTML or it is not; nothing else settles this.
A Content Security Policy blocks the script
Why: The tag loads from the MarqIQ address shown under Script URL. If your pages send a `Content-Security-Policy` header, the browser refuses any script from an origin the policy does not list.
Fix: Open the page, look in the browser console, and check for a refusal naming that address. Add the origin to your `script-src` and `connect-src` directives. `connect-src` matters too, because submissions are reported back to the same origin.
The GTM tag exists but the container was never published
Why: A MarqIQ deploy creates or updates the MP Unified Tracking tag in your workspace and stops there on purpose, so that a person approves what goes live.
Fix: Publish the container in Google Tag Manager. Check the trigger while you are there — the deploy sets All Pages, and a hand-edited trigger may now match nothing.
The tag is on the site, but not on the pages with forms
Why: The tag was added to one template and the forms live on another, or it was put on the home page only.
Fix: View source on the actual page holding the form. Put the tag in a template every page uses, including landing pages your marketing tool serves.
What a working install looks like
Submit one of your own forms with a real email address.
MarqIQ refuses a malformed address rather than storing it, so type a real one.
Open Home.
Read Submissions — last 14 days.
Open Setup & diagnostics.
Confirm Form submissions now reads Ready.
The check prints the count it was measured on, so you can see your test in it.
Note
MarqIQ reports a submission when the form is actually submitted. Loading a page that carries a form records nothing on its own.
Two places the script deliberately does nothing
- Inside HubSpot's drag-and-drop page editor. The script stops on that domain so that editing a page never records a visit.
- On a visitor whose browser sends Do Not Track or Global Privacy Control. No cookie is written and nothing is sent to MarqIQ for them, and this is never overridden.
Next steps
Related articles
Was this article helpful?