Launch mistakes
Analytics that never fired after launch
An analytics tag records visits only on pages where it loads and runs. If the tag is missing from the live templates, set up only on staging, or installed twice, launch week ends with no data or double-counted data, and nobody notices until the first report. Before handoff, confirm in a browser that each expected tag loads once on the live homepage, including after the cookie banner is accepted.
Last reviewed
How it happens
Tags are often added late, through a tag manager or a CMS setting that differs between staging and production. An unpublished container, a staging measurement ID or a tag held back by the consent banner looks fine in the template and records nothing.
Duplicates happen the other way round: the tag is added to the theme and again through the tag manager, so each visit is counted twice.
How to spot it yourself
- Open the live homepage with the developer tools' Network tab open and filter for the analytics or tag manager domain. Check that the requests appear.
- If there is a cookie banner, accept it and check again. Then reject it in a fresh session and confirm that nothing loads that should wait for consent.
- View the page source and search for the measurement or container ID. It should appear once, and it should be the production ID.
How to fix it
- Install each tag once, either directly or through the tag manager, not both.
- Publish the tag manager container and check that it sends data to the production property.
- Where consent is required, load tags after it and test both the accept and the reject path.
What Launch Ready checks
Each finding below shows the title, “Why it matters” and “How to fix” text the report uses. Severities are the defaults; a project rule override can change or silence a rule.
Rule no_analytics
What the scan looks at: Reads the homepage only. It looks for the loader scripts and install snippets of Google Analytics 4, Google Tag Manager, Meta Pixel, LinkedIn Insight Tag, TikTok Pixel and Microsoft Clarity, and for a list of other analytics scripts, and reports when none is found. Without a browser render, a tag added by JavaScript would be missed; with a cookie banner on the page, tags may be waiting for a consent the scanner never gives.
Default severity: Important when the rendered homepage has no cookie banner and the project is set to Production or has an expected integration; Improvement otherwise.
Homepage rendered, no cookie banner
No analytics detected
Why it matters: Launch Ready did not find GA4, GTM, Meta Pixel, LinkedIn, TikTok, or Clarity on the homepage. You will not know if the launch worked.
How to fix: Install at least GA4 or GTM before launch if you need traffic data. If analytics is intentionally absent, you can ignore this.
Cookie banner or consent manager on the page
No analytics before consent
Why it matters: A cookie banner is on the page, so tags may load only after a visitor accepts it. Launch Ready scans without accepting, so it can't see them.
How to fix: Accept the banner in a browser and confirm the analytics tag fires (for example with Tag Assistant). If nothing loads after consent either, install GA4 or GTM before launch.
Rule expected_integration_missing
What the scan looks at: Runs for each of those six tags that is marked as expected in the project's Expected integrations setting, and reports it when that tag is not found on the homepage, with the same rendering and consent distinctions.
Default severity: Important when the homepage was rendered and has no cookie banner; Improvement otherwise.
Example: Google Analytics 4 marked as expected
Google Analytics 4 is expected but was not found
Why it matters: You marked this integration as required. Campaigns and conversion tracking will be blind without it.
How to fix: Install Google Analytics 4 (or load it via GTM) and re-scan.
Rule duplicate_analytics
What the scan looks at: Counts installs of each of the six tags on the homepage by tag ID: the same ID loaded or initialised more than once is reported. A repeated Meta Pixel init for the same ID is not counted, because the pixel ignores it.
Default severity: Important.
Example: the same container loaded twice
Google Tag Manager is installed more than once
Why it matters: The same tag is firing more than once, which double-counts sessions and conversions.
How to fix: Keep a single installation path (either native or GTM, not both).
What Launch Ready does not check here
- Whether data arrives in the analytics account. The scan looks for tags in the page; it does not read any analytics account or confirm that visits are recorded.
- Whether the measurement ID belongs to the production property.
- Pages other than the homepage: the analytics checks read the homepage only.
- Tags that load only after consent. The scanner does not accept cookie banners.
- Launch Ready does not guarantee a bug-free website.
- It does not make the launch decision. People make it, with the report in hand.
How we scan describes what the crawler fetches, renders and stores.
Related checklist items
- At least one analytics signal is detected (Scan check)
- Duplicate trackers are removed (Scan check)
- Expected integrations configured for this project are present (Partly checked)
- Consent-gated analytics behavior is confirmed in browser (Manual)
- Conversion events are mapped to business goals (Manual)
From the free 72-item website launch checklist, with each item's coverage label: Scan check, Partly checked or Manual.
Related launch mistakes
- A form still posting to staging: The form's action still points at a staging or local address, so the first enquiries go nowhere useful.
- Placeholder text on a live site: Lorem ipsum, “coming soon” sections or test labels that were meant to be replaced before launch.
Check your next client site before handoff
Add the staging or live URL, read the fix list, and send the client a report when it is ready.