Acknowledge Findings

Acknowledge Findings is the gate between Audit and Build. The page renders an audit receipt at the top — the GA4 / GTM pair you saved in Discover, when the audit last ran, and how many review items were acknowledged — and a single guided section that lets you record the acknowledgement. Once recorded, the Build stage unlocks. Until then, the Build link at the bottom of the page is greyed out.

Acknowledging doesn't write any GTM, GA4, or Cloud resources. It's a single timestamp on the audit run. Clearing it (or anything that invalidates the underlying review-tag acknowledgements upstream) restores the locked state.

Happy path

Confirm the audit receipt at the top matches the GA4 / GTM you meant to audit.
Click Acknowledge findings.
Continue to Build — Server GTM.

Glossary▶

Audit receipt: The decision-record card at the top of the page. Lists the GTM web container, primary GA4 property, last audit timestamp, and review-item acknowledgement count for the run you're about to acknowledge.
Acknowledged: The state once you've clicked Acknowledge findings. The audit run carries an "approved_at" timestamp, the bottom nav link enables, and Build / Cloud / Connect pages stop redirecting to their locked panels.
Outstanding items: Things upstream that prevent acknowledgement: unacknowledged review tags, the missing no-core-events acknowledgement, or a failing primary-tag check without override. The page links back to Review Audit Report when this is the case.
Live setup: State the setup enters post go-live. This page becomes read-only and shows whether the acknowledgement was on the receipt at the time of go-live. Use Changes and Health for post-live review.

Not covered on this page: the audit scan itself (Review Audit Report) or the Build stage you're unlocking (Build — Server GTM).

Before you start

Complete Select GA4 and GTM + Review Audit Report.
Every "routable with review" tag on the report should be acknowledged and saved.
If no core events were detected, the no-core-events acknowledgement on the report must be ticked.

Audit receipt (decision record)

The receipt card summarises the run you're acknowledging. The pill colour reflects state: amber "needs review" when the audit is present but not yet acknowledgeable, slate "pending" before the first audit, green "pass" once acknowledged.

Row	Source	What "done" looks like
GTM web container	Discover (saved primary GTM).	Container display name.
Primary GA4 property	Discover (saved primary GA4).	GA4 property display name.
Last audit	Report (Run audit / Refresh audit).	Local timestamp; "Not yet run" until you do.
Review Report	Report Step 3 bulk-save.	"N of M items acknowledged" (or "None" when there's nothing to review).

1 Acknowledgement states

The page's single guided section renders one of four headings depending on where you are. The status pill on the right of the step header tracks the same state.

Heading shown	What it means	What to do
Run an audit first	No audit run exists yet for this setup.	Use the inline link to Select GA4 and GTM — you'll loop through Discover and Report before returning here.
Resolve outstanding review items first	An audit run exists, but there's still an unacknowledged review tag, an outstanding no-core-events acknowledgement, or a failing primary-tag check without override.	The step body links to Review audit report →. Resolve what's outstanding in Step 2 / Step 3 there, then come back.
Acknowledge findings to unlock Build	All outstanding items are resolved. The receipt above is locked in once you click. The status pill shows "Pending".	Click Acknowledge findings. The status flips to Acknowledged with today's date and the Build link enables.
Findings acknowledged for setup	Already acknowledged. The status pill shows "Acknowledged on <date>".	Continue to Build, or click Clear acknowledgement if you need to revisit Discover / Report and re-record later.

What clicking Acknowledge findings does

Clicking Acknowledge findings stamps the audit run with an approval timestamp. The page re-renders with the Acknowledged status, the bottom nav unlocks, and the sidebar's downstream stages (Build, Cloud, Connect, Publish, Go Live) stop blocking navigation. None of this touches GTM, GA4, or Cloud resources — it's purely a local checkpoint.

Clicking Clear acknowledgement (the button label flips after you've acknowledged) removes that timestamp. The downstream stages lock again until you re-acknowledge.

Acknowledgement is also cleared automatically when an upstream input changes:

Un-acking a review tag on Review Report (the Save handler clears the acknowledgement if the new set is a strict subset of the old one).
Un-toggling the no-core-events acknowledgement on Review Report Step 2.
Un-toggling the primary-tag override on Discover Step 4.
Re-running the audit (Refresh audit on Report Step 1) — a new audit snapshot replaces the acknowledged one, so the acknowledgement falls off with it.
Changing either primary binding back on Discover — downstream audit state is reset along with the cascade.

What this acknowledgement unlocks

Build — Server GTM Container + Test GA4 Property pages become navigable. The bottom-of-page link Build: Server GTM → goes live the moment acknowledgement lands.
Cloud — GCP Project + Tagging Services + Tagging Endpoint pages become navigable (still gated by Build progress).
Connect — Web Container + Server Container roles and checks become navigable (still gated by Build + Cloud).
Publish, Go Live — unlock progressively as their own prerequisites land.

Acknowledging doesn't bypass any of those stage prerequisites — it just stops the audit gate from holding them all back at once.

After go-live

Once the setup is live, this page is read-only. The receipt is preserved as the setup record, and the page copy explains whether the acknowledgement was on the receipt at the time of go-live (or, if not, notes that it wasn't recorded). For ongoing review post-live, use the Changes and Health surfaces in the sidebar rather than coming back here.

Common errors & failure modes

Symptom	Likely cause	Where to fix
Page shows "Resolve outstanding review items first" and no Acknowledge button	An upstream acknowledgement is missing — usually an unacked review tag, the no-core-events acknowledgement, or a failing primary-tag check.	Use the inline Review audit report → link; work through what's outstanding, save, return.
Page shows "Run an audit first"	No audit run exists yet for this setup. Either it's never been run, or a Discover primary-binding change wiped the previous run.	Follow the link to Select GA4 and GTM, save selections, then Run audit on Review Audit Report.
Build link at the bottom is still greyed out after I clicked Acknowledge findings	The acknowledgement is committed server-side immediately, but stale browser state can mask it.	Refresh the page. If the status pill still shows Pending, the click didn't land — click again and watch the network panel.
Acknowledgement disappeared on its own	An upstream input changed and auto-cleared it: a review tag un-acked, no-core-events un-acked, primary-tag override un-ticked, or the audit was re-run.	Re-establish the upstream acknowledgement on Review Audit Report (or accept the new audit snapshot), then click Acknowledge findings again here.
Page is read-only and says "not recorded in the setup receipt"	Setup went live without an active acknowledgement on the receipt. This is informational, not actionable.	Use Changes and Health to review post-live state; the audit receipt is preserved as historical context.
Clear acknowledgement doesn't appear — only the Acknowledge button	You haven't acknowledged yet, so there's nothing to clear.	Either click Acknowledge findings, or, if you intended to revoke, the wording flips after the first acknowledgement.

Next step

Acknowledgement unlocks the Build stage. The bottom-of-page link Build: Server GTM → activates the moment the audit is acknowledged. Continue to Build — Server GTM to start preparing the server-side GTM container.