When to use this
Go Live is Step 7—the final activation after all required setup steps succeed. On Pro that means Step 1 Connect Site, Step 2 Install Script, Step 3 Consent Banner, Step 5 Legal Pages, and Step 6 Runtime Verification plus this step. On Growth the wizard can also require Step 4 Tracker Blocking before Step 6 unlocks. Until you go live, configuration may exist but the product treats setup as not fully complete for compliance milestones.
Use this step when stakeholders sign off on banner copy, policies, and blocking tests (Growth). Activating early without passing runtime verification can create a false sense of security while trackers still leak. The Go Live panel explains prerequisites and stays locked until every required step for your plan shows completed.
After go live, monitor Protection and Runtime Health continuously; compliance is ongoing, not a one-time toggle.
Marketing launches (new landing pages, A/B tests) should include a checklist item to confirm the runtime snippet is in the experiment variant template—not only control.
goLiveAt timestamps help auditors correlate enforcement start dates with campaign analytics; export the value from setup summary or site settings when responding to DPIA questionnaires.
Step-by-step instructions
- Open Setup → Step 7 · Go Live and review the readiness checklist—all required prior steps should show completed.
- Read any warnings about stale heartbeats or unpublished drafts and resolve them before continuing.
- Click Go Live to confirm activation.
- Acknowledge that visitor-facing enforcement is now tied to your published configuration snapshot.
- Record goLiveAt timestamp shown in dashboard for internal change logs.
- Notify your team that further banner edits require republish and may need re-verification for major enforcement changes.
- Run a post-activation scan from /scanner or dashboard scans to compare public vs protected views if on Pro.
- Schedule a weekly review of Runtime Health cards for heartbeat gaps or blocking anomalies.
- Add go-live date to status page internal documentation for support teams.
Expected result
goLiveAt is set on your site record, Step 7 marks complete, and setup progress reaches 100% (6 required steps on Pro, 7 on Growth). The page shows Go Live Complete with live status for runtime, banner, legal pages, blocking (Growth), and protection. Visitors on production receive consent and enforcement per published settings.
Billing and plan limits still apply—go live does not upgrade features. Growth-only capabilities remain unavailable until you are on Growth.
Post go-live, add a calendar reminder for 30-day rescans and heartbeat reviews—initial success does not prevent later template regressions when agencies edit head markup without telling engineering.
Troubleshooting
Go live button disabled
Open each prior step and read the reason string on locked steps. Most common gaps: unpublished banner, unsaved enforcement mode (Growth), failed legal verify (Growth), or runtime verification heartbeat stale. Fix the earliest incomplete required step for your plan first.
Activated but scans still show issues
Public scanner sees the open web, which may differ from logged-in previews. Wait for cache TTL, confirm script on all locales, and compare owner diagnostics on Pro for private telemetry.
Need to pause protection
Removing the script pauses enforcement but is disruptive. Prefer maintenance windows and republish toggles. Document pauses for compliance audits; consult counsel before leaving sites unprotected long term.