AnchorWorks ← The Briefing Room On the record
AnchorWorks
Executive Brief 020 · July 7, 2026

The Measurement Spine

system introduction
Prepared by Chris Campbell AnchorWorks
The Briefing Room · 2026
  • GTM single tag router§ Executive Decisions · Decision Log

    Google Tag Manager is the single tag router — every pixel and tag fires through it, nothing hard-coded, so nothing double-counts.

  • Company-login account ownership§ Executive Decisions · Decision Log

    All tracking and ad/analytics accounts are created under the company login (chris@myanchorworks.com) — never a freelancer or personal account.

  • Capture-once attribution§ Executive Decisions · Decision Log

    Attribution is captured once, at the source, and never overwritten — original source is the truth, not "where they were last seen."

  • Lane boundary (integration contract)§ Executive Decisions · Decision Log

    Tracking is Chris's lane; the dashboard is Ethan's. One written integration contract names who owns every field, so neither re-does the other's work.

  • Tracking-IDs registry: create vs consume§ Major Accomplishments · 03 · Governance

    A single integration contract names who writes every field, plus a hard rule: tracking IDs are Chris's to create and Ethan's only to consume — from one shared registry, never self-provisioned.

See every standing order in the SOP Library →
01 · Executive Summary

The executive summary.

We poured the measurement spine of the Revenue Engine — the plumbing that records where every lead comes from. We provisioned Google Tag Manager and GA4 under the company's own account, created the ten attribution fields inside GoHighLevel that connect the website to the KPI dashboard, and drew a hard, written boundary between the tracking work and the dashboard build so two people can move in parallel without corrupting each other's data.

Until now, "where did this client come from?" was an educated guess. Every future dollar of ad spend depends on answering it precisely — you cannot scale a channel you cannot measure, and you cannot retarget a visitor you never tagged. This is the foundation the entire paid-growth motion sits on, and it is being laid deliberately before the traffic surge rather than scrambled together after it.

AnchorWorks moved from "we think leads come from X" to a system that records the true origin of every contact — the difference between guessing and knowing.

Current stage: Foundation — the measurement layer is being poured ahead of paid traffic; conversion tracking and retargeting are the next courses.

02 · Executive Decisions · Decision Log

What was decided.

  • Google Tag Manager is the single tag router — every pixel and tag fires through it, nothing hard-coded, so nothing double-counts.

    locked

  • All tracking and ad/analytics accounts are created under the company login (chris@myanchorworks.com) — never a freelancer or personal account.

    locked

  • Tracking is Chris's lane; the dashboard is Ethan's. One written integration contract names who owns every field, so neither re-does the other's work.

    locked

  • Attribution is captured once, at the source, and never overwritten — original source is the truth, not "where they were last seen."

    locked

  • Cash is Stripe's source of truth; GoHighLevel holds the sales outcome and deal value; the dashboard reconciles the two.

    locked

  • Ten attribution fields were created in GoHighLevel, keyed exactly to the dashboard's integration contract — reused where clean, never duplicated.

    locked

  • gclid was renamed gclid_capture (GoHighLevel reserves the name) and re-mapped in the contract so the sync still lines up.

    locked

  • Google Ads is deferred (it forces billing at signup); ship Meta + GA4 first and add Google/YouTube later with no rework.

    locked

  • The Meta Pixel is paused until the scattered Meta Business Manager portfolios are consolidated into one canonical portfolio.

    locked
03 · Major Accomplishments

What was done.

01The measurement layer, under the company's own roof.

The problemThe live website had zero analytics — no tag manager, no GA4, no pixel. Every visitor was invisible; nothing about traffic or behavior was being recorded.
What was doneDecision: Provision Google Tag Manager and GA4 under the company's own account, with GTM as the single control layer everything else fires through — so tags can be added or changed without ever touching site code. Implementation: GTM container GTM-PQZJXQW5 and GA4 property G-YBPMV5S1W4 created and verified under the company login. Deliberately not yet installed on the live site — the container is built and waiting; tags go live only after a QA pass. Dependencies: Meta Pixel (blocked — see 04); Google Ads (deferred, needs billing).
The impactThe company now owns its own measurement stack. When ads run, the audiences and conversions accrue to AnchorWorks — a real, transferable asset — not to a contractor's account.

02Ten fields that connect the website to the dashboard.

The problemThe CRM held 64 custom fields but not one for where a lead came from. The KPI dashboard's attribution columns had nothing to read, so origin data could never flow.
What was doneDecision: Create a dedicated ATTRIBUTION field group in GoHighLevel, keyed exactly to the dashboard's integration contract — reusing existing "Lead Source" fields for the human-readable view rather than duplicating them. Implementation: Ten fields created: the five UTM parameters, ad campaign id, the Meta and Google click-ids, and funnel + channel. gclid became gclid_capture (GHL reserves the name) and the contract was updated so the sync maps cleanly. Dependencies: Phase 2C capture wiring (planned, parked); Ethan's GoHighLevel → Supabase sync.
The impactThe literal seam where marketing data meets the dashboard now exists. The moment capture is wired, every new contact carries its true origin — first-touch, immutable, ready for the "one source of truth" ledger.

