Growth plan features

When to use this

Growth targets agencies, multi-brand operators, and compliance-minded teams needing depth beyond Pro. It includes everything in Pro plus maxActiveSites of three, Step 4 Tracker Blocking, advanced enforcement tooling, advancedAppearance, privacyEntryCustomization, localization, advancedTrackerBlocking, consentReplayVerification, configurationSummary, exportConfig, and multiSiteManagement. The full setup wizard shows seven numbered steps (1–7); Pro counts six required steps and treats Step 4 Tracker Blocking as optional. Growth also enables multiRegion, advancedAnalytics, and edgeRuntime capabilities in entitlements.

Upgrade from Pro when you need pre-consent tracker blocking, editable custom blocking rules, multi-language consent strings, multiple protected websites, or JSON export of CMP config for staging pipelines.

Stripe bills Growth as a separate price id—use dashboard billing to preview proration when upgrading mid-cycle.

Agencies often keep one Growth account and map each client domain to a separate site row with its own consent publish pipeline. configurationSummary and exportConfig support change-control: diff draft versus published JSON before handing releases to client engineering.

consentReplayVerification is the deepest technical check short of manual QA—it watches whether marketing tags remain blocked before accept and fire only after the visitor grants marketing category. Pair it with runtime diagnostics when clients dispute tag behavior.

edgeRuntime and multiRegion flags in entitlements support higher-traffic architectures—confirm with support if your deployment uses regional edges beyond standard Pro delivery.

Portfolio owners should align Growth renewal dates with client contracts to avoid paying for idle site slots between projects.

Step-by-step instructions

1. Confirm Pro is active or upgrade directly from Free via Growth price on /pricing.
2. Complete checkout; verify GROWTH plan on Account billing.
3. Add additional verified sites up to 3 protected websites under Sites management.
4. Configure advanced appearance and privacy entry per site in Consent workspace.
5. Set up localization strings for EU markets with automatic locale detection where supported.
6. Author custom tracking rules in Trackers; save and publish policies.
7. Use configuration summary to diff draft vs published before releases.
8. Run consent replay verification after material rule changes.
9. Export config JSON for backup or infrastructure-as-code workflows if needed.
10. Label each site in internal runbooks with Site ID and goLiveAt timestamp for audit trails across client portfolios.
11. Review advancedAnalytics cards if your dashboard exposes traffic-weighted enforcement metrics for high-traffic properties.
12. Document which clients occupy each of the three site slots to avoid accidental overwrites.
13. Run consent replay on highest-traffic client after bulk rule import.
14. Export JSON configs quarterly for disaster recovery.

Expected result

Multiple properties run independent consent configs under one account. Advanced diagnostics explain per-domain blocking. Teams reduce regression risk with configuration summary and replay tools.

Site replace limitations on Pro lift to true multi-site switching without archiving your only slot.

Agency playbooks should standardize naming conventions for Site IDs in client runbooks and restrict who may publish consent—accidental publish on wrong site row is a common multi-site incident.

Troubleshooting