Repair a Pulse consent finding
Last updated: November 20, 2026
Start with Review details in the alert. Check the affected page, rule, method and observation time. For a current page-source finding, use the source rule catalog, repair the affected template and rescan the same URL. If a page was unreadable, investigate the recorded access or availability reason first.
The visitor-scenario steps below apply when an earlier finding identifies a browser observation, or when you independently test actual behavior. Use the recorded action and region when available. The same steps apply to CYBEXO, another CMP or a custom integration.
Before you change anything
Section titled “Before you change anything”- Use an authorized test session on the exact affected page. Preserve the report and reproduce its visitor scenario; start with a fresh browser profile for first-choice tests.
- Open the browser’s Network and Application/Storage panels. Look for the reported category of new storage or collection activity and its timing. Use request initiators, tag-manager preview and your installation records to locate the script, plugin or integration responsible. A retained cookie alone does not prove it was used again.
- Check all installation paths: theme snippets, tag managers, CMS plugins and embedded integrations can load the same consumer independently. Fix the responsible path and remove unintended duplicates. Keep security protections in place.
- Make and publish the smallest correction, then test both the refused and permitted states. Do not force a granted state, disable the failing check, or hide activity from the scanner to obtain a passing result.
Before choice
Section titled “Before choice”Rule: consent_before_choice. Covered activity occurred before the required visitor choice.
- Put the consumer behind the appropriate consent gate before it can initialize, write identifiers or send covered data. A visible banner or a default command alone does not block an independently loaded script.
- Keep the gate closed while consent is loading, unavailable or awaiting a decision. Use your CMP’s documented state API and lifecycle events; do not infer a grant from the banner disappearing.
- Audit direct scripts, tag-manager triggers and plugin-generated tags for paths that bypass the gate.
- Verify: in a fresh session, wait without choosing. The reported covered activity must remain blocked. Make the relevant positive choice and confirm that the intended consumer can then operate.
After rejection
Section titled “After rejection”Rule: reject_respected. The rejection was not enforced for covered activity.
- Connect the completed rejection action to the affected category’s actual tag and storage controls. Confirm that later page events, timers and plugin hooks consult the denied state.
- Remove unconditional startup paths or callbacks that overwrite a rejection with a grant. A new collection event after rejection matters; an existing stored identifier alone is not proof of new collection.
- Verify: start fresh, reject, then repeat the page action that produced the finding. Confirm no new covered activity and reload to verify that the rejection remains effective. Test acceptance separately to check that the repair has not simply broken the consumer.
After acceptance
Section titled “After acceptance”Rule: accept_respected. A supported accepted choice did not propagate as expected.
- Confirm that the completed action saves a valid choice and that the consumer receives the resulting permitted state. Check errors in saving, state updates and tag initialization.
- Use the documented consent event to start or release the consumer once, when its category is actually granted. Do not grant other categories as a workaround.
- Verify: start fresh, accept the relevant category and perform the supported action. Check actual permitted behavior, not only a queued command. Confirm no duplicate initialization and repeat the refusal test.
Granular choices
Section titled “Granular choices”Rule: granular_respected. A saved category choice did not preserve the categories left unselected.
- Check category-to-consumer mapping. An Analytics grant must not become an advertising grant, and an advertising choice must not automatically grant a separate Analytics preference.
- Ensure the consumer reads the saved, validated state after Save, including denied categories. Opening preferences or changing an unsaved draft is not a completed choice.
- Verify: grant one supported category while refusing the other, save and trigger the relevant behavior. Confirm only the permitted category operates. Repeat with the opposite selection and after reload.
Saved choice
Section titled “Saved choice”Rule: choice_persistence. The tested choice was not restored safely on reload.
- Check that the completed choice is saved through your CMP’s supported mechanism and restored before covered consumers run. Inspect domain/path settings, delivery failures, duplicate initializers and startup code that replaces saved choices with defaults.
- Keep covered consumers blocked while saved consent is being validated. Do not repair this by copying or inventing consent records in browser storage.
- Verify: save a rejection and reload; it must remain enforced. Repeat with a permitted choice and a mixed choice. Reopening and cancelling an unsaved edit must not change the saved decision.
Withdrawal
Section titled “Withdrawal”Rule: withdrawal_respected. Covered activity continued after the visitor withdrew the relevant permission.
- Keep an accessible privacy choices control on the page. Connect a completed withdrawal to the affected consumers immediately, including future timers and manual events.
- Use the consumer’s supported stop/disable mechanism. Removing its script element does not unload code that has already executed. If the integration requires a page reload, complete consent saving first and verify the next denied page; account for unsaved work on your site.
- Verify: grant the relevant category, confirm the consumer starts, reopen privacy choices, withdraw and save, then repeat the activity. Separate requests already in flight from new activity after withdrawal. Check the next denied reload too.
- Withdrawal governs subsequent activity. This check does not establish deletion of historical server-side data or require every pre-existing cookie to disappear.
Implementation-specific examples
Section titled “Implementation-specific examples”Use only the example that matches the affected installation:
- CYBEXO Web: installation and privacy choices and the public consent-state API.
- One direct GA4 destination: Basic/full-off publisher gate, including its supported scope and withdrawal handling.
- GA4 through GTM: Basic Analytics gate and verification. An additional consent check alone does not create a later trigger for a previously blocked tag.
- Google Consent Mode: default, update and effective-state validation. Basic and Advanced implementations have different behavior; a Google command queue is not proof of effective state or collection.
- Google tag gateway: gateway remediation only when that delivery path is in use. A baseline consent finding does not imply gateway use.
- TCF: TCF API validation for a requested TCF check. TCF absence alone is not a failure of an ordinary website.
- Another CMP or consumer: use that provider’s documented consent integration and repeat the same affected scenario. CYBEXO is not required for a site to pass the technical checks.
Incomplete checks
Section titled “Incomplete checks”An incomplete check is an observation gap, not a proven consent violation. Review its reason and the affected page before changing consent settings.
- Check page availability, redirects, robots rules, essential dependency failures and permitted scanner access. Restore authorized inspection without broadly disabling access controls or CSP.
- Check whether the required controls and visitor journey are supported. An opt-out notice alone is not a failing implementation; an unsupported interface can leave required observations incomplete.
- Retry after a temporary scanner interruption. A timeout does not establish that the site failed. Keep any separately proven failure visible while the remaining observations are unavailable.
Verify recovery
Section titled “Verify recovery”For a source finding, publish the repair and rescan the affected page and rule. For a browser finding, repeat the recorded visitor scenario and retain the new interaction evidence. A source scan alone cannot establish recovery of a browser finding. The earlier evidence keeps its original method and time.
Managed monitoring closes an observed finding only after two distinct complete, comparable passing observations meet its recorded recovery requirements. An incomplete job cannot supply recovery credit. Where country-specific recovery is recorded, a pass in a different country does not clear the earlier country observation, and all recorded failure obligations must be satisfied. Changes to the inventory or verification context can prevent comparability; an incident that remains open is not automatically proof that the attempted repair failed.
If the issue remains, share the authenticated report with your authorized developer or use CYBEXO support. Provide the affected page, rule, tested action and deployment revision. Do not send cookie values, authentication tokens or private visitor data. Pulse results do not confer Google or IAB certification.