New for GDPR: Keep track of your contacts’ consent

.imageborder {border: 2px solid #e9e9e9; border-radius: 2px; margin-bottom: 32px !important;}

Tricky beast

I’m going make an assumption here, and it’s this: by now, you don’t need me to tell you about the GDPR, or why it’s important, or even how it will affect you. You know what it is, and you’re already planning for it – and have been for months, or even years. I know this because that’s what you’ve been telling us. We’re fortunate to have customers that are so proactive.

And if you know about the GDPR, you’ll know about Article 7 – even if not by name. Article 7 is the section that deals with that tricky beast: consent.

But perhaps consent isn’t that tricky: isn’t it really just knowing who’s subscribed and who hasn’t?

Under the GDPR, not quite – because simply knowing that a contact is subscribed isn’t going to be good enough. In the post-GDPR world, consent will need to be specific.

Consent’s no luxury

If you have a signup form that contains an opt-in checkbox with, “Yes, I’d love to receive future emails”, then that’s going to cease being the gold standard on May 25. You’re going to need to come up with something more specific – something that says what those emails are going to contain, and how often you’ll be sending them.

But coming up with clearer, more specific opt-in text is one thing. The GDPR also says that you need to be able to demonstrate you have that specific consent.

You may well already be storing preferences in data fields, or perhaps with address books. That’s great, and you should carry on doing that. But being able to demonstrate why a contact has those preferences? That’s something that’s probably new to you – and it’s why we’ve built ConsentInsight.

As of today, you can now store – for free – the exact consent text a contact agreed to. Alongside, you can store the IP address they were on at the time, information about the browser they were using, and when they did it. And if their consent changes, we’ll keep the history too.

Get, store, demonstrate

You can request and store consent wherever you can add a contact (with the exception of adding individual contacts in the app).

The simplest way will be by generating a signup form, which will now get you to set your consent text. If you prefer creating signup forms with our surveys and forms tool, then you can use the new ‘Consent’ building block.

If you’ve obtained consent by some other means, you can set it when importing contacts by including the information in the file you upload (you can map the values just like contact data fields).

Of course, you may also be thinking about retrospectively gaining and storing consent for your current subscribers (we like to call this ‘up-permissioning’). For this, take a look at our two GDPR-themed program templates; you just need to fill in the blanks.

Let us do it for you

If you’d like a helping hand using ConsentInsight, or perhaps running an up-permissioning campaign, we have teams on hand that can help. Just let your account manager know.

ConsentInsight is available in your account now – here’s the link to the documentation. To learn more about dotmailer and the GDPR, visit our trust center.

The post New for GDPR: Keep track of your contacts’ consent appeared first on The Marketing Automation Blog.

Reblogged 1 week ago from blog.dotmailer.com

Changes to how you export and delete contacts in advance of the GDPR

.imageborder {border: 2px solid #e9e9e9; border-radius: 2px; margin-bottom: 32px !important;}

Managing your contacts

As of today, we have new ways of exporting and deleting contacts. Some of these changes are to help you get ready for the GDPR, whilst some are to make managing your contacts easier and build on the new contact editor we launched earlier in the year.

Deleting

Previously, deleting a contact would hide her in your account. You couldn’t get her back unless you re-added her, at which point we’d resurrect the data you’d previously held on her.

But now, when you delete a contact, she’ll go into the recycle bin (previously called ‘Utilities’). She’ll stay there for 30 days, and you can undelete her at any time.

After 30 days, she’ll be removed permanently along with all her information held in contact data fields and Insight data.

If you want to, you can permanently delete her before the 30 days are up directly from the recycle bin.

This means you can now use the delete tool to comply with GDPR (or other) data deletion requests.

Additionally, we’ve made it possible to delete a contact from the contact editor, rather than just from the contact listing page – which should make things just a little bit simpler.


Deleting suppressed contacts

Delete suppressed contact

A suppressed contact is one you can’t email (maybe because she unsubscribed, your previous emails to her have bounced, or another one of a handful of reasons).

When a contact becomes suppressed, we don’t remove the data you’ve collected on her; if she was to become unsuppressed, her old data would be viewable again too.

However, we now offer the option of deleting a suppressed user.

This means you can comply with ‘right to be forgotten’ or similar regulatory requests.

But deleting a suppressed contact differs in one crucial way to deleting a normal contact: we won’t delete the email address. This is so we can continue to keep her suppressed, and so you don’t unintentionally email her in the future (by accidentally re-importing the contact to your account, for example).


Exporting

Export contact data

Up until now, exporting a contact meant exporting an address book they were in. This would give you the data held in your data fields (along with that of every other contact in the address book – which probably wasn’t what you wanted).

Exporting a contact is now easier and more complete. You can export an individual contact from the contact editor, and exports now additionally contain all Insight data you hold for them. This means that when you export a contact, you’ll now get a zip file with everything from the Email area of dotmailer – which will also be in a usable format for GDPR ‘Subject Access Requests’, should you need to fulfil one.

Note that if you have data held in the other areas of dotmailer (surveys and forms, SMS or transactional email) you’ll still have to export that separately.

Individual contact exports will also be kept for seven days in your export area, just like bulk exports.


More on the GDPR

Whether you’re in the midst of preparing for the GDPR, or if you’re yet to start, we have lots of articles to help you get ready. Check them all out here.

The post Changes to how you export and delete contacts in advance of the GDPR appeared first on The Marketing Automation Blog.

Reblogged 4 months ago from blog.dotmailer.com