Visitor's consent and SmartCode execution
As part of the data protection policies like GDPR, it might be necessary to obtain informed consent from visitors before deploying any cookies or trackers to process their data. One way to do this is to display a cookie banner informing visitors about cookies, thereby taking their consent for tracking.
Wingify adheres to data protection regulations and does not collect sensitive information. However, the decision to implement Wingify with cookie consent or not is entirely up to you.
Some of our customers have classified Wingify's cookies as necessary, allowing the Wingify SmartCode to be executed without the visitor's consent, while others have not and require the visitor's consent before executing the Wingify SmartCode.
Let’s look at the different approaches you can adopt to implement the Wingify SmartCode.
Different Methods for Implementing Wingify SmartCode
To determine which implementation is appropriate for you, always consult your legal counsel. They can help you make an informed decision considering the data privacy rules of the countries in which you operate.
Here are the different approaches that you may use to implement Wingify SmartCode:
-
Standard SmartCode Implementation
This implementation allows you to execute the SmartCode without the visitor’s consent, i.e., you do not require any permission before deploying cookies or trackers to process visitor’s data. The SmartCode executes as soon as a visitor lands on your website. If you intend to implement the SmartCode in this manner, click here to learn how to configure it for your website. -
Conditional Execution of SmartCode Based on the Cookie Consent
Wingify allows you to configure the conditional execution of SmartCode based on the Cookie consent status set by your visitors. Refer to Configuring Wingify SmartCode for your website’s cookie consent settings to learn more. -
SmartCode Implementation with Consent Configured for Wingify Insights and Engage
This implementation allows you to execute the SmartCode after obtaining the visitor’s consent. However, this implementation is limited to Wingify Insights and Engage; and with this, the Testing campaigns execute without the visitor’s consent. In Wingify, you can configure this implementation using custom triggers, which allows you to use any complex conditions as the trigger for the Insights and Engage data collection. If you intend to implement the SmartCode in this manner, click here to learn how to configure it for your website.
FAQs
-
Are there legally possible ways to declare Wingify cookies as essential?
If you define the Wingify cookies in the essential category, you can execute the Wingify code without the visitor’s consent. We have customers who have added Wingify in the Strictly Necessary category, but we recommend you consult with your legal counsel.
-
What kind of cookies are used by Wingify?
Wingify uses different cookies, each storing a different set of data. However, the cookies do not store any personally identifiable information or interfere with the loading or functioning of the website. For more information, refer to cookies stored by Wingify.
-
Is the product compliant with the required standards?
Yes, Wingify complies with data privacy rules. Read more about Wingify’s compliance here.
-
Can I integrate using GTM (on a trigger after consent is provided)?
Yes, you can. However, we do not recommend installing the Wingify SmartCode using tag managers like Google Tag Manager. By default, all tag managers load the SmartCode asynchronously, which can cause page flicker or flash of original content. The use of tag managers may also delay the Wingify SmartCode, causing time-out issues and preventing visitors from becoming part of the test.