Independently verify RCS in Connecticut

The Connecticut test

Check how a browser opt-out reaches the deployed tag configuration. Compare a fresh Connecticut visit with and without a supported preference signal. Follow its result from the CMP through each mapped advertising tag, then test a reload with the saved preference.

Set expected behavior with your policy owner before testing. Business scope, data purposes, and exceptions affect that expectation. Use the Connecticut Attorney General: data privacy act as a policy reference; this procedure checks browser behavior and does not certify legal compliance.

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

Run the same paths from a verified visitor

1. Confirm routing. Record the browser exit and the regional rule RCS actually selected. Browser language, timezone, and a DevTools location override are not proof of IP-based routing.
2. 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.
3. Read the decision. Save the banner controls used, the category or purpose values, and any Consent Mode mapping. Use this installation’s documented readback.
4. 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 RCS’s saved state

Check RCS's TCF identity and the site's purpose mapping.

1. Record the RCS script or plugin version, configuration identifier, and published regional rule. Check the deployed site rather than a dashboard preview.
2. If this installation enables the IAB Transparency and Consent Framework (TCF), compare its returned cmpId with 218, the ID in Google's inventory. An absent TCF API may simply mean TCF is not enabled.
3. 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.

(() => {
  if (typeof window.__tcfapi !== "function")
    return { status: "TCF unavailable or disabled" };
  window.__tcfapi("addEventListener", 2, (data, ok) => {
    if (!ok || !data ||
        !["tcloaded", "useractioncomplete"].includes(data.eventStatus))
      return;
    console.log({
      cmpId: data.cmpId,
      expectedCmpId: 218,
      identityMatches: data.cmpId === 218,
      cmpStatus: data.cmpStatus,
      eventStatus: data.eventStatus,
      gdprApplies: data.gdprApplies,
      purposeConsents: data.purpose?.consents,
      purposeLegitimateInterests: data.purpose?.legitimateInterests
    });
    window.__tcfapi("removeEventListener", 2,
      () => {}, data.listenerId);
  });
})()

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.