On-Demand Webinar: Cookie Consent Management by Usercentrics CMP v2 Webinar

CMP for your website - fast and easy

Here's what you'll learn in the webinar:

Using our Adobe Launch Extension, you can add Usercentrics' Consent Management Platform (CMP) to your website in no time and with little effort. User consent is passed to Adobe Experience Cloud (AEC) products with ease. 3rd Party Pixel / Tag Manager can also be integrated with the extension Consent-dependent.

Watch online now (German only):

The speaker

Dinh Bao Dang is primarily an Adobe Experience Manager (AEM) architect. Marketing tools are becoming increasingly important in online business, so the next step was clear: Adobe Experience Cloud (AEC) and the marketing tools it contains. Bao has been involved with it since 2016 and is a certified AEC Developer. Since the GDPR, CMPs belong in the toolbox. The experience gained was very useful in the design of the extension.
Dinh Bao Dang
Software Architect

Transcript of the Webinar: Cookie Consent Management by Usercentrics CMP v2

Introduction & Welcome

Hanni Gummel: Hello and welcome to today's diva-e webinar on Cookie Consent Management by Usercentrics. Today, our experts will introduce you to how you can easily and quickly integrate the Consent Management Portal into your website. My name is Hanni Gummel. I am part of the marketing team, and today I have the honor to accompany you through the webinar. And I would like to introduce our speakers. Dinh Bao Dang is Adobe Experience Manager Architect at diva-e, and he will guide you through the presentation today. And Pascal Riedel is the Product Manager at Usercentrics. He will also be at the start of the Q&A. It's great that you are here today and sharing your expertise and experience in cookie consent management with us. I'll pass it on to you and wish all participants exciting insights in the webinar.

Presentation diva-e

Dinh Bao Dang: Yes, hello everyone. A warm welcome from me as well. Thank you very much for your interest and participation in the webinar. Before we go into media res, I would like to say a few brief words about us. I am Bao, and I work at diva-e. diva-e is one of the largest digital full-service providers in Germany. We have over 800 employees in nine locations and have received several awards, as we can see here on the bottom left. Our guiding principle at diva-e is TXP, Transactional Experience Partner. The idea behind this is that our customers' success hinges on completed transactions in the digital space. This is best achieved by creating sophisticated and engaging experiences. And for this, diva-e positions itself as a holistic partner and provides you with end-to-end support. Our broad portfolio includes, for example, strategy consulting, creative design, commerce and consent platform solutions, hosting and maintenance, and much more. To make the experience around Consent Management perfect, we have found a great partner, Usercentrics. With Usercentrics as a partner, we have been implementing Consent Management for a long time and can therefore serve our customers in the best possible way in this respect. And Usercentrics offers us professional consent management. It is easy to use, intuitive, and highly skilled to cover international compliance requirements. Usercentrics is also Made-in-Germany and meets our enterprise requirements entirely to use it super in our customers and projects. We live in the age of data protection nowadays. And the quote from the CEO also fits perfectly into our leitmotif of designing engaging experiences. He said, "Companies that professionalize consent management secure the trust of their users and can turn privacy into a competitive advantage."

Consent on websites

Dinh Bao Dang: And nowadays, on a website, there can be so many tags, 3rd party pixels, tracking solutions, targeting solutions, You Name It. And since the GDPR, yes, we have to be careful when we include these services or let them trigger. And only if the user has given consent, that is, has agreed. And so the toolbox of every website operator today includes the consent survey, the consent details, i.e. to show the end-user what consent does, i.e. perhaps for which product it is there, which data is recorded, where the data is processed, such things, etc. And you have to be able to make the consent change if the user, yes, changes his mind and maybe wants to take away a consent or decides to give one after all. And last but not least, you have to respect that consent. With usercentrics in our toolbox, we can quickly implement the collection, the details and the change. It's up to us to appreciate the support, and that's what the webinar is mainly about today.

Basic information about the page

