What the analytics consent switch controls
Performance and behavior events start from an explicit analytics choice. The gate lives in the client path, not only in banner copy.
Consent copy matters only when it matches the code path behind it. On this site, the Web Vitals reporter reads the stored analytics choice when it mounts. If the value is not accepted, the reporter returns before it imports the measurement library or posts a metric.
Other optional behavior signals use the same boundary. Funnel events, passive interests and automatic audience resolution check analytics consent before they send or read those signals. An explicit persona choice is different: it is a setting the visitor selected, so it can change the view without creating a passive profile.
This is a narrow promise, not a claim that the browser makes no requests before consent. Requests needed to render the site, record the consent choice or submit a form have separate purposes. The useful check is specific: compare the analytics calls in the network panel before and after the choice, and keep the unconsented experience complete.