Skip to main content
Add data-consent="required" to the installation tag. Then pass consent changes to Dynamite:
Before a grant, Dynamite does not initialize visitor memory, fetch configuration, make decisions, or send measurement. The script itself still downloads; let your consent manager load the tag if that must wait too. consent(false) stops the runtime, restores original content, discards pending tracker events, and clears visitor/enrichment storage on the site. It keeps the denial so the next page does not restart personalization. Already-sent events remain on the server. This method does not erase account data.
The consent choice is stored in localStorage['dynamite:consent']. A remembered grant allows later page loads to start. Without the required attribute, startup is immediate unless a denial was stored.Withdrawal removes localStorage keys starting with ion:visitor or ion:enrichment, sessionStorage keys starting with ion:, and the dynamite_enrichment cookie. Check for naming conflicts on your origin.Visitor memory can fall back to in-memory storage. Required consent depends on localStorage; blocked storage can prevent a grant from starting the runtime.See Visitor memory for profile storage and custom profile sources.