Cookie consent is about clarity and respect. When you give users control over how their data is used, you build trust, and gather better, more reliable insights in return.
How Iterate handles consent
Iterate doesn’t manage cookie consent directly for you. Instead, we recommend using the consent data you’re already collecting to decide who should or shouldn’t see a survey. You can do this by passing a user property to Iterate.
1. Capture consent in your app or site
If you already use a cookie consent tool (like Cookiebot or OneTrust), you likely have a flag available, something like analyticsConsent = true
or false
, based on the user’s selection.
2. Pass consent to Iterate
Once a user makes their choice, send that information to Iterate using the identify method in our SDK. For example:
Iterate('identify', {
external_id: currentUserId,
analytics_consent: analyticsConsent // true or false
});
Make sure this runs after both the consent decision and the Iterate script have loaded.
3. Target surveys based on consent
Within your Iterate survey dashboard, go to Targeting → Identify specific visitors. You’ll be able to filter participants based on the consent value you passed.
To include only users who gave consent:
Set the filteranalytics_consent is true
.To exclude users who didn’t:
Set the filteranalytics_consent is false
.
This gives you full control over who receives surveys, based on real user preferences.
4. Use consent data in exports and reporting
User properties, including consent flags, are attached to every response. You’ll see this data in dashboards, exports, webhooks, and integrations using our API, so you can segment and analyze accordingly.
Best practices
Keep property names consistent. If you use
analytics_consent
, make sure the data type stays the same (true/false
).Always send the consent flag after the user makes their choice, not before.
Use
external_id
to help tie user properties to the right person across sessions or devices.Confirm your setup with your privacy team to stay aligned with relevant regulations.
You don’t need to collect consent through Iterate, but you can use the consent data you already have to make sure you’re only surveying the right people. It’s a simple way to stay compliant, respectful, and targeted, all without adding any extra friction to your user experience.