Skip to main content

Relevic Cookie: What We Store & Why

A detailed breakdown of all cookies Relevic sets to power personalization and visitor behavior tracking

Updated over a week ago

Relevic uses a set of cookies to personalize website content based on user behavior. This guide outlines each cookie name, what it stores, and how it powers features like visitor filters, personalization campaigns, and segmentation.

🚨 Note: All values are anonymous and do not store personally identifiable information (PII).

Global Consent Flag 🌐

Cookie Name

Description

rel_consent_cookie

Stores user consent status (true / false)

First-Time Views (Per Page and Global) ⏰

Cookie Name Pattern

Description

rel_f_v

Timestamp of the first-ever visit to the website

rel_f_p_v

Timestamp of the first page view across the entire site

rel_f_p_v_<page>

Timestamp of the first page view of a specific page (e.g., about-us)

Used in: Visitor Behavior Filter β†’ "First-time visitor on [page]"

Last Views (Per Page and Global) ⏱

Cookie Name Pattern

Description

rel_l_v

Timestamp of the last visit to the website

rel_l_p_v

Timestamp of the last page view across the entire site

rel_l_p_v_<page>

Timestamp of the last page view of a specific page

Used in: Personalization filters like "Last visited more than X days ago"

View Count (Page and Global) ▢️

Cookie Name Pattern

Description

rel_r_v_c

Total Relevic View Count across all pages

rel_r_v_c_<page>

Number of times the user viewed a specific page (e.g., demo-call)

Used in: Audience segmentation β†’ "Seen pricing page more than 3 times"

Deprecated or Ignored ❌

Cookie Name

Description

rel_r_v_i

Old visitor index value (no longer used)

Examples of Page-Specific Cookie Entries πŸ”

These cookies follow a consistent naming pattern where <page> refers to the slug or identifier of the page:

  • rel_f_p_v_about-us: First visit to About Us page

  • rel_l_p_v_pricing: Last time pricing page was viewed

  • rel_r_v_c_features: Number of times the Features page was visited

These values are stored as ISO date strings (e.g., 2025-05-08T10:45:00Z) or as integers in case of count.

Privacy & Data Use πŸ”’

  • Cookies are scoped to your own domain

  • No cross-site tracking is performed

  • All stored data is anonymous and used only to improve on-site experience

For cookie consent management, see our article on "Configuring cookie settings"

Did this answer your question?