Skip to main content
All CollectionsFAQs
GDPR Consent FAQs
GDPR Consent FAQs

Learn how you can work with the GDPR rules with Databowl.

James Dodd avatar
Written by James Dodd
Updated over 3 years ago

In order to comply with GDPR, Databowl has implemented tools to help you stay fully compliant. Below are a breakdown of the features presented as FAQs to help solve your GDPR problems


How can I delete individual leads?

  1. View a lead in Databowl

  2. Delete the lead

  3. The view lead should display that the lead was deleted, when it was deleted, by which user, and the ip address of the request

You should still have an audit of what happened to the record within Databowl

delete_1.JPG

How can track which channels my marketing leads have consented to?

You can track which marketing channels my leads have consented to within Databowl

  • Email

  • Phone

  • SMS

  • Postal

You can pass a True/False or blank along with a timestamp - In the supplier integration document.

To use the GDPR feature please ensure as a minimum you pass:

  • terms_url - Terms the user has agreed to

  • terms_url_timestamp - The time the user agreed to the terms

  • the relevant permission e.g. optin_postal/optin_sms/optin_email/optin_phone

The individual channel optin timestamp will pick the time specified from the terms_url_timestamp if left blank - however, you can supply if they are different to this value

consent_fields.JPG

Testing This

Quickest way to test this is as follows:

Submit a leads with only some of the optin data marked as consented.

View the lead in Databowl.

You should now see it display which ones you've consented to.

Green for optin, Red for opt-out and grey for information not provided.

You can hover over to view the optin/out time

consented_1.JPG

How can export which marketing channels my leads have consented to?

On export, you can map the fields to marketing channel consent.

This will export with true/false


How can update marketing consents via the lead update API?

You can use the lead update API to update marketing consents.


1. Submit a lead to DB, with no optin data (by default these will all be false)
2. Update the lead specifying an optin to one of the marketing channels, ie optin_email with a value of true
3. View the lead in Databowl. You should see that the lead has now opted into the channel you updated with the time that you updated the lead.
4. Update the lead again, opting out, and this time specifying optin_email_timestamp
5. View the lead in Databowl. You should see that the lead is now opted out of the channel you specified with the time that you specified.


How can only send my leads responders that have the appropriate consent?

You can specify SMS responders require SMS consent on the lead and that email responders require Email consent on the lead. This is visible when creating a new responder.

emailsmsconsent.JPG

This option will require the optin_sms/ optin_email, terms_url_timestamp and terms_urlpopulated to work.


How can store and see the T&Cs my leads agreed to?

You can view the Agreed Terms and conditions supplied a PDF and Raw file.

termsoptin.png


How can I submit the new GDPR fields using the test leads functionality?

1. View the submit test leads form for a campaign
2. You should see optin* fields for each marketing channel (Email, SMS, Phone, Post)
3. You should see optin*_timestamp fields for each marketing channel (Email, SMS, Phone, Post)
4. You should see terms_url and terms_url_timestamp fields
5. Submit test leads with various combinations of values for the above.


How can I have the ability to forward the option/timestamp/terms fields?

  1. Set-up a campaign with default fields and a supplier

  2. Set up a forwarding to request

  3. Map the new metadata terms url and terms url timestamp fields

  4. Map some of the new marketing channel fields

  5. Submit leads to the campaign with the new fields (see integration doc) and ensure they forward as you expect

markingchannels.JPG


How can I be warned if I'm forwarding data to an insecure URL?

Go to the create campaign forwarding page and enter a non-https URL. Check that you get a warning about the URL being insecure.

insecurewarning.JPG


How can I ask more questions?

If you have any more questions around GDPR and how you can work within the rules with Databowl, just open a new chat.

Did this answer your question?