Does Attentive tracking fire before Accept?

Not legal advice

This guide explains how to observe Attentive browser and on-site identity activity, plus any related server or API sends, relative to Accept and Reject. It is not legal advice, not an Attentive campaign, journey, SMS, or creative 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 30, 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. Braze and Klaviyo are the sibling checks for on-site messaging plus a server path. This page stays on Attentive.

Short answer

Check Attentive cookies, storage, and network requests before Accept. Do not assume SMS or server APIs are off because the browser SDK is gated. A cookie consent audit asks whether hosts such as cdn.attn.tv, events.attentivemobile.com, or attn.tv appeared before Accept, and whether Reject All stopped them.

Server or SMS paths can still send when the browser SDK is delayed. Treat banner text that says marketing or personalization is off as a claim. Falsify it on a clean visit. Capture Attentive-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 say which Attentive cookies are essential, and it does not walk SMS campaign copy.

Downstream SMS or API sends are harder to see from DevTools alone. Ask engineering for Attentive subscriber or event delivery logs labeled by consent state when the browser pack is clean and Attentive still shows sessions or message triggers. First-party versus third-party labeling still applies when Attentive cookies sit on your domain.

Browser SDK and SMS API

Three layers get mixed when someone says Attentive is off because the browser SDK waits for Accept. Separate the SDK and on-site identity script from server or SMS orchestration. Write the finding as an Attentive host before Accept, or a host after Reject.

Fresh and Reject on the browser

These steps compare a claimed wait-for-Accept state with cookies and requests. They do not create an Attentive journey, write an SMS template, or configure a signup unit. 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 Attentive-related hosts, including cdn.attn.tv, events.attentivemobile.com, and attn.tv.
3. Screenshot the banner state. Label the pack Fresh. Note an on-site signup surface if one renders before any click.
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 Attentive cookie on Fresh, or the same host after Reject.

SMS and API when the SDK looks gated

A quiet browser SDK and a quiet SMS or API path are different results. Server event posts and message orchestration can still run when the page delayed the SDK. Attentive's tag docs say to filter Network for events.attentive when a browser tag event is the question. That filter does not show a server SMS send.

If Fresh and Reject look clean in DevTools and Attentive still shows sessions or triggered sends, 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 cdn.attn.tv before any banner click, with an empty cookie delta. After Reject and one more navigation, events.attentivemobile.com is still there.

This page does not walk through workspace creation, journey build, SMS template, or signup-unit config. The question to falsify is whether a server, API, or SMS send happened on Fresh or after Reject. Braze and Klaviyo use the same browser-versus-downstream split on their own pages. This page stays on Attentive.

When checking Attentive hosts gets slow

Checking Attentive 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 Attentive, 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 Attentive browser cookies and hosts on Fresh, how to repeat the check after Reject, and why a gated browser SDK leaves SMS and API sends untested. It is not legal advice, not an Attentive campaign 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. Braze, Klaviyo, and Meta 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 Braze tracking fire before Accept?
• Does Klaviyo tracking fire before Accept?
• Meta Pixel and CAPI 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