03One contract, two lanes — so the build can't collide.

The problemTwo builders write into the same database. The real risk wasn't a data clash — it was Ethan's build agent re-provisioning the tracking Chris was setting up by hand. A second pixel means every conversion counts twice and the dashboard is corrupted.
What was doneDecision: A single integration contract names who writes every field, plus a hard rule: tracking IDs are Chris's to create and Ethan's only to consume — from one shared registry, never self-provisioned. Implementation: The contract + a tracking-ids registry became the single handoff surface. The lane boundary was written into the repo's auto-loaded instructions, so Ethan's agent obeys it on every session automatically. Dependencies: None — this is the guardrail everything else runs inside.
The impactNo duplicated work, no double-counted conversions, no corrupted numbers. Two people move fast in parallel without stepping on each other — the governance that makes the whole build trustworthy.

04Racing to bank the retargeting audience — and the blocker it surfaced.

The problemA 30–45 day traffic surge is incoming. Visitors not tagged during it are lost for retargeting forever — so the pixel needed to go in ahead of the full attribution build, not after it.
What was doneDecision: Pull a minimal, audience-only install forward — base PageView on every funnel page — kept separate from the full attribution build so one can never block the other. Implementation: A complete install + QA plan was written and readied. Creating the Meta Pixel then surfaced the blocker: AnchorWorks' Meta assets are scattered across portfolios — the ad account lives under a "Grit & Gains Society LLC" portfolio, the Facebook Page is attached to no portfolio, and an empty duplicate "AnchorWorks" portfolio exists. Dependencies: Chris's Business Manager consolidation decision (which portfolio becomes canonical).
The impactThe install is banked and executable in an afternoon once the portfolios are consolidated — but until then, retargeting audience is not accruing. Surfaced as the single priority decision so it isn't discovered late.

05Why this increases enterprise value.

What was doneA measurement spine is unglamorous plumbing — and it is exactly the kind of asset that separates a business that can scale spend from one that can't. It converts marketing from an act of faith into a system of record. Enterprise value A tracked funnel is sellable An acquirer pays for a business that can prove which channels produce customers and at what cost. An untracked funnel is a black box; a measured one is a documented, transferable growth machine. Less chaos One truth for origin No more debating where leads came from. The system records the true source once, at capture, and never overwrites it — the same "capture once" discipline that keeps the whole dashboard honest. Faster execution Ship channels with confidence The day paid traffic runs, we can already tie an ad to a booked call to a closed deal. Spend decisions get made on evidence, in days, not on hunches over months. Compounding Every visitor now countable Retargeting and lookalike pools start compounding the moment the pixel is in. Audience is an appreciating asset — the earlier it's captured, the larger and cheaper the future reach.
04 · Metrics

By the numbers.

10
Attribution fields live in the CRM
2
Company-owned analytics accounts (GTM · GA4)
45
Rows in the master tracking map (full event blueprint)
5
Funnels mapped end to end
1
Written integration contract (the lane boundary)
0
Tags shipped to production without a QA pass
Done
Analytics accounts provisioned
10 / 10
Attribution fields in the CRM
Planned · parked
Pixel install + capture wiring
05 · Current Company Stage

Where we are.

01
Foundation
02
Launch
03
Scale
04
Expansion
05
Acquisition

AnchorWorks is still in Foundation — deliberately pouring the systems the revenue motion will run on before turning on the taps. The measurement spine is the last major piece of plumbing before paid traffic. Installing the pixel, wiring conversion capture, and starting retargeting are what carry Foundation into Launch.

06 · Open Decisions

Decisions still required.

  • Meta Business Manager consolidation. Choose one canonical portfolio, move the ad account (act=99369130) and the AnchorWorks Facebook Page under it, then create the Pixel there. This blocks all retargeting audience capture.
  • Google Ads account. Create now (forces billing) for YouTube/Google audiences, or defer and ship Meta + GA4 first. Current call: defer — add the Google tag later with no rework.
  • LAS scoring fields. The dashboard contract expects las_stage / las_category / las_tier; GoHighLevel currently holds LAS as tags and scores. Decide whether to add the three fields.
07 · Next Priorities

What comes next.

  1. 01
    Consolidate the Meta portfolios, then create the Pixel
    Unblocks retargeting before the surge — the highest-leverage next move.
  2. 02
    Install GTM on the site + LAS subdomain
    Meta PageView + GA4, preview → QA → production. Starts banking audience and analytics.
  3. 03
    Wire the attribution capture (Phase 2C)
    Populate the ten fields at form submit so the dashboard receives real origin data.
  4. 04
    Build the funnel conversion events
    The tracking map's revenue-truth events — bookings, downloads, registrations, closed deals.
  5. 05
    Close the contract loose ends with Ethan
    Confirm the gclid_capture mapping and settle the las_* field decision.
Executive Brief · Nº 020 · July 7, 2026 · Canonical