Summary

Consent is an agreement between you and your contacts about your intentions with their personal data.

We let you to store this consent in a free Insight data collection called ConsentInsight.

ConsentInsight does not count towards your data storage limit.

Why should I record consent?

Consent is both a requirement of the GDPR and best practice.

You should want to know, in no uncertain terms, that the content you are sending your contacts is what they want and agreed to when they opted in. This way, you can make sure that contacts engage with and appreciate your content, and do not ignore it or worse (if it's an email campaign), put it in their spam folder. Otherwise, you risk affecting your sender reputation.

What can I store in ConsentInsight?

A single ConsentInsight record is formed of the following fields, for which you can provide the values:

• Text: What contacts consented to. Use this field to record the answers to questions, such as:
  • Do your contacts want to receive your communications, and from which channels?
  • Do your contacts know what you do with their data?
  • Do you know how often your contacts want to be contacted by you?
• DateTimeConsented: The date and time that your contacts consented to the contents of the Text field
• URL: The URL that contacts gave you their consent from. For example, the URL of a signup form.
• IPAddress: The IP address of the device your contacts used when they gave you their consent
• UserAgent: The type of web browser that your contacts used when they gave you their consent

Please note: For every ConsentInsight record, a  DateTimeCreated field is automatically created and given the value of the date and time, in UTC+00:00, that the ConsentInsight record was created.

You can store multiple ConsentInsight records against one contact, and we guarantee to display up to the latest five ConsentInsight records, both in the app and in the ConsentInsight.json file when you export a contact.

How do I upload a ConsentInsight record for a contact?

You can upload a ConsentInsight record for a contact in the following ways:

• At the time of opt-in. For example, when a contact opts in via a signup form or opts in via a survey that includes the consent element.
• After opt-in. For example, if you want to retrospectively store ConsentInsight for contacts that you already have in your address books, you can do so by updating them via an Excel or CSV file, or updating them via the API.

If you want to upload a ConsentInsight record by importing contacts via an Excel or CSV file, you need to map your columns names to the following consent fields:

• CONSENTTEXT
• CONSENTURL
• CONSENTDATETIME
• CONSENTIP
• CONSENTUSERAGENT

After you've uploaded a ConsentInsight record for a contact, you can view that record by going to the 'Insight data' tab of the 'Manage contact' page, and selecting the ConsentInsight collection from the dropdown. 

Limits for the values of ConsentInsight fields

If you've previously created an Insight data collection, values may be limited to 255 characters, otherwise they are limited to 1000 characters.

Tips

• Segment contacts by what they consented to, for example, by using the 'contains' filter on the consent text to find contacts who consented to different channels