Independent consent verification · state

Independently verify Mandatly in Oregon

To check Mandatly from Oregon, confirm the visitor’s regional rule, run fresh first-load, accept, and refusal paths, then compare the saved choice with cookies and requests. Keep the evidence so the same test can verify a deployed fix.

CookieTrail · Technical procedure · Sources reviewed 4 October 2026

Interactive example · no site is scanned

A saved rejection can still leave a tag running

Example policy: optional analytics must stay off after refusal. Change the evidence for a Mandatly visitor in Oregon and see what you can conclude. These values are teaching fixtures.

01 · REGIONRegional rule unverifiedAn exit location alone does not prove the CMP selected us-or.

02 · SAVED CHOICEOptional analytics: deniedMandatly readback after the example refusal.

03 · BROWSER ACTIVITYOptional analytics cookie appearsExample capture window: 10 seconds after the choice. Server-side processing is outside this fixture.

Change the example evidence

Visitor region and CMP rule verifiedSaved refusal readableCookies and requests capturedFix deployed: optional analytics stays off

Evidence incomplete

Verify the visitor region and selected CMP rule before judging this regional result.

Build your repeatable test plan

Public page URL

Test scope

Add a manual withdrawal test and browser signal testsRepeat after deployment

6 worksheet rows. First load, acceptance, and refusal each use fresh sessions. The worksheet records actual region, selected rule, expected policy, saved state, and observed activity.

Read the generated test plan

Independently verify Mandatly on https://example.com for a visitor in Oregon.
CookieTrail does not currently offer a verified Oregon state route. Use a separately verified Oregon browser exit for this procedure; US East or US West alone is insufficient.
Check browser preference signals and ordinary opt-out as separate paths. Compare signal-on and signal-off Oregon sessions and inspect advertising-purpose mappings. Repeat with a returning visitor. Keep any nonprofit or other business-specific policy decision in the expected-policy record.

Run these paths: first load, accept optional categories, reject / opt out. Use fresh isolated sessions for first load, accept, and reject; withdrawal uses its own earlier acceptance. Record the URL, deployed version, actual visitor region, selected CMP rule, expected policy, saved state, cookies, requests, and capture window. Use the installed CMP's documented readback; missing data is inconclusive. Do not equate a TCF applicability flag or a banner language with geography.

Compare saved choices with observed behavior against the team's stated policy. A request alone does not establish a violation; Google advanced Consent Mode may send cookieless requests. Do not assume browser evidence covers server-side tracking. Investigate mismatches in my repository and explain each finding with evidence. After I deploy a fix, repeat the same URL, regional rule, and paths, then compare both evidence sets.

CookieTrail can capture its supported country routes through its workspace/API/MCP. State/province routing, browser preference signals, and withdrawal require separate verified manual or external browser tests; do not claim those are built-in automated paths. This is a technical test, not legal certification.

Country-route capture is available for CookieTrail’s supported locations. Precise state/province routing, withdrawal, and browser preference signals need separate manual or external tests.

The Oregon test

Check browser preference signals and ordinary opt-out as separate paths. Compare signal-on and signal-off Oregon sessions and inspect advertising-purpose mappings. Repeat with a returning visitor. Keep any nonprofit or other business-specific policy decision in the expected-policy record.

Set expected behavior with your policy owner before testing. Business scope, data purposes, and exceptions affect that expectation. Use the Oregon Department of Justice: privacy law questions as a policy reference; this procedure checks browser behavior and does not certify legal compliance.

CookieTrail does not currently offer a verified Oregon state route. Use a separately verified Oregon browser exit for this procedure; US East or US West alone is insufficient.

Run the same paths from a verified visitor

Confirm routing. Record the browser exit and the regional rule Mandatly actually selected. Browser language, timezone, and a DevTools location override are not proof of IP-based routing.
Start clean. Use separate new sessions for first load, acceptance, and rejection or opt-out. Begin storage and network capture before page load; record the capture window and deployed version.
Read the decision. Save the banner controls used, the category or purpose values, and any Consent Mode mapping. Use this installation’s documented readback.
Compare and repeat. Compare observed tools with the expected policy, investigate a mismatch, and rerun the same URL, regional rule, and paths after deployment.

For this state, add separate browser preference-signal tests where your approved policy calls for them. Record the signal and resulting advertising permissions. A signal-on visit is a different test from clicking Reject; this guide does not assume every state has identical signal requirements.

Read Mandatly’s saved state

Record Mandatly's deployed configuration and saved category choices.

Record the Mandatly script or plugin version, configuration identifier, and published regional rule. Check the deployed site rather than a dashboard preview.
Use the installed product's documented readback or reopen its preferences panel to record saved values. This guide does not invent a native JavaScript API for the product.
Map each saved category or purpose to the site's actual tools. Compare those tools' storage and requests before and after the visitor's decision.

Compare state with observed activity

A saved denial can coexist with a tag that ran too early or never received the update. Trace the affected integration and its event timing. A network request alone does not prove a violation: Google’s advanced Consent Mode can send cookieless requests.

Unreadable state, unverified routing, or a missing capture makes the result inconclusive. Browser captures also cannot establish what a server-side integration does. Keep that investigation separate and compare evidence after the fix.

Common verification questions

Can I test Mandatly from my own country?

You can check that visitor’s configuration. To verify Oregon, use a visitor whose relevant geography and selected rule are confirmed. Compare it with United States to investigate regional differences.

Can Claude validate this setup?

Claude can inspect code and use browser or regional testing tools when connected to them. Give it the same paths and saved evidence across locations; ask it to repeat them after deployment. Use the international testing workflow.

Does this guide prove Mandatly works in Oregon?

It provides a procedure for your deployed site. The examples are illustrative; no customer site or vendor implementation was audited for this page. A supported route also does not establish that every CMP readback is automated.

Platform reference

Mandatly appears in Google’s CMP inventory or partner list. That listing is an identity reference, not a verdict on this site or jurisdiction.

CookieTrail is independent of the listed vendors. The library includes web-capable entries from the referenced inventories; it does not claim to enumerate every CMP on the market.