SO exciting! This is a big pain point for us. Would love to be part of the beta as well 
Hi J, writing from Italy. How do you imagine a touchpoint for existing email receivers to collect their agreement ? Maybe a dedicated form in a separate mail ? Thank you
@LeanScale2 - I can’t open your link but since the beta is not yet available I’m assuming you’re linking to a different product update. I will clarify that since this will go straight to public beta you will be able to opt yourself in when the time comes via the Product Update tool. Just wanted to make sure it’s clear that we are not manually managing a list of beta customers! cc @CCanning
The best way to backfill the new record with data from a custom property will be to set up a one time workflow to convert the status. Hope this helps!
Thanks for the question, Arne. We have no reliable way of determining the country for a contact record at scale as every customer uses their own unique properties to manage this information. For this reason, if opted into consent based tracking the consent record will govern tracking for all contact records in your CRM. That said, any customer with a ‘not applicable’ status will continue to be tracked and will not see the ‘consent opt in’ on the preferences page. Hope this answers your question, and please let us know if you have any feedback!
Hello - Highlighting this point from the post above, but let me know if this doesn’t answer your question!
A “Consent to Track” option will be added to the contact’s Manage Preferences page, giving recipients a choice to opt in or out of tracking at any time. This option will appear for contacts with a Consented, Not Consented or Not Specified status. Contacts marked Not Applicable in the CRM will not see it.*
Hi Jackie
Yes, this would be helpful!
Do you have any idea when this new feature is going to be launched (in beta)? Our legal department really likes this approach, so they want to know when this could be enabled/applied in our HubSpot environment.
Hi Jacky,
Ok, this means that Hubspot recommends to bulg rollout of “Not applicable” to all other contacts in the crm?
Which other implications might that have for contacts with other legal-base state?
Hi Jackie,
Thank you for your feedback.
How the User access to that Consent page ? I suppose that they need to click somewhere to display that page, right ?
Do you have a video or some images to visualize the journey ?
Thank you,
Simone
I can’t find this beta in the product updates, how can i apply for this beta?
Please can I get on the beta list too?
We have not released to public beta yet! I will post here once it is available.
Yes - The recommendation would be to update the status for all customers who are not based in the affected regions to be ‘not applicable’.
When you say what other implications might that have for contacts with other legal-base states - Are you asking how the ‘legal basis to process data’ field and this new tracking record will resolve against one another? If so, see description below.
IF a portal is opted into ‘Data Privacy’ (and thus using ‘legal basis to process data’ to enforce tracking) AND they have consent tracking turned on, tracking logic will be determined as follows:
- Consent record = Consented
- Always track regardless of the ‘legal basis to process data’ field.
- Consent record = Not consented
- Never track. Even if you have a legal basis to process data, a recipient’s explicit revocation of tracking consent supersedes that legal basis.
- Consent record = Not applicable
- Only track if you have ‘legal basis to process data’ for that recipient otherwise, don’t track
- Consent record = Not specified
- Never track. Even if you have a ‘legal basis to process data’ tracking without recipient permission in an affected region would put you out of compliance
I hope this helps. Let me know if you have any other questions!
I cannot publicly post designs of new product that has yet to be released, but if you look at the footer of the marketing emails you send out you will see both an ‘unsubscribe’ link as well as a ‘manage preferences’ link. The ‘manage preferences’ link opens a preferences center for recipients to opt in/out of various types of communications. If opted into consent based tracking. all recipients with a status other than ‘not applicable’ will see an option on the bottom of this page to provide or revoke consent to track.
Hope this helps!
Please can I also get added to the public BETA
Thank you for explanation Jackie.
Neverthless, I still don’t figure how to make User provide its consent.
In Italy, Consent must come from a an active activity coming from the User. We cannot consider that we set it as YES and ask to the User to update. The consent must be gathered before the sending.
As a result, without any pop in or pushcommunication sent to the User, we need to avoid all sendings until they have not agreed for new pixel policy.
Let me know if you have other best pratics coming from similar competitors, please. On my side I will have an in depth analysis with our DPO.
Thank you,
Simone
The beta is not yet available. As this will go straight to public beta you will be able to opt yourself in when the time comes via the Product Update tool.
My understanding of the regulation is that consent does not need to be gathered before sending, it needs to be gathered before sending with a tracking pixel. Upon opting into this feature all of the contacts in your database will have a ‘not specified’ consent status. This means we will not insert any tracking pixels and we will not wrap links with tracking parameters (see original post for more details on what statuses map to what tracking behavior).
Upon sending an untracked email recipients will have access to their preferences center where they can provide explicit consent to track (which would update the status to ‘consented’ and all future emails to that address would include tracking features) or they can explicitly revoke consent (which would update the status to ‘consent declined’ and tracking would continue to be excluded from emails to that address).
Hope this helps clarify how the product works!
Thank you for details Jackie.
The fact is that with this scenario, we won’t expect User doing on their own the proactive action to go and activate the pixel.
So, this means that we need to avoid tracking on all database following your scenario, right ?
Thank you again,