Checklist

How often should I re-run a cookie consent audit?

Run the free scan

Retest cookies before Accept after new pixels, theme or app changes, CMP switches, and seasonal tags. Observation cadence, not a legal mandate.

In brief

Re-run a cookie consent audit when the storefront tracking surface changes. Useful triggers include a new pixel, a theme or app change, a CMP switch, and seasonal campaign tags. A prior Fresh and Reject pack goes stale when the scripts that produced it are no longer live. ConsentProbe can store a new pair. A free US-baseline scan is not an EU or California legal conclusion. This page is an observation cadence, not a statutory re-audit mandate, and not legal advice.

This FAQ explains an observation cadence for re-running cookie consent audits after storefront changes. It is not legal advice, not a statutory re-audit mandate, not a counsel calendar, and not a GDPR, ePrivacy, CPRA, or other compliance certificate. ConsentProbe reports are technical observations of what fired. They do not say what counsel would allow, and they do not say how often counsel requires a formal review. Observation is not counsel permission.

Last updated September 28, 2026. The testing hub owns which test to run next. The pre-consent checklist owns the pass order. A Reject or GPC fix is retested on this page. A vendor migration is compared on the CMP claims versus runtime evidence page. This page answers when a prior Fresh and Reject pack goes stale.

Short answer

Re-run a cookie consent audit when the storefront tracking surface changes. Useful triggers include a new marketing pixel or tag, a theme or app change, a CMP switch or a major banner config change, and seasonal campaign tags that only exist for a few weeks. This page does not set a statutory interval.

A prior Fresh and Reject pack goes stale when the scripts, apps, or consent wiring that produced it are no longer the ones live on the storefront. Treat cadence as observation hygiene. Run Fresh and Reject again after the change, keep the evidence pack, and open the hub or the checklist when you need which test is next.

After a Reject or GPC fix, retest the path you fixed on this page. After a CMP migration, compare the new claims with runtime on the CMP claims versus runtime evidence page.

Triggers that stale a prior pack

A quiet calendar and a changed storefront are different facts. Write the reason as the change you shipped, then rerun Fresh and Reject. Leave any formal review schedule with counsel.

Swipe to see more

Storefront changes that can stale a prior Fresh and Reject pack.
TriggerWhy Fresh and Reject can go staleWhere to open next
New marketing pixel, tag, or embedNew hosts and cookies can appear before AcceptBefore-Accept audit and the marketing-pixels FAQ
Theme, app, or plug-in changeScripts can inject outside the old gate pathPre-consent checklist and the Shopify checklist
CMP switch or major banner configNew claims are not the prior runtime proofCMP claims versus runtime evidence
Seasonal or campaign tagsTemporary scripts exist only for a windowTesting hub, for which pass is next
After a Reject, GPC, or pixel fixYou need proof the fixed path holdsGPC-on passes when Sec-GPC is present and the network no longer matches GPC-off.

Why a fixed calendar alone is weak

A quiet month with no tag changes may not need a new pack. A loud week with three new pixels does. The trigger is the change, not a date this page invents.

An Accept-only capture, or one old Accept file, does not prove Fresh and Reject still hold after a change. The Reject All still tracking page covers that split. This page does not paste it.

CMP marketing copy and auto-block claims change with vendor versions. Runtime is the check. The CMP claims versus runtime evidence guide owns that comparison.

Counsel may set a formal review schedule. This page does not invent that schedule. Ask counsel for mandate questions. Observation is not counsel permission.

Fresh and Reject after a trigger

These steps refresh the pack after a named change. They do not install a CMP, rank vendors, or set a legal calendar. The testing hub and the pre-consent checklist say which pass is next. This page holds the rerun after a Reject or GPC fix. A CMP migration is compared on the CMP claims versus runtime evidence page.

  1. Note the change, whether it is a pixel, a theme or app, a CMP, or a campaign, and write the date.
  2. Use a clean profile. Load the storefront once. Do not click Accept. Capture Network, cookies, storage, and the banner. Label the pack Fresh.
  3. Open a new clean profile. Click Reject All. Navigate once. Recapture the same layers. Label the pack Reject.
  4. Compare the new pair with the last pack for the same URL. Write one finding sentence per new or returned mismatch.
  5. Keep the evidence pack with the change note.
  6. If you just fixed Reject or GPC, rerun Fresh and Reject on the same URL. If you just switched CMP, compare the new claims with runtime on the CMP claims page. For which test is next, open the hub or the checklist.

When the last pack is the only file

Waiting for a calendar reminder while tags keep shipping leaves Fresh and Reject unproven. After a trigger, run a browser cookie audit before Accept. ConsentProbe runs Fresh and Reject on the storefront URL. Each finding stays tied to a request, a cookie, or a screenshot.

Use the free US-baseline visit when you want the report format. Use paid EU or California scenarios when those regions are the claims. The free versus paid guide draws that line. ConsentProbe does not set a legal audit schedule, does not install a CMP, and does not issue a certificate.

FAQ

How often should I re-run a cookie consent audit?

After a concrete storefront change, such as a new pixel, a theme or app change, a CMP switch, or seasonal tags. This page does not set a statutory interval.

Do I need a new audit after switching CMP?

Yes. Retest claims against runtime on the CMP claims versus runtime evidence page.

Is a quiet month with no tag changes a reason to skip?

Often the prior pack still describes the live surface. Retest when something changes, or when counsel asks for a new look.

Does this page set a legal re-audit mandate?

No. This is an observation cadence. Ask counsel for mandate questions. Observation is not counsel permission.

What if I just fixed Reject All?

Retest the fixed path on the same URL. Keep the evidence pack.

Is this legal advice?

No. These are technical observations. Observation is not counsel permission. ConsentProbe does not replace counsel, and it does not install a CMP.

Limits of this page

This page tells you which storefront changes stale a prior Fresh and Reject pack, and which published guide to open next. It does not rewrite the testing hub or the pre-consent checklist. It is not legal advice, not a statutory re-audit mandate, and not a certificate. Observation is not counsel permission. ConsentProbe reports stay tied to requests, cookies, and screenshots. A free US-baseline scan is not an EU or California legal conclusion.

Open the testing hub for which test is next and the pre-consent checklist for the pass order. A Reject or GPC fix stays on this page. After a vendor migration, open the CMP claims page. The before-Accept audit and the evidence-pack page cover the first load and how to file it.

Sources

These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.

Save a US-baseline technical record

After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.

How often should I re-run a cookie audit? | ConsentProbe