Deploy the script with Google Tag Manager
One button writes MarqIQ’s tracking tag into your GTM container, so nobody has to edit the site. MarqIQ writes the tag and stops there — you review it in GTM and publish it yourself. This article starts from a container that is already connected; if yours is not, read Connect Google Tag Manager first.
Before you start
Connect GTM shortly before you deploy
Deploying needs a Google access token that has not expired. You generate it yourself and it lasts about an hour. Where renewal is switched on for your workspace, MarqIQ renews it from the refresh token you stored and the deploy goes through; the Google Tag Manager screen says whether it is. Where it is not, paste a fresh token whenever a deploy returns an error from Google.
Permissions required
You need Publish rights on the GTM container to publish the change once MarqIQ has written it.
The Google pages you will need
Generate the access token at developers.google.com/oauthplayground, and open your container at tagmanager.google.com. The Tag Manager API has to be switched on for your Google Cloud project first, at console.cloud.google.com/apis/library/tagmanager.googleapis.com — without it every request comes back as a 403.
Deploy the tag
Open Tracking Script in the sidebar.
It opens Install & deploy. The page itself is headed Script & Deploy.
Find the card headed Deploy to Google Tag Manager.
The sidebar carries a separate Google Tag Manager item, which is the connection screen. The deploy button is on Script & Deploy, not there.
Click Deploy to GTM.
Read the confirmation.
It names the tag it wrote and its GTM tag id, and tells you to publish your workspace. The page header then reads Live in GTM beside the version number.
What lands in your container
| What | Value |
|---|---|
| Tag name | MP Unified Tracking |
| Tag type | Custom HTML |
| Trigger | All Pages |
| Workspace | The first workspace in the container |
| Published? | No — you publish it |
Search your container for MP Unified Tracking. The card in MarqIQ describes it as a "MarqIQ" tag, which is the name people look for in GTM and never find.
Deploy again later and MarqIQ updates that same tag rather than adding a second one. It matches on the tag name, so if somebody renames it in GTM the next deploy creates a new one alongside.
Note
MarqIQ touches nothing else in your container. No other tag, trigger or variable is read, changed or removed.
Publish it
MarqIQ stops short of publishing, so a person always approves what goes live on the site. Until you publish, the tag sits in the workspace and runs on nothing.
Open your container at tagmanager.google.com.
Find the MP Unified Tracking tag in the workspace MarqIQ wrote to.
If your team uses several workspaces, confirm you are looking at the first one — that is where it lands, and there is no picker.
Click Preview and load your site.
Confirm the MP Unified Tracking tag fires on a page view.
Click Submit.
Click Publish.
Check that MarqIQ is receiving something
Publishing in GTM proves the tag is live. It does not prove anything is reaching MarqIQ, and the two fail separately.
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 Script Capture Quality.
Your submission appears under Submissions — last 14 days. Before the first submission arrives, that block reads No submissions yet instead.
Open Setup & diagnostics.
Read the Form capture card.
A working install shows Form submissions marked Ready, with the count it was measured on.
Note
MarqIQ records a submission when a form is actually submitted. Loading a page that carries the tag records nothing on its own, so a page view is not a test.
If it did not work
Deploy to GTM fails with an error from Google about authentication
Why: The Google access token expired. A token from the OAuth Playground lasts about an hour, and MarqIQ does not renew it.
Fix: Generate a fresh access token at developers.google.com/oauthplayground, paste it on the Google Tag Manager screen, click Update connection, then deploy again. MarqIQ shows you the message Google returned, so read it before repeating the step.
Deploy to GTM answers with an upgrade message
Why: One-click deploy is a Pro feature. The message names the plan it belongs to and the plan your workspace is on.
Fix: Click Copy tag on the CDN Install card and paste the tag into your site yourself, or change plan on Plan & billing. The script is served on every plan, so pasting it by hand costs you the button and nothing else.
You cannot find the tag in GTM
Why: You are searching for "MarqIQ". The tag is named MP Unified Tracking.
Fix: Search for MP Unified Tracking, and check that you are in the container’s first workspace.
The tag is there but the site records nothing
Why: The workspace was never published, so the tag exists in GTM but is not on the live site.
Fix: In GTM, click Submit, then Publish. Then open Setup & diagnostics and confirm Form submissions reads Ready.
Two MP Unified Tracking tags now exist
Why: The original was renamed in GTM, so the next deploy did not recognise it and created a fresh one.
Fix: Delete the older tag in GTM and leave the name alone. MarqIQ finds its tag by name.
The deploy worked, the container is published, and nothing arrives
Why: The install is only one of the causes. Consent gating, a content security policy, an ad blocker on your test browser and a cached page all look identical from a dashboard.
Fix: Work through The script is installed but nothing is arriving. It takes the causes in the order that finds yours fastest.
Next steps
Related articles
Was this article helpful?