Good afternoon and welcome everyone. Today we will talk about the latest French data privacy authorities recommendation about OpenStrike in pixels in emails. My name is Alexander Robin. I am training manager for the EMEA product team, and I am in charge of the French content. I will be your host for today's session. We will begin this webinar with a little bit of context, what is pixel tracking and how this new recommendation of the French data privacy authority affected. So just a few details, it is called recommendation in the official document, but we can call it regulation allow, so it's open to interpretation. Then I will show you the recommended steps to implement the solution. We'll review just after a few considerations, and we will conclude as usual with your questions and feedback. But first, as an introduction, I have two small questions for you. Don't worry, are no ranking or leaderboard today. Just a QR code to scan or a link in the chat. So I can see six people are ready. One. K. Thank you. And I will begin in a few seconds. Lots of players. Great. And we'll start with an easy one. What does CNIL stands for? It is National Confederation of Inuits, Liberal Inuits, Commission National de Informatique et aliberti, Carte National d'Entitete legitimate identity card. So yes, this is Commission National de Informatique et aliberti. Informatiique et de liberte. We will talk about it in details in the next slide. But before that, just to know about the audience, are you aware of these new recommendations in fact? Okay, so no clue. Heard about it and I suppose this is why you are here today. So great. Think we'll have seven more responses. Okay. So we'll introduce everything you have to know today. Thank you. Let's come back to the presentation. And before introducing the solution, let's talk about what is this recommendation in the first place and what companies will need to do and when. So, first question, what is the CNIL or CLV if you heard about it like this. So the CNIL is the Commission National de Informatique Liberte, aka French Data Privacy Authority. They oversee regulations on personal data for French residents, like GDPR for example. What is pixel tracking? So a pixel is a small invisible image the size of one pixel that is embedded in email campaigns. When this image is displayed that usually means that the email has been opened. So pixel tracking is tracking thanks to a pixel. What is the new recommendation from Kneel regarding pixel tracking? This new recommendation was released on April fourteenth that in addition to GDPR and consent collection regarding marketing emails now requires one extra and explicit consent to be provided for email opens tracking. And when will this recommendation be enforced? This one will be enforced on July fourteenth. Who is affected by this recommendation? So French customers, of course, but they are not the only one affected by it. Any company, any account collecting data from French residents. In order to help you disable the automatic tracking of email opens and to adapt your templates and email campaigns to this new recommendation, we have four suggested steps for you to follow. First of all, you will need to completely disable the default email opens tracking. Keep in mind, this will be applied to the entire account and this must be requested through SAP support. If you have multiple accounts or tenants, you will need to repeat this operation for each of them. Then you will need to start collecting consent regarding open tracking in a contact field. For that, you will need to create a single choice custom field with the following values. True for consent provided, false for consent not provided. And if this field is left empty, that would mean no explicit consent from the contact. This could also be used in the templates or campaigns that you will use for other countries where this recommendation does not apply. Next, if you create campaigns using the blog based editor or VCE, You will need to modify your email templates. You will need to create a variable in each of your templates. This will allow you to disable open tracking either at a template level or at the level of each campaign you have created from these templates. After creating this variable, you will need to add a snippet of ESL for Emarsys scripted language into these same templates. And finally, whether you are using the HTML editor or the VCE, sort of blog based editor, you will need to edit the email campaigns that will be sent after the recommendation comes into effect, which is July fourteenth. Now let's take a closer look at steps two, three, and four. As a reminder, step two is about collecting OpenStrike consent and store it in a custom contact data field that you have to create. You can do this through management and field editor. This custom field has to be a single choice field with the following values, true and false. The field ID will be generated upon creation. This field, so in your screen contact dot twenty eighty eight seventy nine in our demo account will be the field we will refer to in the ESL snippet that will be inserted in the email templates. This generated ID will be different in each of your accounts, so pay attention to that when you create this field. And don't forget to change the ID in your code if you copy and paste or distribute templates from an account to another. Let me quickly show you in the platform. It is here in management and then field editor. We have already created this one but it's quite simple. You can create a field and then you can call it consent opens tracking. Then a single choice, you click on create, and then you need to attributes false true and false. And then you click on save and this will be created. So this is how you can create this custom field. You can see it is live. So let's come back here. Step three is editing your email templates if you are using the blog based editor. After navigating to content, email templates, you can choose your template and edit. You will need to create a new do not track opens variable in all your email templates, and a snippet of ESL code like this one must be embedded in the head element of all your templates. I will show you right after. In this example of snippet contact dot twenty eight thousand eight and seventy nine you can find here is the ID of the custom field we created in the previous step. This is the consent field. This field will have a value and as a reminder, in our example, the field open tracking consent, false value meant consent not given. So the pixel we can see here on the entire second line will be added to your email following two different scenarios. If the do not track variable is set to off, all opens from all your contacts will be tracked. Use this if you wish to send email campaigns that do not require consent for opens tracking. If now the variable do not track, oops sorry, is set to on and the value of the consent, so the end is here, the value of the consent is different from false. Only contacts who have given their consent will receive an email with this pixel. And as a reminder, the values off and on, you can see here, are the values we had here when we were creating the on the variable we will create as I will show you. The dual track opens variable and on and off all these values here. Let's take a look in the platform. So for your templates, it is on content, email templates. I will just come back a few clicks so you can see. You can choose your templates. Click on edit. Two steps, create a variable and add the snippet. Variable is the last one. It is the fourth one here, and you can easily create one by clicking create variable. And then here you can enter, for example, do not track. This one already exist. So let's add consent. I oops. Sorry. Do not track consent. I can make the product label make it easier to read. And then the variable type has to be selectable. And then here, like the screenshot I had previously, you can have true. So do not reconcile true, and you have here on, and then false and off. And then don't forget to click on editable by the editor of the campaign, otherwise the variable won't be in this campaign. You won't be able to choose which use case you want. Click there and click on create. Then when the variable is created you can go in the frame editor. On my screen, on my example, it's already there and just before the head element is closed you can copy and paste your ESL snippet. Let's come back here. So this is the variable we were creating and this is the snippet or an example of it that you can use for your templates. If you are using the block based editor and after modifying your template, you need to set the value of the variable in the email campaigns that you will send after the recommendation is enforced. So to achieve this, now it's simpler than the template of course. You can navigate to your email campaign, to the second tab called content creation, and then you have here the style settings. You can look for your variable, and in our demo we have called it do not track opens. Then you have, of course, to define in your email templates true for emails requiring consent and false for campaigns that do not require a consent for open tracking. Finally, if you are using the HTML editor, you just need to insert a consent verification condition in your header and add this pixel to it. This snippet could also contain conditions to only display this pixel for French versions of this campaign using low counts. And in real conditions, what does it look like? Let's have a look in the platform as well. Channel, email campaigns, I have one already opened. Second step, so second tab content creation, and then style settings. You can look for it here, and depending on your use case, can you send this campaign to people that haven't given your consent or you need the consent, so you will have to choose the variable here. And that's all for this campaign. Beyond modifying templates and email campaigns, there are also other elements to consider. The first one is about reporting. Contacts who have not given consent or whose content field is empty will not be highlighted as such. They will be included in the didn't open responses in the results summary. The second consideration or second point of attention is about the existing campaigns. There is no retro activity on campaigns that have already been sent, not really for that, but campaigns that have already been created but not sent, so they can be scheduled or automated, will continue to collect opens until the changes we have discussed are applied to your templates and or email complaints. So don't forget to update your code and include the variable in your models, in your templates, and or components. This concludes today's webinar, and it's now time for questions and feedback. So if you don't have any questions, thank you for your attention and I invite you to scan the QR code to fill out our satisfaction survey. For those who have questions, I will now stop the recording and enable your microphones.