Dinh Bao Dang: What do we have on the site right now? We have Adobe Analytics in there and Adobe Target. Analytics is, yes, web analytics. Adobe Target allows us to bring personalized experiences to the site. The core extension is just the basic functionality of Adobe Launch. That's always there. And last but not least, we installed the Experience Cloud ID service. That gives a user a unique ID that is then used in Adobe's cloud products so that you have a uniform customer profile and a uniform ID. Exactly. Here in the Rules, here we also have relatively little. Here Adobe Target was loaded, and the personalization started. The pageview, that is, when a user comes fresh to the page, the pageview is tracked once. And here we have a rule for the video played event. So stop when I press on the video. So. Now let's go and install usercentrics on the page. To do that, we will go into the extensions here, into the catalog, and search for usercentrics. Here we have the extension that we built. We can install it here. Now we have it in, and you have to enter two values first. Enter your Usercentrics Settings-ID. Here we also put question mark buttons like that. And you can check here. Okay. It can be found under Usercentrics Admin Interface. Then I go over to the Usercentrics Admin Interface, and I already have my Settings-ID. I copy it and enter it here into the extension. Now I have to enter the Usercentrics Window Name. Then I look, you must create a new Window Event in the Usercentrics Admin Interface under Implementation. So I go over here to Usercentrics, go into implementation, scroll down a bit, and here we have the Window Event. You can call this one whatever you want. I'm going to call it a webinar. You could also call it Usercentrics Launch Window Event or just ABC. Here you can name it as you like. We call it a webinar, save it once, and enter it into our extension. Then I kept that once, and now we have the extension installed and configured.

Bringing usercentrics to the website

Dinh Bao Dang: We would like to bring usercentrics to the website. To do that, I'll create a new rule. I'll call it Load Usercentrics, for example. And on which event would I like to have the rule fire? I would like that to be as high up on DOM ready as early as possible, please. And the action, what should it do? I want to load usercentrics. And then, here in the steps, you can select from the extensions which action you want to use from which extension. And here, we choose our Usercentrics extension. And here, under Action Type, there are Load Usercentrics. Now we take that, keep changes, save that to our library and build that once. Now, why is this taking so long today? Okay. The library is created, and we can now go back to the website and load that again. And we see Usercentrics is loaded and, yeah, all we had to do was bring a snippet of code Adobe Launch into the page, and the rest we were able to click everything together in Adobe Launch. And here we see, for example, Adobe Target is active, and Trekking is going out. Why is that? I hit deny, reloaded the page, and we see, still tracking. Of course, we don't want that. And we now have to connect the consent we collect from Usercentrics with the Adobe products. But before we do that, I would like to set the effects to opt-in. We see here it's being tracked. It's being targeted. The products are out-of-the-box opt-out. That means, if you get the extensions fresh in, they are on Opt-Out. But since we prefer to play it safe here in the EU, we do privacy first and set them to opt-in. To do this, I go into the Adobe Target Extension and say here DGPR Opt-In I put it to enabled. And here in the Experience Cloud ID Service, I'll also go in once, configure that, and set the opt-in on. So. Let's save that away, build the library once. Here on the page, I made myself a clear CMP Data button. If I press it, all my usercentrics data will be deleted, and then I come up like a new user or just like a fresh user. And, exactly, the library is built. Then we reload the website once wholly. And we see, it doesn't get targeted, no analytics comes out, and if I accept everything, nothing happens because, as I said, we haven't connected it yet. So. Let's look at how we then put that consent in form with the Adobe Experience products. And, right, that's where we go in here into our extension and say we'd like to use the Experience Cloud ID Service Opt-In. The Experience Cloud ID Service has what's called an opt-in framework. And that's what our extension communicates with. And then that opt-in framework will share with the Adobe Experience Cloud products and tell them, "Yes, you're allowed to do something." Or, "No, you're not allowed to do anything." And this is where we turn it on now, save that, and build the library. And now we have the launch page set up. In other words, we've got it enabled. Now, of course, in Usercentrics, we have to register the services. The services are so-called data processing services. And we have also provided a few default services here. Namely, the ones that come from Adobe. Yes, we are in the Adobe launch universe, in the Adobe universe, and we have already provided the template IDs for the Adobe products.

