Permission for triggered messages
This system lets you check permissions before you send marketing messages. Or for example, you could allow this system to always request email sends and rely on your ESP's permission mechanism to make the decision about permission. Most importantly you should not send emails to anyone who has unsubscribed.
ICO guidelines
Provided you follow these ICO guidelines, you don't need consent to send triggered emails.
"The sender must meet all three of the following criteria:
it obtained the contact details in the course of a sale or negotiations for a sale [e.g. from your cart page or a registration page that's clearly related to buying];
the marketing is for similar products or services [the email markets relevant products and doesn't include marketing for unrelated third-parties such as charities];
it provides a simple means of opting out at time of collection [this does not have to be an extra checkbox on your subscribe form - you could put an unsubscribe link anywhere easy to find, e.g. on your privacy page] and provides one in each subsequent communication."
You must get specific consent to send newsletters and other bulk marketing emails.
Data fields for email marketing permission
Each visitor has an email marketing permission data field assigned to them, which can be used to handle the email marketing permission within the system.
View email marketing permission data field
This field can be viewed against each visitor on the visitor details page:
Go to Reports > All Reports > Site Activity & Insight > Visitors.
Enter the visitor's email or ID in the search bar at the top right and search.
The field can be seen on the left hand side of the page.
Set email marketing permission data field
This field can be set in 2 ways:
Given Positive Permission
The visitor has given explicit consent and the system can send them triggered emails.
Don’t send
The system does not send emails to this visitor.
Not Set
The system emails visitors based on how your account is configured. The default is to send emails if set to Not Set.
If you want to change this to only send when positive permission has been given, you can select the appropriate checkbox on the Triggers settings page.
To access, expand the User menu and go to Settings > Triggers and Messaging integrations > Trigger Settings.
Examples
Example of how positive email permission looks on the Visitor details page:
Options that can be set for email permissions:
Update email marketing permission data field
If you want to use our system to manage email permissions, you can update the Email Marketing Permissions field in a number of different ways:
Manually changing the field on a visitor’s details page - this is useful if a single person contacts you.
The script on your website.
For help, speak to our support team.Our API.
Learn more in Integration API.Our unsubscribe link.
Learn more in Add an unsubscribe link to your emails.Importing the field during person imports.
Learn more in Import person data.
Person imports
When importing the field during a person import, the Person.perm field needs to be set during the import to the status that you want to give that visitor:
1 = Given Positive Permission
0 = Don’t send
Not Set
The system emails visitors based on how your account is configured. The default is to send emails if set to Not Set.
If you want to change this to only send when positive permission has been given, you can select the appropriate checkbox on the Triggers settings page.
To access, expand the User menu and go to Settings > Triggers and Messaging integrations > Trigger Settings.
This status is then set against that person and it works with your account settings, as explained above. You can also use other import options such as True/False, Yes/No.
Learn more in Import person data.
Data fields for SMS marketing permission
Each visitor has an SMS marketing permission data field assigned to them, it can be used to handle SMS marketing permission within the system.
View SMS marketing permission data field
This field can be viewed against each visitor on the visitor details page:
Expand the Reports drop-down menu and go to All Reports > Site Activity & Insight > Visitors.
Enter the visitor's email or ID in the search bar at the top right and search.
The field can be seen on the left hand side of the page.
Set SMS marketing permission data field
This field can be set in 2 ways:
Given Positive Permission
The visitor has given explicit consent and the system can send them triggered SMS messages.
Don’t send
The system won’t send SMS messages to this visitor.
Not Set
The system sends SMS messages to visitors based on how your account is configured. The default is not to send SMS messages if set to Not Set.
If you want to change this to only send when positive permission has been given, you can select the appropriate checkbox on the Triggers settings page.
To access, expand the User menu and go to Settings > Triggers and Messaging integrations > Trigger Settings.
Update SMS marketing permission data field
If you want to use our system to manage SMS permissions, you can update the SMS marketing permissions field in a number of different ways:
Manually changing the field on a visitor’s details page - this is useful if a single person contacts you.
The script on your website.
For help, speak to our support team.Our API.
Learn more in Integration API.Importing the field during person imports.
Learn more in Import person data.
Person imports
When importing the field during a person import, the Person.mediums.sms.perm field needs to be set during the import to the status that you want to give that visitor:
1 = Given Positive Permission
0 = Don’t send
Not Set
The system sends SMS messages to visitors based on how your account is configured. The default is not to send SMS messages if set to Not Set.
If you want to change this to only send when positive permission has been given, you can select the appropriate checkbox on the Triggers settings page.
To access, expand the User menu and go to Settings > Triggers and Messaging integrations > Trigger Settings.
This status is then set against that person and it works with your account settings, as explained above. You can also use other import options such as True/False, Yes/No.
Learn more in Import person data.
Data fields for GDPR
Each visitor has a Data Processing Permission (GDPR) data field assigned to them. This data field affects the whole person, not any specific communication channel. It impacts triggers, personalization and visibility of personal data in the system.
View process data (GDPR) data field
This field can be viewed against each visitor on the visitor details page:
Expand the Reports drop-down menu and go to All Reports > Site Activity & Insight > Visitors.
Enter the visitor's email or ID in the search bar at the top right and search.
The field can be seen on the left hand side of the page.
Set process data (GDPR) data field
This field can be set in 2 ways:
Process
The system is allowed to send triggers and use personal data.
Do not process
Prevents the processing of personal data, which supports the "Do Not Process" or "Right to Restriction of Processing" provision of GDPR. No triggered messages are sent and personalization does not happen, as personal data will be ignored.
By default, consumers are set to have their data processed. Consumers can opt-out of that to exercise their "Right to Restriction of Processing".
Update Process Data (GDPR) data field
The Data Processing Permission field can be updated using the following methods:
Manually changing the field on a visitor’s details page - this is useful if a single person contacts you.
Our API.
Learn more in Integration API.Importing the field during person imports.
Learn more in Import person data.
Deprecated permission fields
There are 3 old data fields that still exist for permissions, but have now been deprecated because they overlap with the above fields.
Email exclusion field
Person.email_exclusion - this was previously used to set visitor permission to do not send for Triggered emails, but the same can be achieved with email permission field Person.perm and setting it to Do not send or (0).
SMS exclusion field
Person.mediums.sms.exclusion - this was previously used to set visitor permission to do not send for Triggered SMS, but the same can be achieved with SMS permission field Person.mediums.sms.perm and setting it to Do not send or (0).
Person explicit consent
Person.explicitPermission - this was previously used to set visitors that had given explicit consent, but this is now not granular enough and the fields Email permission, SMS permission, and Data processing should be used instead.