Preview, publication, and access
Design editing and CMP publication are separate actions. Preview new source without changing the release visitors receive.
Draft to Live
- Edit/synchronize files at the owning scope.
- Select the design on a compatible framework and save its draft configuration.
- Open Preview: it uses current source and configuration.
- Review source, design, content, configuration, and target stage in Dashboard publication review.
- Publish: the platform freezes the complete compiler input, including shared partials, into an immutable customer-design version. The framework snapshot references that exact release.
- Verify the installed CMP on the intended site/stage. Later source changes stay drafts until explicitly published again.
Shared source may have several consumers. Editing it does not silently republish all of them: review/publish each affected consumer. A full design freezes every authored view, including unchanged views. A custom banner freezes only the customer notice source and separately records the exact official preference-center/trigger version reviewed with it. Components and CSS stay separate between those bundles.
Maintained secondary views
A published banner uses its frozen official secondary version until an eligible update is released. Official updates follow the existing clean-framework propagation rules: dirty customer drafts are excluded, version pins are respected, and Staging-enabled apps retain their review/promotion boundary. Your next explicit publication can also pick up a newer official version. Switching the active view replaces its CSS while keeping the selected theme, so notice rules do not accumulate in preferences.
Pro’s shared-design pin applies to the official secondary design in banner mode. If pin access ends, it follows the same release behavior as an official full design. The add-on does not grant version pinning or Staging to Starter.
Stage and framework boundaries
Free/Starter publish directly to Live; Pro can use optional Staging and promotion. The add-on does not grant Pro's staging or controlled-update features. During public beta, ordinary TCF supports editing/preview but remains blocked from general Staging/Live publication. A separately authorized verification app is an operational exception, not an add-on benefit.
Access lifecycle
| State | Custom authoring/delivery |
|---|---|
| Evaluation and grace | Granted without purchased ownership |
| Healthy Starter/Pro with add-on | Enabled subject to role/configuration |
| Paid past-due/grace | Retained until suspension |
| Add-on removed or access suspended | Source retained, authoring/custom delivery unavailable, system design serves |
| Eligible access restored | Retained designs available; review assignment and release status |
Billing changes refresh after provider confirmation. Clicking Add/Remove is not immediate authorization. Publishing cannot create a pending custom release while access is inactive: restore access and review/publish. Existing immutable releases and unpublished edits are separate states.
Verify the result
- Check notice, preferences, and enabled reopening control on the installed CMP.
- Accept, reject, save granular choices, reopen, and reload; verify persistence and consent-dependent behavior.
- Cancel a staged preference edit and confirm the prior decision remains.
- Check enabled locales, RTL, keyboard, zoom, small viewport height/width, and light/dark appearance.
- Check configured services including uncategorized entries and required purpose/vendor/opt-out disclosures.
- Edit a draft after publication and verify Live retains the release until explicitly published again.
- Inspect target and diff before promotion or restoring an available prior snapshot. A source save or customer CLI push is not a rollback/deployment action.
Correct source, configuration, access, or runtime failures and repeat the relevant check. See troubleshooting.