Adobe Analytics

Dinh Bao Dang: We are using Adobe Analytics and Adobe Target today. So lets a check in with Adobe Analytics. Here, the template ID is BJf5. So we'll go over here to Usercentrics, go into Service Settings, Data Processing Services, and say add Data Processing Service Fire Data Place. Then we now add Analytics, and we see Adobe Analytics Bjf5, which matches precisely with the template ID that we saw over there. We also see Adobe Analytics here; there are several other template IDs here with BR, CA, and so on. And, right, I'll get to that later, how you might use those. But we're going to go the standard route now and take the standard Adobe Analytics template and put that in the performance category and save that once. Now we need Adobe Target. That has the template ID 8L9. So we'll go over, add Data Processing Service, enter Target. I think there's too much Target. Then we'll take Adobe Target. And we see the same game. Again, there are different template IDs, but we'll take the Full Template ID 8L9. We'll add that one, and I'll say it belongs to the marketing category and save that once. So now we've finished the basic configuration. Now I can go back to my website. I'll delete my CMP Data once again and reload it entirely once. And we can see there's no tracking. There's no personalization. And now, if I press accept all, we see that Analytics is already tracking. And if I also play my video here, we also see the video played was fired. That works. Some will probably think, why didn't the personalization work now? This now works after a page reload. And directly, this varies from project to project. Some projects are okay with it or want it to happen only after a page supply so that there is no flickering. For example, if you were to replace the entire image here and hit accept all, you might not want the image to be replaced immediately, but you might wish for the experiences to come through on the next call or the next page reload. But we would like to, or I would like to show here in this webinar, how you can do that on the fly. So that when I come up and give the consent, the experience is loaded immediately. How do you do that? You go into the rules here, to our Adobe Target Rule. And if we look at those, it fires at the event when the window is loaded. And then Target is loaded, and Fire Global Mbox is called Target. Would you please do the personalization? And I want yes now that if-. As soon as I accept, I like the personalization to be fired. To do that, I need to add another event here, which I also get from my extension, Usercentrics. And can say here on Consent Update, meaning, if a user changes the consent somehow, gives new permission, takes license away and, exactly, then I would like that on Consent Update also, that this rule then also fires. And Target should only be loaded and fire the global Mbox or do the targeting if the consent is given. Accordingly, I have to add a condition. I get this condition from the extension. It is then called Consent Given. In other words, yes, consent has been given. And this for Adobe Target. I saved this and built the library again. There you go. Now let's wait a moment. The library has been created. Then I can reload once on the website. I'll come up now as a new user, saying come, here, accept everything.

Adobe Target

Dinh Bao Dang: And we see Adobe Target going off and Adobe Analytics going off. And here, when I play the video, again, that goes off. And now if I decide, oh no, I don't want to be tracked so much for performance marketing, okay, it's okay for me, then I might get new offers or better coupon codes or something, but the performance I don't want at all, then I can turn this off. And through the opt-in framework, our extension communicates directly with the opt-in framework and directly with Adobe Analytics. And if you would press up here, for example, we see that the video player is not sent. In other words, Adobe Analytics is no longer tracking anything. Of course, if I reload now, Adobe Analytics may not follow me anymore. What we see here. We can also do it the other way around, for example. I say performance is okay, but I don't want marketing. I'll save that. And the next time I come to the website, we also see there's no marketing, so no targeting, but Analytics is fired. One more little thing I want to point out here. For example, when I come up as a fresh user, we see yes, no tracking and no targeting. And as a user, I go down, and oh, there's a nice video. And for example, now I think to myself. Oh, the video is now covered by the banner. That's too silly for me. I press accept on everything. And when we do that, we see that the video played event went out and the pageview. That means Adobe Analytics internally stores the tracking events, but only when the user agrees that Adobe Analytics can send them out. So. We have now successfully connected Adobe Analytics and Target with our Consent Management.

