Fanplayr 360
  • Introduction
  • Data
  • Navigation
  • Tutorials
    • Sync High Value Users to Facebook Custom Audience
  • Features
    • Overview
    • Filters
      • Examples
    • Insights
    • Audiences
      • List
      • Editing
    • Automations
      • List
      • Editing
    • Pipelines
      • List
      • Editing
    • Exports
      • List
      • Editing
    • Profiles
      • Profile
  • 🔗Integrations
    • Sources
      • List
      • Editing
    • Destinations
      • List
      • Editing
    • Catalog
      • Amplitude
      • Attentive
      • AWS S3
      • Cordial
      • Custom Integration
      • Facebook Custom Audience
      • FTP/SFTP - Password Authentication
      • Google Ads
      • JavaScript
      • Mailchimp
      • Mailup
      • Pipedrive
      • Salesforce Commerce Cloud
      • Salesforce Marketing Cloud
      • Send In Blue
      • SFTP - SSH Key Authentication
      • Shopify
      • Slack
      • TikTok
      • Twilio
      • VTEX IO
  • Other
    • Mapping
      • Events
      • Event Attributes
    • Data Dictionary
      • Events
      • Event Attributes
      • User Attributes
    • Data Health
    • Compliance
      • PII
      • Consent
    • Account Settings
      • Personal
      • Preferences
      • Company
      • Users
      • Security
      • Invoices
  • 👩‍💻API Reference
    • API Overview
    • JavaScript API
      • Javascript API Reference
    • Custom API
      • Sessions and Users
      • Tracking Page Views
      • Tracking Events
      • Managing Identity
      • User Profile Data
      • Managing Consent
    • Semantic Data
      • Semantic Events
        • E-Commerce
        • Messaging
        • Other
      • Semantic Objects
      • Semantic User Attributes
      • Fanplayr 360 Generated Attributes
  • PrivacyID
  • Appendix
    • Terminology
Powered by GitBook
On this page
  • Where it is used
  • How to set consent
  1. Other
  2. Compliance

Consent

PreviousPIINextAccount Settings

Last updated 2 years ago

Your users need to give consent to be contacted by you, both to keep them happy, and to apply by local laws such as or .

Fanplayr 360 allows you to set consent for specific channels such as email or sms, along with granular detail over the purpose and topics your users want to be contacted about.

The above example screenshot shows consent given by a Profile to be contacted by SMS for transactional messages, an by email (at different email addresses) for different purposes and topics.

Where it is used

This example screenshot shows consent being tested before sending an SMS in an Automation.

How to set consent

A list of consents given by a user can be viewed in the , can be checked in and filtered upon in , and .

Consent can be set (or removed) using our or . Some integrations may also add or remove consent ie an integration with an ESP.

Profile
Automations
Exports
Audiences
Insights
GDPR
CCPA
Custom API
An example from the Profile screen
JavaScript API