Consent

How iReveal respects consent: your banner decides, capture is first-party, and opt-outs travel.

iReveal is consent-aware by design, and the design is simple: your consent banner decides; iReveal obeys.

The tag loads on consent

The iReveal tag is gated by your consent management platform like any analytics tag: wire it to load only after the visitor consents, using your CMP's consent-granted callback. No banner interaction, no capture. The wiring pattern is the same as the platform pixel's; see Events and pixels.

First-party, in your environment

Capture is server-side and first-party, under your domain and your policies, and with warehouse deployment it runs inside your own environment, so visitor data does not leave your control to be resolved.

Opt-outs travel

A visitor who opts out stays opted out downstream: suppression and consent flags ride with the record into scoring, audiences, and any activation. Deletion and access requests follow the platform's DSAR support; see GDPR, CCPA and DSAR.

Regional rules differ, and your legal team owns the consent policy. iReveal's job is to make the compliant configuration the easy one: one tag, gated by your banner, honored everywhere downstream.