Documentation / Connect your site
Analytics consent and CMP
Connect the SDK to your consent manager and measure consent separately from experiment conversion.
Step by step
- Have your developer configure the CMP to allow the kopair tag only after analytics consent. The SDK does not provide a consent banner. Verify the deployed consent integration rather than assuming that installing the tag connects it to your CMP. Test accepting, denying and withdrawing consent.
- Open Sites → CMP consent. Import daily UTC aggregates from your CMP manually or through its authenticated push integration.
- Eligible must be at least consented + denied. Keep push credentials on your integration server; rotate or revoke a token in the dialog when needed.
A WordPress cookie-banner plugin and a Tilda consent banner may expose different callbacks. Map the actual banner state to the SDK, rather than treating a button with the label “Accept” as universal consent.
How to verify
With a correctly gated tag, the SDK does not observe visitors before consent, so it cannot provide the denominator for consent rate. Missing CMP totals must not be interpreted as zero denials. Confirm denial leaves the original site and sends no analytics.