As a personalization platform, PureClarity requires tracking shopper actions to gather data for audience segmentation and deliver targeted campaigns and recommendations at optimal times.
Privacy-focused legislation like GDPR and CCPA requires shoppers to opt-in to tracking by giving explicit consent, typically through cookie banners.

​
Privacy Legislation Compliance

Key privacy laws:
  • GDPR (General Data Protection Regulation) - European Union
  • CCPA (California Consumer Privacy Act) - California, USA
  • Similar legislation in various jurisdictions globally
Compliance fundamentals:
  • Shoppers must opt-in to tracking
  • Consent typically given via cookie banners
  • Clear control over personal data usage
PureClarity provides optional consent requirements that can be controlled via Customer Privacy Settings.
Default behavior:
  • Consent requirement is disabled by default
  • Serves global market with varying legal requirements
  • Enable if your business operates under privacy legislation

​
Platform-Specific Handling

BigCommerce Customers
BigCommerce customers don’t need to modify PureClarity settings - we automatically use BigCommerce’s built-in consent management.
Other Platforms
  • Requires manual implementation
  • Integration with existing cookie banners
  • Custom consent event handling

​
Implementation Guide

When a shopper provides tracking consent, call: 
_pc('accept_cookies', true);
Event trigger points:
  • Cookie banner “Accept” button click
  • Privacy settings consent toggle
  • First-time visitor consent flow
This call instructs PureClarity to begin storing cookies and tracking the user’s behavior for personalization.
For GDPR compliance, shoppers can revoke consent. When supported by your platform: 
_pc('accept_cookies', false);
Revocation effects:
  • PureClarity removes existing cookies
  • Tracking stops immediately
  • Personalization reverts to general recommendations
Ensure your cookie banner implementation supports consent revocation to maintain GDPR compliance.

​
Functional Limitations

Without tracking consent, shoppers experience limited personalization: Recommendation Limitations
  • Only general recommendations available (e.g., Best Sellers)
  • No personalized product suggestions
  • Reduced conversion optimization
Campaign Restrictions
  • Only broad segment campaigns shown (“First Time Visitors”, “Everyone”)
  • Targeted campaigns unavailable
  • Limited marketing effectiveness
Popup Limitations
  • Only basic segment popups display
  • No tracking of previously shown popups
  • Shoppers see maximum one popup per session
Analytics Impact
  • Shopper behavior not reflected in analytics
  • Unable to map clickthroughs to conversions
  • Reduced data for optimization

​
User Experience Effects

Without tracking cookies, PureClarity treats the shopper as a new person on every page visit, severely limiting personalization capabilities.
Session behavior:
  • Each page view treated as new visitor
  • No cross-page behavior correlation
  • Personalization resets per page
Post-consent behavior:
  • Once consent given, all current session activity tied to shopper profile
  • Historical behavior incorporated into personalization
  • Full feature set becomes available

​
Implementation Best Practices

Essential elements:
  1. Clear consent language about tracking and personalization
  2. Easy accept/reject options for user choice
  3. Event triggers calling PureClarity consent functions
  4. Consent persistence across sessions

​
Compliance Strategy

Work with legal counsel to ensure your consent implementation meets local privacy law requirements.
Recommended approach:
  • Audit your customer base - determine applicable legislation
  • Review consent banner - ensure clarity and compliance
  • Test implementation - verify consent events work correctly
  • Monitor performance - track impact on conversion rates

​
Performance Considerations

Conversion optimization:
  • Clear value proposition for consent
  • Streamlined consent process
  • Immediate personalization benefits post-consent
  • Transparent data usage explanation

​
Technical Integration

​
Event Verification

Test consent implementation: 
// Check if consent has been given
_pc('get_consent_status', function(status) {
  console.log('Consent status:', status);
});

​
Debugging

Verification steps:
  1. Check cookie presence after consent
  2. Verify personalization activation
  3. Confirm analytics tracking