Skip to content
FRVR SDK

Consent

FRVR.consentProvider bridges to a Consent Management Platform (CMP) so you don’t have to integrate one per channel. Analytics, ads, and features all check it before doing anything that needs consent.

Configuration

Section titled “Configuration”

On web, pick a provider by name:

FRVR.config.consent = {
  providerName: 'tcfv2',   // or 'cookiepro'
  config: { /* CMP‑specific */ },
};

Native channels provide consent through their own host apps — you don’t need to configure anything.

Section titled “React to consent changes”
FRVR.consentProvider.onConsentChanged((consents, legitimateInterests) => {
  // consents: array of purposes the user allowed
  // legitimateInterests: array of purposes relied on by legit‑interest
  refreshAds();
});

Call at any time to let the CMP re‑prompt:

FRVR.consentProvider.consentToTerms();

Who uses it

Section titled “Who uses it”
  • Ads — each provider gets notified via FRVR.ads.setUserConsent(bool) when consent changes.
  • Analytics — tracker queues events before consent is known (up to 100), then dispatches or drops based on the result.
  • Features — feature flag fetches are consent‑aware.

If you opt not to configure a CMP, the SDK assumes no consent and refrains from sending sensitive events.