Does Amplitude tracking fire before Accept?

Not legal advice

This guide explains how to observe Amplitude browser analytics and any related server or export sends relative to Accept and Reject. It is not legal advice, not an Amplitude project, SDK, or Taxonomy setup tutorial, 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. Observation is not counsel permission.

Last updated September 29, 2026. The before-Accept audit owns the general first load. The Reject leftovers guide owns a Reject failure. The pre-consent checklist owns the pass order. The marketing-pixels FAQ owns the wider pixel question. The party-label guide owns first-party versus third-party names. Mixpanel and Segment are the sibling checks for a browser SDK plus downstream fan-out. This page stays on Amplitude.

Short answer

Amplitude often loads through a browser analytics SDK, and many setups also send events from the server or from export and pipeline jobs. A cookie consent audit asks whether Amplitude cookies, storage, or requests to cdn.amplitude.com, api2.amplitude.com, api.amplitude.com, or related hosts appeared before Accept, and whether Reject All stopped them.

Server or export paths can still send when the browser SDK is delayed. Treat banner text that says analytics or marketing is off as a claim. Falsify it on a clean visit. Capture Amplitude-related hosts and cookies on Fresh. Repeat after Reject. Note any post-Reject fan-out. Host names are examples of where a browser test can look. This page does not tell you which host to block, and it does not say which Amplitude cookies are essential.

Downstream sends are harder to see from DevTools alone. Ask engineering for Amplitude User Lookup or delivery logs labeled by consent state when the browser pack is clean and Amplitude still shows events. First-party versus third-party labeling still applies when Amplitude cookies sit on your domain. ConsentProbe can produce Fresh and Reject packs with request, cookie, and screenshot links.

Browser SDK and export sends

Three layers get mixed when someone says Amplitude is off because the browser SDK waits for Accept. Separate the SDK from the export send. Write the finding as an Amplitude host before Accept, or a host after Reject. Leave permission with counsel.

Fresh and Reject on the browser

These steps compare a claimed wait-for-Accept state with cookies and requests. They do not create an Amplitude project, install an SDK, or edit a Taxonomy. The before-Accept audit and the pre-consent checklist hold the general method.

1. Use a clean profile. Load the storefront once. Do not click Accept.
2. Capture cookies, storage, and Network for Amplitude-related hosts, including cdn.amplitude.com, api2.amplitude.com, and api.amplitude.com.
3. Screenshot the banner state. Label the pack Fresh.
4. Open a new clean profile, or clear storage. Click Reject All. Navigate once more.
5. Recapture cookies and Network. Label the pack Reject. Compare it with Fresh and, if you ran one, with an Accept control.
6. Write one finding sentence per mismatch, such as an Amplitude cookie on Fresh, or the same host after Reject.

Exports when the SDK looks gated

A quiet browser SDK and a quiet export are different results. Server track calls, batch uploads, or warehouse syncs can still deliver events when the page delayed the SDK. An identify call on Fresh is one more row to label.

If Fresh and Reject look clean in DevTools and the Amplitude project still shows events, ask engineering for delivery logs tagged by consent state and timestamp. Each row should carry a label, Fresh or Reject or Accept, that you can line up with the browser pack.

Example of a storefront clue, not a customer capture: Fresh Network shows a request to cdn.amplitude.com before any banner click. After Reject and one more navigation, api2.amplitude.com is still there. Storage keys that include amp_ are clues to confirm in Application, not a complete cookie list.

This page does not walk through project creation, SDK install, Taxonomy, Cohort, or warehouse export config. The question to falsify is whether an export send happened on Fresh or after Reject. Mixpanel and Segment use the same browser-versus-downstream split on their own pages. HubSpot, Klaviyo, and GA4 are the other named-tool cousins. This page stays on Amplitude.

When checking Amplitude hosts gets slow

Checking Amplitude hosts across templates by hand takes a long time. 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 install or configure Amplitude, does not install a CMP, and does not issue a certificate. A free US-baseline scan is not an EU or California legal conclusion.

FAQ

Limits of this page

This page tells you how to check Amplitude browser cookies and hosts on Fresh, how to repeat the check after Reject, and why a gated SDK leaves exports untested. It is not legal advice, not an Amplitude setup guide, 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.

Related guides

Open the before-Accept audit for the general first load, the Reject leftovers guide when Reject still tracks, the pre-consent checklist for the pass order, the marketing-pixels FAQ for the wider pixel question, and the party-label guide for domain names. Mixpanel, Segment, HubSpot, Klaviyo, and GA4 are the sibling checks.

• How to run a cookie audit before Accept
• Reject All still tracking
• Pre-consent audit checklist
• Does Reject All stop marketing pixels?
• First-party vs third-party cookies
• Does Mixpanel tracking fire before Accept?
• Does Segment tracking fire before Accept?
• Does HubSpot tracking fire before Accept?
• Does Klaviyo tracking fire before Accept?
• Do GA4 cookies fire before Accept?
• GTM tags before Accept
• Cookie consent evidence pack
• Free US-baseline vs paid EU and California
• CMP claims vs runtime evidence
• Cookie audit hub
• ConsentProbe methodology
• Pricing and listed regional products