3rd Party Tags

Dinh Bao Dang: Now, I would like to put the one LinkedIn Insight tag on the page to see how you would do that with a 3rd party tag. To do that, I've installed Observepoint, and I'm filtering for LinkedIn here so that we can, yeah, see only the LinkedIn stuff and not get confused. So how do we go about this? LinkedIn is a new DPS, so it's a new data processing service that we have to register here first in the extension. To do that, I'm going to go into the configuration. And here, we also have a custom section. And here, you can register your own data processing services. Up here, we have only the default templates for the different Adobe products. But now, I would like to implement a non-Adobe product and call my service name LinkedIn. And I have to register LinkedIn with Usercentrics. So here at the Data Processing Services, I add another one, searching for LinkedIn. Oops. Well, now I've pressed too much, sorry. Here, LinkedIn Insight Tag. This one I'd like to put on the website. So I'll pick that one out and, yeah, I'll put it in the performance category, safe DPS and save that once overall. And now, with the LinkedIn Insight Tag, we see the template ID JQ2 and so on. Now, I will copy that template ID out and paste it into the extension here. And so, the connection is established. The extension knows about this template. And back here, we have an Adobe category. This is important, for example, if I want to use other templates and assign them to the target. The use case would be, for instance, that I either create Custom Data Processing Services from scratch and write everything by hand, or I'm not satisfied with the descriptions that come from the database. I have to change something because, for example, my legal department told me to. Then I can customize a template that comes from the Usercentrics database. And then a little warning dialogue comes up. It will go down to customer services. And when I do that, we also see that Adobe Target has a new template ID. Here we see I7q compared to the default 8L9. Technically, this is now a new template. And for our extension to work with this template, I would have to copy out this template ID here, paste it into our custom section and say this is Adobe Target. So that the extension knows that it can then tell Adobe Target, "If this template ID has been consented to, I'm allowed to do something." But since we're implementing LinkedIn here, I'm going to set that to none because that has nothing to do with, right? LinkedIn has nothing to do with Adobe products. Now I'm going to go back and turn this Except by Default off and save that away. So now we're back in Launch and, right, LinkedIn I've now logged in. I can save that now. And now we need the rule itself, how to get LinkedIn on the page. Then I'll create a new law, add a rule, and call that LinkedIn. When would I like to fire that? I want to fire that at window loaded, and the action now is Custom Code and JavaScript here. Now here we have the first place where I need JavaScript. But I didn't write this JavaScript myself. This JavaScript, I get that from the LinkedIn Admin console. That's where I say, "I'd like to have my Insight Tag. Please give me the code." I copy that out and paste it here. So the bottom line is I didn't write any JavaScript here either. I copied and pasted JavaScript. Like this. Keep Changes. And now, if I were to save this and build it, then every page load, the LinkedIn Insight tag would be fired.

Consent Manager Platform

Dinh Bao Dang: Now, of course, the Consent Management Platform level is still missing. And there, I would like to have the optimization, as seen with Adobe Target, that when I give the consent also, then immediately the tag should be fired. Then I select my extension here again and say, "In the case of a Consent update, I'd like you to do something." And now, of course, I have to add the condition, when is he allowed to do something. And here, I can again select our extension. The consent must be given. And now we have LinkedIn here in the checkboxes. The one that we configured earlier under the Custom DPS. That means the more DPS I add; the more will come here. Namely, all of the ones that I add in there. And so I can hook-click and say, "I'd like to query this template ID here." So, keep Changing. And now our rule is also ready to go. So I'm going to save that. Save once and build the library once. So, the library is done. So now we can clear cache once and load completely. And, yes, I'll do the easy case. I'll say accept everything. And we see bang, LinkedIn is fired. Now, of course, if I reload, I expect LinkedIn to be fired. That works, too. I had already given the consent. And if I now, for example, say ah no, LinkedIn I don't want so, ah, I put it in a performance, here LinkedIn Insight Tag, I don't like that, for whatever reason, save service. And then, if I navigate further on the page or get to the next page, we also see that LinkedIn is not fired. Just like the Consent describes that as well. And if I accept everything again, then we see bang again, LinkedIn is fired, the data is passed through. So. With that, we're through, through the hands-on. And let's move on to the Key Takeaways.

