Consent and privacy

The tag never shows a banner. On a site we do not own that would be presumptuous and usually a duplicate, so it reads whatever consent tool you already run and reports what it finds.

vibiz.setConsent({ advertising: true });

Without advertising consent, the tag never sends contact details from the browser. Traffic analytics and traits keep working: traits stay in Vibiz and never reach an ad platform.

A form reported from a server is different. Someone who types their email or phone into a form wants to be contacted, so when a server sends an event with contact details and no advertising consent, the readable email, phone and name are kept for your CRM, and nothing else is. What reaches Meta or Google is decided per value: only a contact detail that arrived with advertising consent is ever uploaded, and without consent no matching digest is stored at all. The @vibiz/analytics/node package still sends contact details only with advertisingConsent: true.

Meta's _fbp cookie

_fbp is Meta's browser id, an advertising cookie. The tag reads it, or creates one in Meta's format when your site has no pixel, only once advertising consent is granted: through setConsent({ advertising: true }), or a Google consent mode update with ad_user_data: 'granted'. With consent denied, or with no signal at all, the tag neither writes _fbp nor reads one your own pixel set, and events go out without it. It is checked on every event, so the first event after consent is granted carries it.

Keeping pages and values out

The page URL, the referrer and the text of clicked elements are sent as they are unless you say otherwise. excludePaths, redactPatterns, redactUrl, captureText: false and beforeSend hold back whole pages, mask values such as a wallet address or a token, or drop an event before it leaves; see Install.