This page is part of RevSure’s Comprehensive FAQs, your all-in-one hub for answers on capabilities, data, security, scalability, configurability, and more. Click here to return to the FAQ home.
Is RudderStack part of the RevSure implementation stack?
Yes, RevSure incorporates RudderStack within its implementation stack for event collection purposes. Event processing and data storage are fully managed within RevSure environment, with the RudderStack dataplane deployed in RevSure’s private GCP Infrastructure to ensure customer event data remains within RevSure-managed systems.
Does RevSure recommend consent gating or suppression for GDPR/EEA visitors?
RevSure recommends following your own consent policies. We do not prescribe a specific approach, so you should align with whatever your legal and privacy team has defined.
Are there recommended GTM Consent Mode settings (analytics_storage and/or ad_storage)?
Ideally analytics_storage, though any category is workable depending on how your consent policy is structured.• Should these scripts/cookies load prior to consent for EEA visitors, or wait until consent is granted?The script itself can load either before or after consent. Events are only fired after consent is granted, since RudderStack handles that gating internally. As long as the cookies are configured properly through the Cookie Manager, no events will fire until consent is granted.
One additional note: Our team is actively testing the integration against CookieYes specifically. We will share an updated script along with test results shortly. I will follow up here as soon as that is ready.