Insight is not enough.
Implementation is
where value is created.
Every high-priority finding becomes an Implementation Pack — a single document with the owner, the steps, the QA checklist, the success metric and the validation plan.
Ten parts.
One ship-ready brief.
Every pack follows the same structure so any team — in-house or agency — can pick it up and act without translation.
- 01Title & priority
Clear headline plus High / Medium / Low priority based on commercial impact.
- 02Owner role
Mapped to the role best placed to ship the fix — developer, paid media, CRO, ecommerce ops.
- 03Issue summary
One-paragraph description of what is broken or under-performing.
- 04Why it matters
Commercial impact framed in revenue, EBITDA or wasted spend terms.
- 05Evidence
The specific data points, variance, timeframe and source that triggered the finding.
- 06Recommended steps
Numbered, sequential implementation steps written for the assigned owner.
- 07QA checklist
What to verify before marking the fix complete.
- 08Success metric
The single metric and tolerance that defines a successful fix.
- 09Validation window
How long Attributed will watch after the fix lands to confirm resolution.
- 10Status lifecycle
Tracked from Generated → In review → In progress → Implemented → Validated.
One real pack,
end to end.
A typical High-priority pack generated by Forge from a Ledger finding.
GA4 purchase revenue under-reporting
Shopify revenue is 24% higher than GA4 purchase revenue over the last 7 days, suggesting a material under-count in GA4.
Reporting, ad platform optimisation and audience modelling are all anchored to GA4 revenue. A 24% under-count means Smart Bidding is optimising against a weak signal, board reporting understates store performance, and remarketing audiences exclude legitimate buyers.
- Shopify revenue (7 days): £142,300 — verified at transaction level.
- GA4 purchase revenue (7 days): £108,150 — variance −24.0%.
- Variance exceeds 10% tolerance for six consecutive days.
- 23% of Shopify transaction IDs have no matching GA4 purchase event.
- 01Audit the GA4 purchase tag in GTM and confirm it fires on every Shopify thank-you page variant.
- 02Verify transaction_id is populated on every purchase event and matches the Shopify order ID.
- 03Confirm consent gating is not blocking the purchase event for users who have accepted analytics.
- 04Validate cross-domain configuration between the storefront and the checkout subdomain.
- 05Backfill the past 30 days using the Measurement Protocol if material revenue is permanently lost.
- GA4 DebugView shows purchase events firing on every test checkout.
- transaction_id matches Shopify order ID in every test transaction.
- GA4 Real-time Purchase report matches Shopify within 5 minutes.
- Daily Shopify vs GA4 variance returns within ±10% for 7 consecutive days.
Reduce Shopify vs GA4 revenue variance below 10% within 14 days.
14 days post-fix
From generated
to validated.
Every pack moves through the same five states so progress is always visible to the team.
- 01Generated
- 02In review
- 03In progress
- 04Implemented
- 05Validated
Forge turns findings
into Implementation Packs.
Forge listens to every other agent. When a finding clears the priority threshold, Forge generates the pack — owner, steps, QA, metric, validation.