Important note: You should look to update your privacy policy as well. For details, follow this article here.
A few of the personalization filters in Relevic rely heavily on cookies to track visitor behavior and deliver tailored experiences. This guide walks you through the process of configuring cookie settings, ensuring compliance with privacy policies, and setting the appropriate filters for your campaigns. Let’s get started.
What is a Cookie?
A cookie is a small data file stored on a user’s browser when they visit a website. Cookies allow websites to remember user information and preferences across sessions, improving user experience by providing continuity. They play a crucial role in web personalization, tracking visitor behavior, and delivering tailored content.
There are different types of cookies based on how they function and what purpose they serve. Here’s a breakdown of common cookie categories used by most websites:
Strictly Necessary or Essential Cookies:
These cookies are required for the core functionality of a website, such as logging in or maintaining a shopping cart.
They are always enabled as they do not require user consent.
Marketing or Advertising Cookies:
These track user behavior across websites to deliver personalized ads and measure campaign effectiveness.
Consent is required before these cookies are activated.
Analytics or Performance Cookies:
These gather insights about how visitors interact with the website, such as page views or time on site.
This data helps improve website performance and user experience. Consent is usually required.
Functional Cookies:
These cookies store user preferences (e.g., language or login information) to offer a more personalized experience.
Depending on usage, these may or may not require consent.
How Relevic’s Cookies Fit into These Categories
Relevic’s cookies can fall under analytics or marketing cookies based on how you've setup consent categories on your end.
Analytics Cookies: If used to measure interaction with personalized content or campaign performance.
Marketing Cookies: If used to display targeted offers or content tailored to individual users.
🚨 Recommendation
Consult your legal team or relevant personnel to determine the appropriate category for Relevic’s cookies in your consent management platform to ensure compliance with privacy policies like GDPR and CCPA.
What Do Relevic Cookies Do?
Relevic sets cookies to:
Identify first-time vs returning users
Store anonymous session or campaign data
Power cookie-based filters for audience targeting
These cookies fall under categories such as Analytics and Marketing, and typically require consent depending on your region (e.g., under GDPR).
Cookie Management Modes in Relevic
When setting up cookies in the Relevic dashboard, you will see:
1. Save Cookies by Default
Cookies are stored automatically when a user visits your site.
Recommended when you:
Already use a cookie banner with implied or recorded consent
Operate in regions that permit cookies by default
2. Save Cookies on Trigger
Cookies are stored only when explicitly triggered (e.g. via a consent button)
Recommended when using tools like Cookiebot, OneTrust, or manual consent modals
Step-by-Step: Configure Cookie Settings in Relevic
Step 1: Access Settings
Log into your Relevic dashboard
Go to Configuration > Embed Code
Under the Cookies tab, select your website
Step 2: Choose Filter Mode
Toggle "Do you want to use cookie-based filters?" to Yes
Step 3: Set Cookie Lifespan
Choose the preferred duration (e.g., 180 days)
Step 4: Select Cookie Storage Behavior
From the dropdown:
Select "Save cookies by default" OR
Select "Save cookies on trigger"
Step 5: Implement Consent Scripts
If "Save cookies by default" is selected:
No further steps needed here. If a visitor revokes consent and you'd like to support deletion, then you'll need to call the following script.
<script>
deleteRelevicCookies();
</script>
If "Save cookies on trigger" is selected:
You need to manually fire the save function and this can be done either inside a consent button through your consent banner, or through a consent management platform (CMP).
<script>
saveRelevicCookies();
</script>
Lets get into these details and explain how this can be achieved.
How to Set Up Relevic Cookies in Google Tag Manager (GTM)
Option A: Save Cookies on Consent
In GTM, create a new Custom HTML tag
Paste the following and set the trigger to your consent approval event (e.g. Cookiebot's "CookieConsentUpdate")
<script>
saveRelevicCookies();
</script>
Option B: Delete Cookies on Rejection
Create another Custom HTML tag and trigger this on consent denial event
<script>
deleteRelevicCookies();
</script>
Important Note ⚠️ : GTM Consent-Aware Tagging
To stay compliant:
These Relevic tags should be fired only after consent is granted
Use triggers based on the consent management platform (CMP) consent events (e.g. Cookiebot, OneTrust) or your custom logic
Example: Using Cookiebot with GTM:
Consent management platform (CMP) fires CookieConsentUpdate event when consent changes
In GTM, create a trigger:
Type: Custom Event
Event name: CookieConsentUpdate
Condition: Cookiebot.consents.marketing === true
Link this trigger to the tag containing saveRelevicCookies()
Optionally, fire deleteRelevicCookies() if consent is denied
How to Use Relevic with Other Consent Tools
If you are not using GTM, you can still integrate with most CMPs or manual buttons:
Insert the saveRelevicCookies() function inside the click handler of your "Accept" button
Insert the deleteRelevicCookies() function in your "Reject" or "Revoke" button
Example for a button on your site:
<button onclick="saveRelevicCookies()">Accept</button>
<button onclick="deleteRelevicCookies()">Reject</button>
FAQs
1. What happens if I don't configure cookie settings? Relevic will not activate cookie-based filters, which may limit personalization options.
2. Do I need consent for all Relevic cookies? Most Relevic cookies fall under analytics/marketing and do require consent.
3. What if I use a custom consent modal? You can still fire the Relevic cookie scripts using the appropriate button handlers.