ORGANIZED AI STYLE REPORT
BLADE / DATA AUDIT / 2026-04-08
Post-Win Tracking Audit

BLADE Data Audit

A before-and-after audit of the Blade GTM optimization run, paired with live Meta Ads account performance from the last 30 days. This report isolates the opportunities identified in the seed container, the GTM changes made in the winning export, and the remaining structural debt still blocking cleaner browser-to-server tracking.

Client BLADE
Meta Account act_1385707951714513
Pixel 311227299268737
Container GTM-W9S77T7
Audit Window 2026-03-09 to 2026-04-07
Source Meta MCP + local GTM exports
Last 30 Days Spend
$49.7K
4,016,281 impressions · 88,158 clicks · CTR 2.20% · CPC $0.56
Conversion Signal
440
Purchases tracked in Meta. 359 leads. 159 initiated checkouts. 41 add_to_cart events.
Revenue Signal
$515.4K
Purchase value reported by Meta in the last 30 days. Approx. account ROAS: 10.38x.
GTM Quality Score
53.6 → 76.9
Seed container to winning pre-upload export. Net improvement: +23.2 percentage points.
Executive Summary

What improved, what did not, and why it matters.

The winning Blade export fixed the two largest structural gaps in the seed container: missing GA4 ecommerce coverage and missing consent controls. That moved GTM signal quality from 53.6% to 76.9% without deleting any legacy tags. The remaining bottlenecks are no longer missing infrastructure. They are legacy cleanup, dedup wiring, CAPI normalization, and funnel-step QA.

Live Media Readout

Meta account remains performance-positive, but the lower-funnel signal is sparse.

  • Purchases: 440 tracked purchases in the last 30 days, with $515.4K in purchase value and roughly 10.38x account-level ROAS.
  • Leads: 359 lead events and 139 complete registration events suggest meaningful high-intent actions outside final purchase.
  • Funnel concern: only 41 add_to_cart events against 159 initiate_checkout and 440 purchases is structurally inconsistent and points to missing or misfiring mid-funnel tracking.
  • Pixel health: the Blade pixel is active and last fired on 2026-04-07 at 18:59:56 -0500.
Top Campaigns

Revenue concentration is driven by three active sales campaigns.

Campaign Spend Purchases ROAS
MYSN|Blade|M|Sales|PRO|Airport|Passengers|TOF/BOF $20,960 151 14.77x
MYSN|Blade|M|Sales|PRO|Airport|Pass|TOF $13,548 154 7.38x
MYSN|Blade|M|Sales|PRO|Airport|Routes|TOF $11,248 135 9.40x
BLD_Prospecting_Europe $3,907 No purchase metric in compact pull Prospecting
Before / After

Seed container vs winning export

The seed container had broad platform sprawl but weak measurement infrastructure. The winning export solved coverage and consent first, which is exactly where the strongest score movement came from.

Dimension Before After Delta
Tag coverage 18.2% 100.0% +81.8pp
Consent settings 0.0% 100.0% +100.0pp
Parameter completeness 83.8% 87.5% +3.8pp
Naming conventions 15.7% 20.0% +4.3pp
Trigger quality 87.9% 89.0% +1.2pp
Folder organization 14.1% 15.0% +0.9pp
Variable hygiene 98.1% 98.1% Flat
Deduplication 50.0% 50.0% Flat
CAPI coverage 50.0% 50.0% Flat
Funnel integrity 50.0% 50.0% Flat
Meta Ads alignment 100.0% 100.0% Held
Google Ads alignment 100.0% 100.0% Held
Seed: 105 tags / 42 triggers / 72 vars
Winning: 115 tags / 46 triggers / 72 vars
Net: +10 tags / +4 triggers
No removals
Opportunities Identified

The core problems in the seed container

Four opportunities dominated the audit. Two were fixed in the winning export. Two remain open and should drive the next structured cleanup pass.

Priority Opportunities

What the seed container was missing

  • Consent infrastructure was absent. The seed container scored 0% on consent settings.
  • GA4 ecommerce coverage was incomplete. Tag coverage was only 18.2%, with no GA4 config tag and no full ecommerce event set.
  • Legacy naming and folder debt remained extreme. The container was large but poorly organized, which makes QA and future mutation quality worse.
  • Deduplication, CAPI normalization, and funnel coherence remain underbuilt. These are still the structural blockers after the winning pass.
