This article covers:
- Managing and creating consent reasons in Gecko.
- Existing consent gathered through Do Not Call/SMS.
- Collecting consent reasons.
Account-wide consent reason fields have been introduced, alongside the general GDPR update for Gecko, allowing you to collect, track and enforce consent across the system.
A new section should be available for you inside the Gecko settings page, labelled ‘Data Security Preferences’. This section gives you the ability to manage and define consent reasons, which are now stored against each contact (you can view those if you visit any Contact’s Overview page and scroll down).
The general process in the Gecko system for collecting and enforcing consent will be achieved through Forms and Email/SMS templates. You will be able to collect consent and apply it to contacts through form fields and workflows while enforcing it will be achieved through templates (e.g. a marketing email template can be set to and only be received by contacts that have explicitly given you their consent to receive marketing emails).
Managing Consent Reasons
Default consent reasons
By default, your account will have the Email, SMS and Call consent reasons, which are automatically visible on each contact. You are free to create your own contact reasons and apply them as you see fit.
Creating new consent reasons
New consent reasons can be standalone or as part of a grouping, e.g. Marketing Emails (which can fall under the Email grouping). This gives you the option to grant and take away consent from contacts on a mode of communication, as opposed to a consent reason.
In addition to this, you are able to set descriptions for each consent reason, which will be shown against each consent reason on your form’s consent field. (Note: this is exclusive to the Gecko Protect package.)
If you currently have a Gecko integration with a CRM System, then you would be able to specify the Export Values to be sent when syncing consent reasons over. For example, your CRM system might expect to receive ‘True/False’ when syncing Email consent information, which this feature allows you to configure.
Assign consent reasons en masse
In addition to this, if you have already collected consent through an existing form field or other methods, you are able to access the ‘Assign Consent’ option from the Consent Reasons screen. This gives you the option to identify contacts and assign consent en masse. For example, you could filter out contacts based on their existing consent or based on the import they came into the system through.
Existing consent gathered through Do Not Call/SMS
If you have already collected consent from existing contacts in the form of 'Do Not Call/SMS', this information will automatically be transferred into the new consent reasons system. Contacts that have previously been marked as Do Not Call or Do Not SMS, will now have the relevant SMS or Call consent reason automatically removed, making them unavailable to receive SMs or Call communication, whereas everyone else will automatically have those consent reasons enabled.
Collecting consent through forms
In order to collect consent, you would need to create a checkbox (or multiple choice) field in your Gecko forms, giving form respondents the ability to pick and choose the consent they would like to provide.
- Add a checkbox (or multiple choice) field in your form requesting consent.
- Save your form and navigate to the workflows tab.
- Add a workflow and set the conditions to look for whether or not your new consent field contains one of your consent options (e.g. email).
- Afterwards, add an action to run based on the above conditions to Assign consent values, set the operation to Give consent to and select the Consent Reason to match the one in the Condition (or your form).
- Repeat this for each consent reason given on your form.
Ignore consent reasons
- You are given the option to ignore consent reasons. This functionality has been included in order to be able to send communication in the case of emergency (e.g. weather), as well as to not disrupt your current flow of communication prior to the enforcement of GDPR.
- Note: the ignore toggle will be set as ON by default.
Any questions? Feel free to start a live chat with a member of our support team or explore the rest of our academy at your leisure.