Managing cookie consent
Overview
To ensure compliance with privacy regulations, customers handle cookies and respond to user consent preferences with care and transparency. The Attribution Library is designed to support you in this process of setting the referral code cookie based on user preference. It is your responsibility to prompt website visitors to specify their preferred tracking level.
Cookie consent is a complex legal subject, varying across different jurisdictions. While the Attribution Library offers tools for managing cookie consent, it is the responsibility of your organization to consult with legal experts to ensure compliance with specific regional laws and regulatory requirements.
Understanding referral cookies
The Attribution Library employs a specific first-party cookie to enable returning user to claim their referral discount (see Storing the Referral Code in a Cookie). This cookie functions as a strictly necessary or essential cookie by default, but should be configured based on your privacy guidelines.
It's important to note that these cookies do not directly monitor the identity of returning users. Instead, it records the referral code, also known as the Unique campaign code (UCC), originating from the invitation link provided by a referrer and additional parameters to support returning users.
Cookies are not required to directly attribute referrals in Cello. They are used to assist in attributing a referral when a new user leaves and returns to the signup.
List of first-party referral cookies that are set
| Cookie | Purpose | Persistent or Session | Lifespan | Default type |
|---|---|---|---|---|
| cello-referral | Cello uses cello-referral cookie to identify the referrer and campaign. These let us link referrer and new user that sign up, and help us to apply rewards and discount based on the campaign terms. | Persistent | 3 months | Strictly necessary or essential cookies |
| cello-productId | Cello uses cello-productId cookie to identify the product (account) using Cello on this page. | Persistent | 3 months | Strictly necessary or essential cookies |
| cello-source | Cello uses cello-source cookie to identify source of visit to signup page | Persistent | 3 months | Analytics cookie or optional cookie |
| cello-cookie-consent | Cello uses cello-cookie-consent cookie to store consent to managing cookies | Persistent | 3 months | Strictly necessary or essential cookie for custom cookie handling |
Methods for Handling Consent
The Attribution Library provides several methods for handling user consent efficiently:
1. Custom Method
Custom method only works if your account has been configured to use custom cookie handling. Contact Cello Support to enable it.
Utilize the Attribution Library's JavaScript API to dynamically inform it when a visitor has consented to cookie storage. This method offers full control over the timing of cookie storage, allowing you to align it with your user consent process.
allowCookies
To allow the storage of the referral code cookie:
window.CelloAttribution('allowCookies');deleteCookies
To halt the storage of the referral code cookie and clear it:
window.CelloAttribution('deleteCookies');2. Consent System Method No code
For users of popular cookie management and consent platforms such as OneTrust, CookieBot, and Civic Cookie Control, the Attribution Library offers built-in support for seamless integration. Our Cello support team can assist you in configuring the right tool for your specific needs, eliminating the need for coding.
Supported Tools
- OneTrust
New - CookieFirst
Coming soon - CookieBot
Coming soon - Civic Cookie Control
Coming soon
These methods allow you to handle cookie consent effectively when utilizing the Attribution Library to track returning referees seamlessly.