The Key Takeaways

Dinh Bao Dang: What can I take away from today? So you can easily integrate and use Usercentrics using the Adobe Experience Platform Launch Extension. Adobe Experience Cloud products can be connected to consent in a few clicks, and you can also integrate 3rd party services and, of course, control them by support. And last but not least, no JavaScript is required. I configured everything in the UI, and you don't need a developer to do it. Here I have written down a few more links for you, which you can also read at your leisure after the webinar. So. And now I'm looking forward to your questions.


Hanni Gummel: Yes, excellent. Thank you very much for these exciting insights—small moments. So. Now we're going to get into the Q&A. And now you have the opportunity to ask your questions directly to the experts. Feel free to use the question window again in the control panel in the webinar, and otherwise, feel free to use the time now to ask the questions. So, the following question.

Is the extension also available for Google Tag Manager?

Dinh Bao Dang: Pascal, would you like to answer that?

Pascal Riedel: I am happy to answer as well. There is no extension for Google Tag Manager from us directly and especially not with diva-e. diva-e focuses on Adobe Launch as far as I know or on Adobe Platform. We only have guides for Google Tag Manager, which is then very manual at the moment. There is, I think, but there is no dedicated extension for Google's Tag Manager now.

Hanni Gummel: All right, thank you very much. Next question.

Does the extension cost anything?

Dinh Bao Dang: No, you can download it from the store there, as I just demonstrated earlier. And, exactly, it doesn't cost anything. So there are some extensions on Adobe Launch that cost money, but ours is not.

Hanni Gummel: And next question.

Can I also use it to control Google Analytics?

Dinh Bao Dang: Yes. With that, you can also control the Consent of or for Google Analytics within Adobe Launch. So if you install Google Analytics via GTM, you have to do that with GTM. Still, if you run Google Analytics via Launch, we can also control the consent to allow or disallow tracking events with our extension.

Hanni Gummel: Okay, thank you very much. Further questions. Here.

Can I implement Usercentrics independently of Launch?

Dinh Bao Dang: Exactly. You can also implement it manually, write JavaScript to it, and bring it directly to the website. With Adobe Launch, you have the convenience of a UI and the flexibility without having a developer to, yeah, change the implementation or change rules, add new rules. And, exactly, that's the benefit of Adobe Launch. But theoretically, you can also implement everything by hand, on foot.

Hanni Gummel: Thank you very much. And one last question.

Does the whole thing also work with, I hope I'm pronouncing it right, TCF 2 from Usercentrics?

Dinh Bao Dang: Exactly. Our extension doesn't have TCF support yet. But, yeah, maybe Pascal can say something more about that.

Pascal Riedel: It's a bit more complicated with TCF because there are no rules necessarily tied to whether a tag fires or not. Usually, the tags all run simultaneously, which would then make the whole tag management system obsolete. So at the moment, it's not envisioned. But, as Bao says, it's also possible that something like this will come again in the future and that we will then make another customized version with TCF support.

Hanni Gummel: Wonderful, thank you very much. I think that's all the questions for now. If you have any further questions, please feel free to contact us at usercentrics@diva-e.com. The Bao and the team are looking forward to your questions and exchanging them with you. And of course, we will provide the recording and the presentation afterwards. And that's the end of it. We thank you for your participation and your questions. And a big thank you also to our speakers for this exciting input and the tremendous hands-on today. We wish you all the best. See you next time. Have a good day. Stay healthy. Ciao, ciao.