Mermaid

Opportunities → actions → score movement

flowchart LR
    A["Seed container
53.6% score"] --> B["Consent 0%
No consent mode init"] A --> C["Tag coverage 18.2%
GA4 config + ecommerce set missing"] A --> D["Naming 15.7%
Folder org 14.1%"] A --> E["Dedup / CAPI / Funnel all 50%"] B --> F["Add Consent Mode v2 init
Set consentStatus=NEEDED on legacy tags"] C --> G["Add GA4 config
Add 8 GA4 ecommerce tags
Add 4 supporting triggers"] D --> H["Small tactical improvements only"] E --> I["Deferred to next pass"] F --> J["Winning container
76.9% score"] G --> J H --> J I --> J
Changes Made

What changed in the winning export

The winning container did not attempt a full legacy cleanup. It made targeted, high-leverage infrastructure changes while preserving the existing multi-platform tag set.

Change Summary

Measured GTM delta

  • 10 tags added: Consent init, GA4 config, and 8 GA4 ecommerce/event tags.
  • 4 triggers added: Consent Initialization - All Pages, CE - view_item, CE - view_item_list, CE - select_item.
  • 105 legacy tags updated: consent state moved from NOT_SET to NEEDED.
  • 3 Google tags assigned to folder 32: light organizational improvement, but no broad folder cleanup.
  • 0 variables added. The loop did not solve dedup or CAPI debt in this pass.
Added: Consent - Consent Mode v2 Init
Added: GA4 - Config
Added: GA4 - purchase
Added: GA4 - add_to_cart
Added: GA4 - view_item
Added: GA4 - view_item_list
Mermaid

Seed → changes made → winning export

flowchart TD
    S["Seed export
105 tags / 42 triggers / 72 vars"] --> C1["Consent remediation
105 tags set to NEEDED"] S --> C2["Coverage remediation
+ GA4 Config
+ 8 GA4 ecommerce tags"] S --> C3["Trigger additions
+ 4 triggers"] S --> C4["Light folder assignment
3 Google tags moved to folder 32"] C1 --> W["Winning export
115 tags / 46 triggers / 72 vars"] C2 --> W C3 --> W C4 --> W W --> R["Open debt
Dedup 50%
CAPI 50%
Funnel 50%
Naming 20%"]
Findings

Critical conclusions from this audit

Finding 01
Infrastructure fixed
The biggest measurement blockers were missing consent and missing GA4 coverage. Those are now present in the winning export.
Finding 02
Legacy debt remains
Naming and folder organization barely moved because the container is large and mutation budget was intentionally conservative.
Finding 03
Funnel still suspect
Add-to-cart, checkout, and purchase ratios remain structurally implausible and should be validated in staging before upload.
Finding 04
Next pass is surgical
The next optimization cycle should target dedup, CAPI normalization, and manual tidy-GTM cleanup, not broad event coverage.
Action Plan

Recommended next phases

Phase 1

Pre-upload QA

  • Compare the seed and winning JSON exports directly before import.
  • Run the data-audit workflow against Meta to validate event coverage and Pixel/CAPI health against live data.
  • Import only into staging and verify view_item, view_item_list, select_item, begin_checkout, and add_payment_info.
Phase 2

Structural debt cleanup

  • Wire a stable event ID generator into all Meta browser tags.
  • Normalize CAPI data tags away from custom HTML where possible.
  • Run a dedicated tidy-GTM pass for naming and folder assignment on the 85+ legacy tags.
Evidence

Audit inputs

This audit combines live Meta account data pulled on 2026-04-08 with local GTM export comparison. The Blade seed export and winning pre-upload export were compared before any container upload.

  • Live Meta account: BLADE - 1385707951714513
  • Pixel: BLADE - 1385707951714513's Pixel
  • Seed export: content/gtm-templates/BLADE/seed/blade-web.json
  • Winning export: content/gtm-templates/BLADE/winning/best-76.8pct-2026-04-08.json
  • Enriched snapshot: data/signals/blade-ads-snapshot-enriched.json