Let's dive into the GDPR, the preference center. A quick reminder of what GDPR is. You remember, in May 2018, comes this new European regulation on how to manage and protect our data and protect it, which was intended to be completely uniform across Europe as soon as it came out. And over time, it diverged diverged a little. Today, we're in a position, in France, which has come back a little to what we had before, which is not necessarily the same as in Germany, where on the B2B side you're allowed to write e-mails to people, if they haven't already done so. explicitly asked to be unsubscribed beforehand, and that in our communications we propose an easy way to unsubscribe. This is really the B2B principle, which isn't quite the same as same thing in B2C. So, the best practice we're going to adopt adopt is to have at the foot of our e-mails, systematically, a link pointing to what we're called a preference center preferences center. If you go to the e-mail you've received, there's a little link. By the way, the fact that spam engines spam engines see an unsubscribe link inevitably results in a loss of points because they know right away that it's e-mail marketing. But you're not supposed to send marketing e-mails via Marketo - I'm not talking about operational operational e-mails. You're not supposed to send marketing e-mails marketing e-mails via Marketo without a link unsubscribe link. Marketo is watching this. That's the link you have there. This link here points to my preferences center. So you can put it wherever you like: at the top, at the bottom, in the footer. You can be quite creative. Behind, it's going to take us to, my place, this page which is a a bit long, where I show you everything you can do. So it's not necessarily the right thing to do. you have to do. Generally, we try to keep preference centers that are short, but I wanted to have a little fun. So, I chose to put the possibility of unsubscribing right away. I find it more pleasant for for the visitor who wants to unsubscribe to immediately find the field where they can unsubscribe and accept. Someone who wants to unsubscribe, we have two ways of approaching them: or you can say straight away: "Yes, I'll comply with your request as easily as possible so that so that your irritation doesn't increase", or we use the IKEA technique technique, where we take him through a convoluted path. Like IKEA aisles. You want to buy a lamp (inaudible) and you're going to pass through the bedding, through the plants, through the shelves, and maybe you're not going to buy a lamp, but a mattress, a plant and a shelf. Until recently, it was placed at the bottom. Testing both. On this preference center, the idea is also to use it to ask the person what you want personal information, company information, interests, the consents he gives us and to be able to manage the law to information and the right to be forgotten, which is what the GDPR is asking us to do. If I go through these different topics from one to the next, on the personal information, there aren't many subtleties. These are the database fields we're displayed here. The only little subtlety I have here, is the fact that I allow you to change the address. You know, in Marketo, the Email Address field is a key key, meaning that if you fill in the the same form twice with two different Marketo will create two people in base; not to know that it's the same person who has filled in the same e-mail a second and I'll update the profile. E-mail is really the key. If you want to allow visitors to change their e-mail through a Marketo form, a special field is required. Here, I've created a New e-mail field and a campaign, which we'll see next. which will copy the value of this New e-mail field into the e-mail Adress once the form has been submitted. Feel free to interrupt me, ask any questions live, of course. Here, I also have fields that are more company-oriented fields. There's a little trap you need to be aware of. If it's a new person coming who's not known to the base, don't worry, these fields are carried table and I'll get the fields. On the other hand, if it's one of your customers, and especially if you are synchronized with a CRM, be it Salesforce, Dynamics or any other solution, if you're connected with a CRM, you need to know that Marketo is not the master of the table of companies. CRM is the master. So these fields, your customer will be able to enter them, but on first modification... these fields are modified in Marketo, they will be pushed to the CRM side, but they cannot be copied to the Company table, table. And on the first modification of the Kamelot account, these fields will be modified on the Marketo side, so the information will be lost. Perhaps an alert is needed marketing side so that the person, on the marketing side, makes the change manually in the CRM. It's a bit special, the Company fields we put on forms, you have to bear in mind in mind that the information may be lost. Here I have centers of interest which are different from My consents. So why do I have both? It's a little bit different, asking permission to talk to a contact. The GDPR tells us: "Normally, you can't have consent global", you can't have a checkbox. This is what we had a little before May 2018. We'd gone from "I just have a field, inscriptions on my page, my preference center", to "I request global consent". That was a little better. The GDPR says: "No, you can't have global consent, the visitor who gives his consent must know exactly what he is giving his consent." So there, then we have a gray area, that is, it's not defined exactly what level of granularity to ask for. I chose five consents because I'm testing things. You can have two, you can have three, you can have four. The idea is that you don't have in case of an inspection, we can prove that it's still granular enough. So, it's one thing to ask consents, but it's another different thing to say to the person: "With us, what do you interested in? What are you looking for from us?" It's not all the same thing. Consents are more likely to be oriented towards campaign types you're going to do. Why are you doing this? It's that when the operational marketing person marketing person does his campaign they need to find newsletter consent immediately. She must not ask herself and say to herself: "The guy gave me his preference on customer experience, on marketing strategy, but I'm doing a newsletter that talks a bit about all that, so what do I get?" You don't want to be able to ask yourself questions. That's why the consents are generally aligned with the types of marketing campaigns. So, it's more of an internal vision. So, centers of interest, it's more of a focused vision visitor-centric, customer-centric, prospect-centered. It's: "Dear you, dear visitor, what are you looking for? from us?" To be clear, as soon as someone gives you their preferences, we can imagine putting an education flow behind it. In other words, if you come to me me for information on marketing automation, ideally, I have a nurturing flow on marketing automation. And as soon as this box is checked, I'll send you my feed of nurturing. If it's the customer experience you're interested in, ditto. While you wouldn't expect this for events, thought leadership or training. Of course, I have customers who decided to mix the two and to have a single block that mixes both both preferences and consents. Everyone remains free. I'll explain my philosophy to you. I'm not saying it's the absolute truth. absolute truth, but in any case, that's how I did it. In any case, what's important is that for consents, I really encourage you to use text fields in order to have the values "Yes", "No", "Select". We can represent them differently to make it a little more sympathetic. Why did I do that? It's absolutely necessary differentiate, in consent, the fact that the person didn't information, explicitly said yes or explicitly said no. Which, with a checkbox, is quite complicated to do. So, we can do it, but it's not easy. So for me, I prefer not to have to think too much. In my campaigns, for example when I want to send out my newsletter, I'm going to take the people who said yes. I'll take the people who are subscribed to my newsletter. When I did my webinar yesterday morning, I took the people who didn't hadn't said no to me, in this current GDPR logic where I can send unsolicited possibly unsolicited to people in my database, provided that it can interest them and provided they can unsubscribe. So here were the people I absolutely I absolutely had to exclude, were the people who explicitly told me who explicitly told me: "No, your events don't so don't write to me. me." Having this text field, these values "Yes", "No" and "empty", makes it easy to differentiate between these and it's much easier for the team easier for the team to manage operational marketing. Fewer knots in the brain. For preferences, you can set checkboxes, and the person can have several preferences. Here's what we're interested in, is to know that "Yes, I like marketing automation." So, by default, it's empty and as soon as the person says yes... So, here we have two philosophies, once again: either, at creation, we'll check off everything and we'll encourage the person to come to say: "No, social selling nor transformation digital transformation", or leave it empty the creation of the person and the person will fill in little by little. I confess that I rather chose the option the option where I check off everything at the start and I encourage the person to come to uncheck what doesn't of interest. Sylvain, how are you managing this? I mean, when we register on your site - I don't remember - these areas of interest, when can you give them? You can give them at the very beginning, when you register or create an account, or we'll have to go have to go specifically to this page to do it? So, when a person is created in my database, as soon as the person is created, I instantiate these five fields to "Yes", already. And then, indeed, when the person comes, they'll see that they've left the boxes checked and she'll be able to decide to uncheck. Okay, so you've made the bias that you set everything to "True", and then the people (inaudible). OK, all right. I certainly don't do this for consents. Yes, of course I do. So, the consents, you don't put anything at all, by default? When you arrive, you're at "Select". And it's these consent fields that I'm going to use next on my actual campaign pages. Wait, I have to take my cookies, because the progressive profiling. If I remove this one and this one, that should be enough. I'll freshen it up a bit. Here, I have the Consents field you saw on the events. So I put it in the progressive profiling, which means that once the person has registered, these fields will disappear and the fields will appear, so she'll still be able to return to the preference center because there are the link there, but I don't ask for consent consent every time. That is, once I have it, I don't ask again. This prevents the person, the next time, to say : "No, I'm not interested after all. interested." So, centers of interest, consents. Good practice too... here I made blocks by subject. Don't hesitate to give via rich text, what's involved in giving consent or not consent. Here, these are consents on another BU we have, so I'll probably do another another preference center for this BU because they're two different different populations. But I didn't have time for that. And three last points that I manage on my preference center: pauses. Here we can say: "I'd like to pause for 90 seconds, 60 days, 30 days", which means the person will have this marketing field "Suspended" checked. And you know that this field, by default, it's a system field Marketo. As soon as it is checked, the person is excluded from marketing campaigns. So that's pretty interesting. We don't have to worry about it afterwards. And here, she can exercise her right to information by checking this box. What's that going to do? It'll send an alert to me, Sylvain, it won't do anything in the database, and I'll have a campaign on both the Marketo and Salesforce sides Salesforce side, which will allow me send an e-mail with all the information all the information, all the fields I have on the person in Marketo. Before pressing the button, I still look at the profile to see who it is. It allows me to be compliant to the management part of the right in theory. (Inaudible), Sylvain, on whether or not to send the information? I've never found a case where I didn't send it. I don't know. I always imagine the slightly rotten case of a field text somewhere something that a bit contentious. Yes, I know what you mean. (Inaudible) I'm interested to see if there's anything special about the thing. (Inaudible) Okay. You just look in the CRM all the information you send him, instead of doing it automatically? That's it. Right. Yes, you're right, that's better. You never know, if there's something written in the CRM. By the way, I'm not sending the field Message field. By default, I don't send text fields, the "long texts" fields. It's safer. In theory, the right to information, we're supposed to go collect in all the systems we have - marketing automation automation, CRM, back-office, the API, everything you've got - and get all the information out. As far as I know, there aren't know how to do that, except maybe Facebook and Google - and then again. I consider that by taking out the information I have in marketing automation and CRM, since both are connected, I'm already in the top 1% of companies that are on top. Before going any further, we're already going to wait for the others to catch up and that'll be good. And I don't think Merlin/Leonard is not the target of the CNIL either, given the fact that we do very few very few outbound campaigns. But it's an easy way to be compliant at low cost. Ditto on the Right to be Forgotten section. Here, I have this sentence, with the only mandatory field in the preference center: "I understand and accept the policy privacy policy", in which I say that there will be cookies that will be stored, that the information will be used to make segments, for processing, for scoring, etc. This is the page that nobody reads, but which we're obliged to put on. If the person puts "No" here, it means they won't authorize me to store their data. So, ditto, I get an alert that this person wishes to exercise his right information. By the way, if I put "No", I get a text that appears says - I'll have to correct this copyright problem, that's when I added it, I didn't (lower) the copyright - we're going to delete your data, basically. Idem, I have a campaign at my disposal Salesforce side and on the Marketo side, which will empty all Marketo fields, and therefore Salesforce, which will keep just the e-mail, the date on which the person request and the date on which I responded to the request. Because I need to be able in case of an inspection, that we received this request and exercised it. If I delete the data, I won't be able to prove it. In theory, what you're supposed to do.., is to anonymize, including e-mail. Since I only have the e-mail, I put "Unsuscribe", I set "Blacklist", I've entered all possible fields to tick to say "No, I'm not writing to him", I consider this a good first step. Let's take a look at Marketo, if you don't mind, to see how how it's going. I'm going to close this. I've created a whole bunch of fields. I've prefixed them all PF like Preference Center. I've created fields. For example, here I have my field Seminars Date... Seminars Source. Here's my consent field Events. It's synchronized with Salesforce, that's why I see it in this folder. This allows me to display part of the preference center on the CRM side. So I find the centers of interest and consents here, with the preferred language and solution. I've added to this field PF_Subscription_Events, ABO_Events, the Date field and the Source field. This means that each time this field is modified, I'll change the date, to keep track of the date when the change took place. And the source is : has the change been made on preference center? Has it been done on the webinar? And so on. So, I have fields like this for all my consents. I have fields for the policy. These are the fields you saw at the end, at the very bottom. Those were the fields. So, each time, there's the date and the source. The field for New E-mail. What else is there? Right to information here. And Pause field. So, if I go to Marketo, I'll have a campaign here that will handle the e-mail change. That's what I was saying. As soon as the New E-mail field empty, what am I going to do? I'm going to copy. I'll wait a minute. Why am I waiting a minute? That's a good question, it'll come to me. Exactly, because I put a choice here. Here we have two conditions that must be met at the same time: the fact that the person has filled in the preference center and the fact that that this field is not empty. In principle, I only use this field in the preference center. But suppose I could use this field this field elsewhere: here I want make sure the field has been modified through the preference center. In Marketo, this type of condition this type of condition. You can't say "as soon as the preference center is filled and the field has been modified". You know that if you set two triggers, Marketo puts an "Or" between the two. It says it's either one or the other. If you want to say "No, I really want it to be this and the condition The preference center has been filled'", to do this, we take one of the two triggers, one of the two conditions - here, I've chosen to change the field - wait a minute and I've made a Smart List which is "People who have filled my preference center within five minutes". I'm using a Choice here, in the field change. So, if the person has filled in the preference center within five minutes, I change the Email Address field with the value of the New e-mail. Here, I'll set the checkbox to "False" and the New E-mail field to to "empty". If you want to put an empty value in a field, this is the Null" value. Is this clear to everyone? Yes, it's almost too easy, I think. Yes, it's very well thought out, I think. Too easy? It's Marketo, it's too easy. This is it. On paper, it looks simple. But it's a great idea, I think, to be able to change the e-mail easily for the person. Yes. So, when I created the person, we saw that I instantiated its fields Preferences set to "True". Let's take an example of an opt-in, the Events opt-in for example. After that, it's the same for the four others. Now that's interesting. This is the case where the person is created on the Salesforce side, or the Events consent field field is set to "Yes". It can be in the webinar or it may be on the preferences. I'll wait a minute. So, if she has filled the preference within five minutes and she hasn't unsubscribed, I'll skip the Status program to "Opt-in". I didn't show you, but I have created a special channel for the preference center, which contains three states: Member, Opt-in and Opt-out. This is interesting because it at a glance, in the program header, the number of people who have passed through my preference center - 205. I've acquired four people via preference center, which is surprising because this not supposed to be a campaign the preference center, but why not? So, to date, 102 people are opt-in, 71 have unsubscribed and 32 haven't given a clear a clear answer. That's pretty handy. So, if we look at the opt-in... Opt-in, what does that mean? It means that the person hasn't unsubscribed, obviously, but I have at least one of the consents out of the five. So, here, if she sets the Opt-in field to "Yes", i.e. creation, or on modification, the Status program is set to "Opt-in", save change date field to "Date" and source "Preference Center preferences" as source. That way, I can prove, in the event of an audit, who gave me consent, on what date and why, via consent. Of course, all these campaigns are always "every time" because that the person can give consent consent, withdraw it, give it again, withdraw it (inaudible). So now we have the Opt-ins. We manage the Opt-out newsletter since it's a bit special. Marketo no longer uses it. So, unsubscribe. Here, we'll say that as soon as the person unsubscribes, whatever the channel... I used the Data Value field Changes, Unsubscribe. On Unsubscribe, you have two options: either you can use Data Value Changes with the field, or Unsubscribe from e-mail, which is a bit trickier and I have less control over. Unsubscribe from e-mail, I think it works fine when you use Marketo's standard unsubscribe link. I think so. But it doesn't work as well when you use a custom link that points to a preference center and then has a form with lots of fields, including an unsubscribe field. That's why I don't use this one this one too much, because it has more limited than this trigger. So, if the person unsubscribes, what am I going to do? I wait a minute, for this Smart List to fill up. So, if he has filled the within five minutes, I send a notification to the person saying: "This has been taken into account your unsubscription, we apologize and we won't bother you again ever again". And I set all granular granular consents. I change the date and put the source. And now, indeed, if it has filled the preference center within five minutes, I put the source "Preference center preferences", otherwise I assume he unsubscribed via e-mail. So, by default, it's empty. Same for newsletter, same for thought leadership. It's a bit of a suspender belt, because he's unsubscribed, why do we set "No" for unitary consent? I don't want there to be any inconsistency between my values, first the global Unsubscribe, then the local consents. There's nothing worse than having, say having, for example, consents to "Yes" on Newsletter and Events, and someone who unsubscribed. We wonder what the truth is. So it's important to keep consistency in the data. So, we change everything back to "No", and when we get to the end, here - these are local local consent, both HR - we switch the Status to "Opt-out". So, in my program, people who have my program are people who have unregistered. And you have to manage the fact that the person can re-enroll. So she was Unsubscribe. So, I haven't managed that it right yet. If it changes from "True" to "False", here, I'll pass the consents to "Null", I'll return to the initial state, neither initial state, neither "Yes" nor "No". Just because she has doesn't necessarily mean she's giving me consent. So you have to be careful. Now I set everything to "Null" and replay the the dates, and so on. And I set the person back to "Member", and not to "Opt-in". Does that make sense to you? Yes. Yes, yes. OK. Every time I visit this page, I think page, I think to myself to do something. Let's imagine that someone has unsubscribes and registers again for a webinar or a content download download or whatever. She'll receive the operational e-mail which usually follows the filling of this form. Since it's an operational e-mail, it's going to happen to him because he's is operational and it bypasses the Suscribe field. But if I was really into it, I'd have to create a special campaign for people who fill in a form and then unsubscribe, saying: "We noticed that you registered for the webinar, you've downloaded the white paper, and so on, but I note that you've unsubscribed." There, there are several possibilities. The most cavalier will remove the flag from the Unsubscribe field directly, saying: "You've been automatically feel free to go to the to our preference center to modify your choices." Or we could say: "We've noted that you've unregistered, don't hesitate to go to the to uncheck the Unsubscribe box." So, imagine that 90% of people aren't going to do anything after that. So, depending on what you want the person to do the person to do, we'll choose one or the other. So I'll have to write that down for myself because since the time I've been saying I was going to do it. Reinscribe. Am I making myself clear? Yes. That's how you get automatically unsubscribed people, in fact. So, break management. Quite simple. As soon as the person changes the field related to breaks... there's a little subtlety because there's a list of values. As soon as the Pause field changes to 30 and it wasn't at 30, i.e. it was either at nothing, or, for example, at 60 or 90, I send an e-mail to the person saying that we've noted that it was paused for 30 days, I pass the Suspended marketing field to "True", wait 30 days and after 30 days, I switch back to the marketing Suspended field to "False". and change the Pause number field back to to "Null" and the... what's this, PF Pause? Ah yes, it's the checkbox that brings up the list of values to "False". Then imagine the case where the person triggers a pause for 30 days and comes back after 15 days. As it returns after 15 days, the form will be pre-filled and she'll see that she's on 30 days. Then you have to imagine the case where I was at 30 days and I go to 60 days. That's why I did a bit of convoluted thing. It's just that if she's like that, when she goes into the countryside at 60 days, it will be taken into account in the 60-day campaign, because it goes from 60 days to not 60 days, so she'll back into this one. So she's going to leave for a break for 60 days. And if, for example, the person had put in 90 days from the start and finally comes back 15 days later and takes 30 days, does that handle it too? Yes, it makes me think I've forgotten forgotten something, you're right. If I detect that she was in a... yes, I need to add something, good point. That is, I need to add here, just before Wait. In fact, if I detect that she's in the 30-day campaign - I'll do it right away - I have to get her out of the campaign. No, it's not "Member", it's "Remove". "Remove from flow", we'll put a Choice. If you're a Smart Campaign member, 30-day pause management, and I have to do the same thing with 90 days, I take you out from 30-day break management. And otherwise I do nothing. And if you're a member of the campaign... I have to do the same thing on the other two campaigns. So, for example, every time I enter a new pause and I detect that you were already present in a pause, I also have to remove you from the campaign, otherwise you'll leave for both campaigns. There will be some side effects, in fact. It's 90 days now. He doesn't seem to like it. This is number 3, not 1, that's why. I'll take you off the campaign for 90 days and otherwise do nothing. That's it, and I'll do the same thing: in the 30 days, I'll remove the 60 and the 90 and at 90, the 30 and 60. And so we agree that every time each time the person modifies this field, they change it from 60 to 90, the counter returns to zero? Exactly. With these two flows. We don't often use the "Remove from flow", but this is a good case. Remove from flow" lets you to remove a person who is in a Smart Campaign flow, especially during a break. This is the only way to remove a person from a flow, which is already gone and one person is stuck on a break. The typical case is that you have your e-mail flow invitation to a webinar. So, you have a first action, I send the e-mail, I wait for the dunning date. At dunning date, people who are still at guest" status, I send reminder number 1. Then I wait for dunning date number 2, and so on. And you realize that you've made a mistake with the dunning or anything else, so you want to stop the flow. Once it's gone batch, there's no way to stop it. People are in the flow and the only way is to create a Smart campaign on the side that will take people out of the flow. So we say: "All people who are members of the Smart Campaign 'Send invitation', I remove them from the flow with the campaign name." I think I've got a Marketo Tips on that. Right to information. As soon as the Right to information field field changes from "False" to "True" - and has I only use this field here, but even if I use it elsewhere, it would be the same flow - I'll send an alert to the owner and to marketing@merlinleonard.com, saying that someone has requested his right to information. I'm changing the request date, source of request, and I'll add the person to a static list, to the people who have asked for their right. And that's it for the first phase. The second phase is to act. Here, a campaign is made available available to Sales Insights. That's how it works in Salesforce, here. In my marketing campaigns, on the Salesforce side, because I used this trigger, I'll be entitled to the information action. That's a good campaign, Right to information action, campaign. And it's the fact that I'm using this trigger with Sales Insights here that makes it the other way around. side. So it's a campaign that I'm going to trigger manually, after viewing the person's profile, on the Salesforce side. I could also trigger it in Marketo. When you go to the database, you can also trigger campaigns manually. Just set Campaign is requested. Then we'd set Marketo flow action. If you go to a person on the database, you'll see in the menu that you can trigger campaigns by hand, especially with this. I'm going to remove it because it wasn't not the idea. What's going on? I'm sending the e-mail containing the right to information. You can have a look, it's a long e-mail containing all database fields. And then, I set the to "False". If the person accepts the policy, what is do I do? I don't even know what I'm doing anymore. Ah yes, I'm just recording the date and the source she did it to. Right to be forgotten, alert, it's the same thing. As soon as the person puts "No" in the Right to be forgotten field, I'll send an alert internally. I'm going to send a notification to the person saying and that we're going to process it ASAP. I save the date and source and add it to the list. And on the action side, ditto, it's available on the Salesforce side, thanks to this trigger. This is a long flow that sets all fields to "Null" all the fields I can, or to "False" when it's a Boolean. This takes a long time because there are many actions. This campaign is quite complicated because Marketo tends to bug once there are a lot of actions like this. Now I send an e-mail to the person that I've exercised his right and we've erased all their data. data. I'll save the date and we'll switch all database fields to "Null". for text fields. I set the Name to "Default". There are some fields I can't change to "Null". What is it, for example? System Date Time. Why did I put this in? System Date Time ? Oh yes, I'll set all the unitary consent units to be more coherent. I set the preferences to "No". You've got it, it's "Null" or "False". or "False". I set his status to "Disqualified", I set "Unsubscribed" and I set because she has requested her right to be forgotten. You said you kept her e-mail address earlier, at the beginning, and I thought you'd set his e-mail address to "Null". or was I dreaming? Was I dreaming? This is the personal e-mail. Ah, it's the personal one, all right. Basically, you remove all the fields, set them all to "Null", except for the reference e-mail address? Including first and last name. So, if she goes from "Yes, I want to be forgotten" to "No", what do I do? I send an alert, save it on the date and remove it from the list. But I don't do anything special on the fields. So, I get an e-mail notification as soon as it fills in the Preference Centers form. We'll send her a notification unless she has unsubscribed. This smart list is if she filled in the preference center and hasn't unsubscribed, this is number 3. People who have filled in the preference center in the five minutes, who have not unregistered, who didn't request who did not request a break to be informed and accepted privacy policy. I exclude all the special cases that I've dealt with through the others previous campaigns. So, I send a notification and an internal alert. And I don't forget to manage the acquisition. Like all programs that can be acquisition programs, this is not supposed to be the case for the preference center, there are still four people who have been acquired. As soon as she fills in this form, if the Acquisition Program field and Acquisition Date are empty, don't forget to enter the date in Acquisition Date and the program name in Acquisition Program. This is good general practice in terms of acquisition for all acquisition campaigns. What do I have to show you show you? The form, there's nothing special about it. This is a Marketo form. Do you have any questions? I spent 50 minutes there anyway. Perhaps I'll let you talk, and then answer the following questions. There's work to do. Is there work? Yes. In any case, I'll have to redo this preference center. You've already shown it to us and I thought your preference center was really interesting. You have to do everything in the back. For every action, you have a campaign. It's hyper coupled, so it's hyper interesting. You've got the guide now. This is it. We, on the other hand, have already started working on our preferences, but it's nice to have a reminder from you for how all the workflows work. workflows work. This is important. Thank you, Sylvain. At your service, folks.