A reference for each section of the 401 Group Marketing Intelligence Platform.
The Overview is your daily starting point. It shows every active dealer in a single table with their Meta and Google ad spend for the current month-to-date alongside their monthly budgets and a traffic-light pacing indicator. Green means spend is on track relative to how far through the month you are; amber means slightly over or stalled; red means significantly over budget or severely underspent. The four summary cards at the top give an instant read on total portfolio spend, Meta spend, Google spend, and how many dealers currently have ad accounts configured. Click any dealer row to jump directly to their Dealer Detail page.
Dealer Detail is a deep-dive into a single dealership's ad performance. Use the search box to find a dealer by name or brand. Once selected, you see platform cards for Meta and Google showing their month-to-date spend, monthly budget, and pacing status, followed by a daily spend chart covering the last 30 days. If a budget has not been entered for the current month a budget entry field is shown so you can set it inline. The chart stacks Meta and Google spend by day, making it easy to spot weekends, promotions, or unexpected drops. Use this view when a client calls about their spend or when you need to prepare a monthly report for a specific location.
Tracking is the tag infrastructure audit module. It monitors the marketing tag setup across all 38+ dealer websites by pulling live data from the Google Tag Manager API and from automated headless browser scans of each dealer's homepage. It tracks GTM containers, Meta pixels, GA4 measurement IDs, and Clarity tags, and flags problems automatically — missing containers, orphaned triggers, disappearing tags, pixels that are not managed through GTM, and Meta pixels that are not sending server-side (CAPI) events. The Tracking section has five sub-tabs, each described below.
Settings is where ad accounts are managed and data syncs are triggered. Use the "+ Add account" button to manually register a single Meta or Google ad account to a dealer, or use "Import from Meta BM" to fetch every account in the 401 Group Business Manager at once and assign them to dealers in a single step. Once accounts are registered, the platform pulls daily spend data from the Meta Ads API and from the Google Ads data sheet each night at 5:30 AM. The "Sync now" button runs that collection immediately without waiting for the scheduled job — useful after adding new accounts or after a gap in data.
The Tracking Overview gives a portfolio-wide health check of tag configuration across all dealers. Each row shows a dealer's overall status (clean, warning, or critical), how many tracking containers are registered, how many open critical and warning findings exist, and when their containers were last synced against the live APIs. The four summary cards at the top count total containers, dealers with critical issues, dealers with warnings, and dealers that are fully clean. Click any dealer row to jump to their Tracking Dealer page. This is the right place to start each week to see which dealers need attention before a client call or reporting cycle.
The Tracking Dealer tab gives a full picture of one dealership's tag infrastructure. Search for a dealer to load their registered containers — GTM, Meta Pixel, GA4, and Clarity — along with who manages each one (401 Group or the dealer's own digital agency). Below the container list, open findings are shown with severity and the dates they were first and last detected. Each finding has Acknowledge and Resolve buttons so issues can be triaged without leaving the page.
The Tag inventory section shows the actual contents of each container from the last API sync. For GTM containers this is a full list of every tag and trigger by name and type — exactly what is inside the container, not just a count. For Meta pixel containers it shows CAPI status, the owning business, and browser versus server event counts from the last seven days. The "Scrape live page" button launches a headless browser scan of the dealer's homepage in real time (takes 15–20 seconds) and returns every tracking ID found on the live page: GTM container IDs, GA4 measurement IDs, Meta pixel IDs, Google Ads conversion IDs, and whether Clarivoy, dataLayer, fbq, and gtag are present. This is the fastest way to confirm what is actually firing on a site versus what should be there.
The Inventory tab is the master tag registry for the entire portfolio. It shows every tracking tag found across all 39 dealer sites — GTM containers expanded to their individual tags, Meta pixels with CAPI status, GA4 IDs, and Clarity tags. Use the dealer filter to narrow to a single dealer. Open issues are summarised in a banner at the top; each issue links to the rule explanation below. Issues auto-resolve on the next sync when the underlying condition clears — no manual action required.
The Changes tab shows the snapshot history for all tracking containers over the last 30 days. Each row records a date, the container it covers, and the tag and trigger counts at that point in time. When a container's fingerprint changes between two consecutive snapshots — meaning tags or triggers were added, removed, or modified — that change is surfaced here. This makes it straightforward to answer the question "when did something change in this GTM container?" without logging into GTM directly. It is also the feed that powers the tag_disappeared audit rule, which fires a critical finding any time a tag present yesterday is missing today.
Tracking Settings is where containers are configured and syncs are manually triggered. Each dealer's tracking containers — GTM container IDs, Meta pixel IDs, GA4 measurement IDs, Clarity project IDs — are registered here, along with which party manages them (401 Group or the dealer's own D2C agency). The "Sync all dealers" button runs a full GTM API sync and Meta pixel snapshot across the entire portfolio immediately, rather than waiting for the 4:00 AM scheduled job. The "Run audit" button re-evaluates all audit rules against the current container data, and optionally includes a live HTML scrape of all dealer homepages. Use this after making container changes to see results right away.
Each rule runs automatically on every nightly sync and on any manual sync. When the condition clears, the finding auto-resolves — no manual action needed.
No GTM container has been found for this dealer — either in the tag registry or on the live site. Without GTM, there is no centralised tag management: conversion pixels, analytics, and remarketing tags would all need to be hardcoded directly into the site HTML, making them harder to manage and audit. Action: confirm whether a GTM container exists on the site by running a live scrape on the Dealer tab. If a container is found, it will be auto-registered on the next sync and this finding will clear.
The Clarivoy attribution script was not detected on the dealer's homepage during the last HTML scrape. Clarivoy tracks lead sources and call attribution across sessions — its absence means phone calls and form submissions may not be attributed to the correct marketing channel. Action: confirm with the dealer whether Clarivoy is expected to be on this site. If yes, add the script via GTM. Note that some D2C-managed sites may have Clarivoy on interior pages but not the homepage — in that case this finding can be ignored.
A Meta pixel fbq('init', ...) call was found directly in the page's HTML source, outside of any GTM container. Hardcoded pixels are harder to update, can't be version-controlled in GTM, and may fire inconsistently across pages. Action: remove the hardcoded pixel from the HTML and re-implement it as a Meta Pixel tag inside GTM. The pixel ID will be visible in the live scrape result on the Dealer tab.
A trigger exists inside a GTM container but no tag references it — it doesn't fire any tag and isn't used as a blocking condition on any other tag. Orphan triggers are dead weight: they clutter the container and can mislead anyone reviewing the setup into thinking something is firing when it isn't. Action: low urgency. Review the trigger in GTM and delete it if it is no longer needed. Check whether a tag that used to reference it was accidentally deleted.
A CTA-related trigger in GTM is configured to match on the visible text of a clicked element (e.g. fires when the button says "Get a Quote"). This is fragile: if someone changes the button label — even a small wording change like "Request a Quote" — the trigger stops firing silently and conversion tracking breaks without any error or alert. Action: rewrite the trigger in GTM to use a stable CSS class, element ID, or data- attribute as the matching condition instead of the button text.
A tag that was present in the previous GTM snapshot is completely absent in the current one. This is a regression detector — it fires when someone removes or accidentally deletes a tag from GTM. Conversion tracking, GA4 measurement, or a remarketing pixel could have gone dark without anyone noticing. Action: check GTM's version history for this container to see who made the change and whether it was intentional. If accidental, restore from the previous published version.
The Meta pixel for this dealer has received zero server-side events (Conversions API / CAPI) in the last seven days, or the pixel is inaccessible via the 401 Group Business Manager credentials. Without CAPI, Meta's ad measurement relies entirely on browser-side pixel events, which iOS privacy restrictions significantly degrade — typically 30–60% of conversions go unattributed. Action: implement the Meta Conversions API for this dealer. If the pixel belongs to the dealer's own Business Manager rather than 401's, request co-admin access or confirm they have CAPI set up independently.
Two or more different GA4 measurement IDs are registered for the same dealer. This usually means one ID is the 401-managed property and another was added by the D2C agency or directly by the dealer. Duplicate GA4 tags cause double-counting of sessions, events, and conversions in both properties. Action: identify which GA4 property is the authoritative one (check with the dealer and 401's analytics setup), then remove or pause the duplicate tag in GTM.