Get a closer look at Termly’s privacy compliance tools in this hands-on product workshop from the 2026 Termly Partner Summit.
Join members of Termly’s Client Success, Product, and Technical Support teams for a walkthrough of the platform, including features designed to simplify privacy management for agencies and businesses managing multiple websites. Explore bulk website management, customizable consent banners, WordPress and e-commerce integrations, regional consent settings, multi-language policies, and Google Consent Mode v2.
The session also covers advanced cookie configuration, Termly’s Partner API, and practical tips for implementing, testing, and maintaining consent management across your websites.
Read the transcript
0:04
Perfect.
0:05
So, again, hello everyone, and thank you very much for coming to Termly's 2026 Partner Summit.
0:13
This is going to be our last session of today. We're going to have a product workshop.
0:18
We're going to have a live walkthrough of the Termly platform, plus some tips and tricks that will help you to get more out of the interface.
0:26
I will be your host. My name is Cami Hernandez. I am the Client Success Manager here at Termly, and today I'm accompanied by three of our team members.
0:34
The first one is Ronald Laz. He is our Product Marketer.
0:38
And then two other Technical Support Engineers, Raouia Belhiba and Rogelyn Pizon.
0:44
By the way, Roge has been unable to turn on her camera, so I apologize for the inconvenience.
0:50
But again, she's going to be able to share her screen and do the presentation as normal. Now let's go to the topic at hand.
0:59
This is going to be the agenda for today.
1:01
We're going to start with a rundown of the platform, showing you a little bit of how it works.
1:06
But we're going to just focus on the managing of multiple domains, multi-site setup, management, and a couple
1:13
of new things that we developed that I want to show that's going to make the lives of our agencies a lot easier.
1:20
Then we're going to go through the integrations and the third-party connections that we have, such as WordPress Plugin, sorry, and the e-commerce platforms that we work with.
1:29
Then we're going to go with geo-regions, translated policies, and Google Consent Mode and Analytics.
1:35
I know this is an important part for our customers, so please be attentive to it.
1:40
And lastly, we're going to go through the advanced cookie configuration and some of the API support.
1:47
Please also have in mind that you can find some resources under the Resource tab here on the webinar.
1:54
Those are going to be some useful articles that might be helpful for some of the questions that you can have. So without further ado, let's begin.
2:03
So as I was telling you, for those of you that are not part of the Termly family yet, this is how the interface looks.
2:11
It's a very, very user-friendly tool. There's not a lot of things that can go wrong with it.
2:17
I'm going to give you kind of an overview, but very high-level, of how it works because, as I said before, today we're going to focus on those agency features that we have available for you guys.
2:29
So this is how you're going to see all of your customers.
2:32
As I said before, the good thing about the agency program is that you are able to have all your customers under one account, under your umbrella.
2:40
This means also that you will have centralized billing for all of them.
2:45
And then you can decide how you want to charge your customers, right? Of course, this comes with discounted tiers.
2:51
Once again, if you need information on anything, please feel free to reach out to anyone on our team, and we can give you further information.
2:59
So let's show you guys a little bit of what we have.
3:02
We have the consent management, everything related to the scanner of cookies, the scanner itself, how to classify them all in buckets.
3:12
We also have the consent banner. It's fully customizable. We are improving this part every day, literally.
3:21
Also, we have a bunch of languages that your customers are going to be able to access.
3:25
This is something that Ronald is going to speak of later on.
3:29
We have consent logs, Google Consent Mode, as you know, something that we're also going to talk about in this session.
3:35
Right now we have 10 different policies available for our customers.
3:39
Building the policies is really the easiest thing in the world.
3:42
You just have to answer a couple of questions about your customer's company.
3:47
And even when the questions might be a little bit difficult, we do have these things that are going to give you more information on what exactly are we asking for, why are we asking for those things.
3:59
This being said, let's go to the part that I was telling you about before.
4:05
So what are the things that we have available for the agency?
4:08
So besides being able to have all of your customers under the same plan and under the same umbrella,
4:15
you will also be able to add different users to the platform. Right now we have two types of users. The first one is going to be the administrator.
4:24
I will always advise this to be part of your company, your account managers, or someone within your
4:32
enterprise because this person is going to have access to billing and all your customers' accounts and just about everything that you have on it.
4:40
And the second one, and the most useful one for our agencies, is the editor access.
4:45
So this is normally for your customers. You can give them access to specific domains, and they can collaborate with you within these domains.
4:54
They won't have access to anything related to billing or to any other of your customers, but they will be able to log in, maybe help you
5:02
answering some questions, getting the codes to install, or whatever it is that you need them to do.
5:09
After that, we have the most useful thing and the thing that we've been working on for the past few quarters within Termly, and it is our dashboard.
5:20
So a couple of cool things on the dashboard.
5:22
Once again, you're going to be able to see all of your customers by name and URL, the creation date of each of the sites.
5:29
This normally is for billing purposes for you guys.
5:33
Banner status, cookie status, last time scanned, banner views, and policies.
5:38
And the thing that I wanted to talk to you about today, that is a new thing that we have, are the tags. So you're going to be able,
5:46
for example, I have customers in the UK and in the U.S., and I have 2,000 customers within Termly.
5:53
Hopefully, I can tag them to be either U.S. or UK. In this case, I can tag templates that
6:02
I'll show you why these are tagged as such. We can put, as you can see here, several, several templates. I'm sorry, several tags.
6:11
So if, for example, it's a U.S., but it's also California, and I want to put something else like that, it is possible. Very easy to do, as you can see.
6:20
Just click on the little pencil there, add them, remove them, and that's it.
6:27
Now as you can see, and as I was saying, this, for example, is marked as template.
6:32
And this brings us to the second thing that we wanted to show you guys. That is the option to copy settings.
6:39
So this is a very requested thing from our customers from before, and as I said, we've been working on it.
6:46
So when you select a site and you go to Copy Settings, as it says here, you're going to select here the source that you're going to copy from.
6:55
Very important to have that in mind. And for example, I'm going to choose this one.
7:01
I can either copy the banner or consent settings or copy, in this case, the privacy policy, because these sites only have the privacy policy.
7:10
If I choose any other site that might have more policies, I will also be able to copy those policies onto the one that I selected before.
7:20
The last thing that I'm going to be able to do is to remove all other documents from the target website. Again, easy to do.
7:28
I can do it with multiple sites. So for example, if I want to copy it onto, let's do something, let's use both.
7:36
I want to filter by U.S. region and then copy settings onto these four. That is something that we have available.
7:45
If you have a lot of customers, this is very useful for you to kind of do these things on your own.
7:50
We had it before, but it was a very manual process from our end. You had to reach out to us, and then we could do it.
7:57
Now you can do it by yourselves. This dashboard and these kinds of options to manage multiple customers,
8:03
it's something that we are working on all the time, as Juan showed in one of the sessions before.
8:09
So please, I just can't tell you enough to be aware of what's coming and a lot of things that we are developing for our agencies.
8:20
If you have any questions, I'm going to leave my information here on the chat. Feel free to reach out at any point.
8:27
And I think that's it from my end.
8:31
Now I want to introduce and give a warm welcome to our next speaker.
8:36
Rao is going to talk to us about the integrations and third-party connections, such as WordPress plugins and all the e-commerce platforms that we work with.
8:45
So Rao, the floor is yours.
Thank you, Cami.
8:49
So for my segment, I'll focus on the e-commerce side from a technical perspective, specifically how Termly integrates into e-commerce websites without disrupting store functionality.
9:01
And I'll be using WordPress as the example since it is currently one of the most
9:09
used platforms by users, but the same technical principles apply to other platforms.
9:20
So I'm going to start by sharing my screen.
9:30
So e-commerce websites are some of the most technically complex sites to maintain.
9:36
They usually rely on multiple third-party scripts running at the same time.
9:42
Analytics tools, marketing pixels, payment providers, checkout logic, and lots of plugins all layered together.
9:50
So from a technical standpoint, the biggest risks are scripts loading in the wrong order, scripts loading more than once, plugin conflicts, and unintended impact on checkout flows.
10:05
So when you integrate any additional tooling into an e-commerce site, stability is critical.
10:14
So WordPress e-commerce sites add even more complexity because scripts can be injected in multiple ways.
10:22
So they can come from an active theme, a child theme, a plugin, or tag manager.
10:31
So this makes manual script management risky, especially on stores that update themes or plugins frequently.
10:40
So the goal with Termly is to integrate in a way that minimizes manual edits and ongoing maintenance while still giving you proper consent and policies.
10:51
So I'll start on WordPress, and that's by installing Termly's plugin.
11:00
So in the WordPress dashboard, you go to Plugins and search for Termly, click on Install Now.
11:24
And once installed, activate it.
11:28
So once the Termly plugin is installed and activated, there's no custom code or theme editing required.
11:36
You just go to Termly here and go back to your Termly dashboard, browse to API Key Settings, and then API Key, Copy to Clipboard.
11:48
Once copied, you go back to your dashboard, the WordPress dashboard, and paste in your API key and click on Save API Key.
11:59
So adding the API key here establishes a direct, stable connection between the WordPress site and the Termly dashboard.
12:09
So that means the banner, the cookies, are all managed centrally in Termly rather than being hard-coded into the website.
12:22
So as you can see here, now I have everything here.
12:26
So as you can see, Cookie Management, I can see my cookies. They're the same that appear in your Termly dashboard in the cookie report.
12:39
And that's what I meant by you can manage everything centrally here in Termly, and you'll see them reflect here.
12:46
So this is the website.
12:48
Before I turn on my dashboard, I turn on my consent banner. Sorry.
12:52
And when I go back to Cookie Management here at Termly and I click on this toggle, it's turned on. Refresh, and the consent banner is appearing.
13:06
So after the API key is added, the site stays in sync with the configuration you manage in Termly.
13:14
So in practice, that means no need to edit header or footer files, no need to
13:20
reinject scripts after theme updates, and far less risk of accidentally duplicating code.
13:28
So for e-commerce sites, this is especially important because checkout pages are extremely sensitive to changes.
13:36
So the integration is lightweight and designed to coexist with existing e-commerce scripts.
13:44
I'm going to show you how to embed a policy now on your WordPress site.
13:50
So as Camila said, this is the list of policies that we provide today.
13:57
I'm going to take the example of the privacy policy, but literally they all embed in the same way. We have three ways of embedding the policy.
14:06
It's via HTML, a code snippet, or the URL. I go back here and go to Pages and Add a Page.
14:20
I'm going to grab the code now. I'm going to use the HTML format. Go back here. Let's name our privacy policy.
14:27
Let's name our policy.
14:29
Privacy Policy or page, choose block, click on the plus sign, Custom HTML, and preview. Boom.
14:39
You have your policy ready to be used. Of course, click on the Publish button. For the code snippet,
14:48
the same applies.
14:51
So I would go to HTML, add the HTML tag, and just paste the code.
15:01
And when I click on Preview, boom.
15:04
Also, your policy is here. For the last option, which is the URL,
15:10
you can use it within your pages as a hyperlink or in the footer section.
15:16
I'm going to show you how it reflects or how it shows.
15:20
So you would simply do this, and you'd see it here, as simple as that.
15:28
So also this is for the policy part.
15:35
So when we talk about the ease of use of e-commerce, we're not just talking about the first-time setup.
15:42
We're also talking about how this behaves across different domains and subdomains over time.
15:49
So we have something called the Domain Rules that lets you define how Termly behaves on specific domains.
15:58
You set the rules once, and Termly applies the right behavior in the background.
16:03
So it's found under Consent Management, and then you click on Domain Rules.
16:08
So for a technical team, that means less custom blocking logic and fewer one-off fixes.
16:16
For a store owner, it means the consent experience stays consistent while everything like payment flows and forms,
16:25
apps work as expected.
16:27
And from an e-commerce perspective, the combination of the WordPress plugin and the policy URLs, embeds, and Domain Rules give you something that's easy to roll out and easy to maintain.
16:38
So how it works is that you would click on Edit Domain Rules.
16:43
Let's say you have a script that is blocked because it's not essential and the Auto Blocker is blocking it.
16:50
You'd simply take that script and add it either at the account level
16:54
if you have several websites that use the same script, or for this website only. You would categorize it as
17:02
you want, whether it be essential, advertising, analytics, performance, or social, and click on Save, and the changes would reflect on your website within seconds.
17:14
So one of the most common questions that we get from e-commerce teams is that, is this safe to use on a live store?
17:22
Is there any risk to checkout?
17:25
So this integration is designed specifically for live environments.
17:29
It avoids direct edits to sensitive templates and instead centralizes configuration in Termly.
17:38
So cart logic, checkout flows, continue to run as usual, and that's the goal for Termly,
17:47
that is to give you consent and policies without becoming another fragile part of your website.
17:56
So today I used WordPress as the example. Today,
18:03
I used WordPress as the example because it's so common, but the same principles apply to other e-commerce environments, whether it be Shopify or custom builds.
18:12
And I'm going to show you here what I'm talking about.
18:15
When you click on Consent Banner, you'd see the button Install and second step, which is Embed the Consent Banner,
18:24
after, of course, your website scan is done. And these are the support articles that we provide currently, but simply
18:33
our plain HTML, which is here, you would grab this code and add it to the header section of your website, and that's it.
18:45
Nothing else to be done. So a recap here.
18:51
The focus for Termly on e-commerce sites is really three things.
18:56
Ease of integration, especially via the WordPress plugin.
19:00
Like I showed today, stability around critical flows, and maintainability over time, like Domain Rules and centrally managed policies.
19:12
So we connected a WordPress site, looked at how a policy can be exposed with a simple URL, and how the same process applies to other policies as well.
19:22
So that's the workflow I wanted to walk through today, and I'm happy to take any technical questions by the end of the session.
19:30
Back at you, Cami.
All right, thank you very much for that, Rao.
19:37
So now let's welcome our next panelist.
19:41
Ron is going to talk to us about geo-regions, translated policies, and finally, a very important topic: Google Consent Mode and Analytics.
19:49
Go ahead.
Hi everyone. Just to check, can you guys see my presentation?
We can see it. Yes.
Yeah, great.
19:59
So hello again, everyone. Thank you for joining our Partner Summit.
20:02
So for today's product workshop, for this specific session, I'll be talking about, the first one would be geo-regions and then multi-language
20:11
policies, and then by the second half, that would be Google Consent Mode and Analytics. So let's dive right in.
20:18
Let's talk about why it is important to have geo-regions and a multilingual policy.
20:22
As you guys know, website owners or websites should be, visitors, sorry, should be visible across different visitors that are coming from different parts of the world.
20:33
That includes regions that have different compliance requirements from one another.
20:38
One might have stricter compliance laws or regulations compared to one that has much more relaxed laws.
20:44
And then these are the policies that you have on your website or tools that you have on it should adjust based on the local laws and regulations for your visitors.
20:55
Luckily, Termly supports businesses that operate worldwide, and we allow you to set different consent settings and behavior for each region.
21:04
This accommodates policies, consent banners, and many more. So how do you do it? It's very simple.
21:12
Under your Termly dashboard, you simply head over to your Consent Banner tab, and then from there, just scroll down a little bit. You would be able to see Regions.
21:21
Right now, Termly supports five regions, namely Global, and then we have two separate regions for the U.S.
21:28
The first one having much stricter laws, and then the second one would be the much more relaxed one. And then we also have Europe, Brazil, and Canada.
21:37
So let's try to discuss it one by one. For the U.S.,
21:41
as I mentioned, one on the left side is those states which have much stricter privacy laws.
21:48
That includes California, Colorado, up to Virginia.
21:52
While all of the states that are not mentioned on the list will fall onto the right part, which is All Other States.
21:58
These remaining states of the U.S. do not have, or do not have strict privacy laws.
22:04
They might offer the more relaxed version compared to the list on the left one.
22:11
Okay, these are also the lists of some of the privacy laws that are covered under the states with consumer privacy laws.
22:20
That includes California CCPA, Colorado CPA, all the way again to Virginia VCDPA.
22:27
So there's many more, but these are the common ones that are being covered by this category of states with consumer privacy laws.
22:35
Then going forward with the other regions we have here, Canada using or covering with PIPEDA and then Quebec's Law 25, and then Brazil's with LGPD.
22:46
Now, how Termly determines whether your visitors are falling under certain regions is based on their IP address.
22:55
So when they are visiting with a Canadian IP address, then Termly will be able to show them the configuration that you configured towards those Canadian regions.
23:05
And then the same thing for Brazil and then for the U.S. Also, we have Europe for GDPR compliance, and if your users are visiting outside
23:15
of Europe, Brazil, Canada, and the U.S., they will likely fall towards the Global configuration of the Termly dashboard.
23:24
Sample coverage under the Global region would be Australia's Privacy Act, New Zealand, and then South Africa, and
23:31
then as mentioned earlier on the previous session, we have many more data privacy or compliance regulations
23:39
that we're covering, and then you can explore those on the list that we will be sharing on the support article later or via chat.
23:46
So how do you configure geo-regions on your dashboard?
23:50
Once again, on the Consent Banner tab, you will be able to select which region first that you will be configuring.
23:57
And then under the region, for example, here we have Global, you will be able to set different settings based on the compliance that you're working with.
24:05
So for Global, you will be able to set if ever you want to enable the consent banner, toggle the Decline button or the Preference button. You will
24:15
also have consent behavior and then Google Consent Mode that we will be talking about in a bit.
24:21
One thing that I would like to note is that the settings that you're configuring on Global are different from the settings that you will be
24:29
configuring for Canada, let's say, or for Europe. So those specific settings allow you to have different
24:35
configurations so that you can comply with different laws that you're complying with.
24:41
So if ever you're not sure, let's say you want to enable the banner, you want to enable Google Consent Mode, or you're not really sure how to do those things,
24:51
Termly offers the default settings, which cover those privacy laws like GDPR or CCPA by default.
25:00
So simply head over to your Consent Banner tab, and then you will be able to see this link highlighted in blue to reset the recommended settings for all regions.
25:09
Or if you're only working for a certain region, then you can use the setting down below.
25:16
Okay, moving forward, we also have here the multi-language policies.
25:20
It is very important because businesses operate in different countries or different spectrums around the globe, and then
25:29
some regulations often require your policies to be presented in the local language of your visitors.
25:35
This not only builds trust but also offers transparency between the business owners and then those website visitors that are checking your website or checking your businesses.
25:46
On Termly, we are offering multilingual policies for these policies that we have, starting from the Privacy Policy, Cookie Policy, all the way
25:56
to the new policy template that we released this January, which is the Accessibility Statement. And then here are the supported languages.
26:04
English, German, Spanish, Italian, all the way up to Greek.
26:07
But right now we're still working on expanding these languages based on the demand by our users.
26:13
So if ever you're looking forward to different languages, or different, what do you call this, different languages here,
26:22
just feel free to add it on our feature list, or feel free to add it on the chat, and then we'll take it over for you.
26:30
So how it works, as Rao mentioned earlier, we have three different ways of adding the policies to your website, namely the HTML format, the code snippet, and then the URL option.
26:41
However, for a multi-language policy to work, you will only be able to do this by using the code snippet and then URL.
26:49
So I would like to emphasize that HTML format is not supported with multi-language policy.
26:56
So yep, moving forward, the first step would be to install either the code snippet and then URL, and then you're done. Once the website visitor hits your website,
27:06
and then they have a browser language that is different from English, like what I have here. For example, they have an Italian browser language.
27:16
Then the policy that you have in English will automatically be translated on their view like this.
27:23
So no need to add this feature, no need to add something difficult. Termly handles this by default for your end.
27:30
As long as the browser default language is one of the supported languages that we have, then your policies will automatically be translated.
27:38
So in the case that you don't want the translated version of Termly and you only want the English version, simply reach out to customer support, and then we'll have it disabled on your end.
27:49
So that's it for the geo-regions and multi-language policies.
27:52
If you have any questions, feel free to drop it on the chat or on the Q&A button on your screen.
27:57
We'll be now heading over towards Google Consent Mode and Analytics.
28:02
So as you guys know, the consent management platform or the consent banner that you add on your website greatly affects the data that you are able to collect from your users.
28:13
So when the user clicks the Accept button, you will be able to expect full data collection based on your consent
28:19
banner, or when the user declines it, you will have a limited amount of data or no data at all.
28:27
So it really depends on the consent management platform that you're working with.
28:31
But there are also other things that you can consider. The first one would be, again, the regions, like what I've discussed earlier.
28:37
Some regions have strict privacy compliance laws or regulations. Some have a relaxed version.
28:44
So having a consent management platform that allows you to configure different settings for different regions will greatly affect the amount of data that
28:53
you can collect from your users and, again, will also greatly affect how you can comply with those different requirements from different regions.
29:02
Other things that you can consider aside from regions would be the consent behavior and if the consent management platform supports this.
29:09
So consent behavior typically falls into two different categories. The first one is opt-in.
29:15
Opt-in is usually applied for those regions that have strict compliance, such as GDPR or CCPA.
29:23
Basically, opt-in simply means to not accept immediately when the visitor visits your website.
29:30
Their data will not be collected at all until they click the Accept button on the consent banner.
29:36
And then also the opposite of the opt-in would be the opt-out behavior.
29:40
This behavior is usually applied for those regions that have relaxed laws, such as Global and then U.S. with relaxed privacy compliance regulations.
29:51
So basically, opt-out means that user data will be actively collected until they click the Decline button on the consent banner.
30:00
So once you know that regions and consent behavior are very important, we have good news for
30:07
you that Termly supports both of them, which is the regions and then the consent behavior. Not only that Termly supports these two categories,
30:16
we also offer Google Consent Mode, which is very important.
30:20
So a brief discussion about GCM would be, once you add or once you enable Consent Mode on your
30:27
website or on your consent management platform, it allows your website to read and adjust the Google tags that you have on it based on the consumer preference.
30:37
So it is important because if your website is using Google services to track online behavior, you will be punished by law if you're not using Google Consent Mode.
30:46
So yep, it is a legal requirement based on their services.
30:53
So right now, Termly is one of the Gold partners of Google when it comes to their CMP Partner Program.
31:00
Every year we strive to fully commit to building compliance and building ease of use towards our users.
31:09
So how to enable? Oh, sorry.
31:10
Before we discuss how to enable Consent Mode, I would like to inform you first about the two different Consent Mode versions that we have.
31:20
The first one, you can use the Basic Consent Mode. This is the simplest version.
31:24
It simply means that until the user interacts with the consent banner, either they accept or they decline,
31:33
this will block Google tags until the user accepts it. Meanwhile, you have here the Advanced Consent Mode.
31:40
So this is the advanced version that allows you to grab some data even if the user clicks Decline.
31:46
So what it does is that when the website loads, before the consent banner loads fully,
31:52
it will send cookieless pings from the website data towards Google Analytics.
32:01
So this ping is essentially anonymized information and does not contain information that may track the user, such as IP address or any user identifiers.
32:12
So both of these configurations are available on your Termly dashboard.
32:17
So one more thing, Google Consent Mode, the advanced version on the Termly dashboard, allows you to set
32:24
default states for each parameter so that it gives you the option to only select which kind of
32:32
parameter you would like to have or you would like to accept on your dashboard.
32:36
So listed here are ad storage, user data, personalization, analytics storage, functionality, all the way to social storage.
32:44
So every time there's some update with Google Consent Mode, Termly ensures that this list will also be updated.
32:53
So how to implement Google Consent Mode with Termly? It's very easy.
32:57
On your Termly dashboard, you have the Google Consent Mode tab specifically, and then you have six steps, very simple.
33:06
First is the basic, common: add the website to the Termly dashboard.
33:10
Make sure to scan it so that the cookies will be able to be listed on our cookie report.
33:17
And then step three would be configuring Google Consent Mode. So this is how it looks.
33:23
Once you click step three, you will first then select a region, either from Global, U.S., Canada, Brazil, or Europe.
33:31
And then from there, you will be able to select which Google Consent Mode option you would like to enable for this region. For example, on Global,
33:40
you want to have Basic, but for America or U.S., you would like to have Consent Mode.
33:46
So it's very possible to do that using the Termly version of Google Consent Mode.
33:51
So going back again, once you add the Consent Mode, make sure to embed the consent banner to your website and then the Preference Center link.
34:00
Step four and step five ensure that your users have a way to communicate their consent preference to the website towards Google Consent Mode once added.
34:14
Finally, you have your step six here, which is a very new feature from Termly, which is the ability to scan whether Google Consent Mode has been implemented successfully.
34:24
So previously, website owners tended to do this manually by checking their website code, checking their
34:32
website's Google Tag Manager, and then checking with Termly to make sure all those three departments have been linked in successfully and make sure
34:40
that they are receiving their data from the visitor's starting point towards their analytics dashboard.
34:48
So yep, once you click the Scan button on step six, you will be able to see this email whether you pass or you fail.
35:01
So when you fail the compliance, you will see the email that contains the legal, sorry, why it is important to make
35:10
sure that you pass the compliance and then what are the steps you need to do to make sure that the next time you scan it, it will be successful.
35:20
And then if you're still having any issues or you're still having any troubles passing the compliance
35:27
checklist, we also listed here the support articles that you can visit, and luckily, you also have a
35:34
dedicated support team that can help you address the concerns that you might have when you run the Google compliance checklist.
35:43
So that's basically it for my session with regard to Google Consent Mode, Analytics, geo-regions, and multi-language policies.
35:51
Once again, if you have any questions, feel free to drop it on the Q&A, and we'll answer it at the end. Thank you. Back to you, Cami.
Thank you, Ron.
35:59
So as Ron was saying, feel free to leave your Q&A questions on the Q&A button.
36:05
But also, I left my contact on the chat just in case you guys actually need a session to go through all of this.
36:12
We are fully available, so just feel free to shoot an email, and we will set that up. Now for our next speaker,
36:18
as I said, Roge doesn't have her camera on, is unable to put it on.
36:23
So sorry for that, but she's going to talk to us about the advanced cookie configuration and the API support. So Roge, go ahead.
36:32
Yes, hello. Hello, everyone. I apologize for my camera. Zoom has failed my camera.
36:41
So, I apologize. So I'm going to share my screen right now.
36:45
Please let me know if you can see my screen right now.
36:54
It's loading. We can see it now, right? Okay.
36:58
So I'll be guiding you through advanced cookie configuration and the API.
37:08
So our goal is to make sure you not only understand the technical steps, but also feel confident applying them to your own setup.
37:16
This matters because effective cookie configuration helps you to stay compliant with regulations, build
37:25
trust with your users, and ensure your data practices are transparent and accurate.
37:30
So by mastering these steps, you'll be better prepared for audits, common pitfalls, and create a smoother experience for your visitors.
37:40
So what is an advanced cookie configuration?
37:44
So advanced cookie configuration means taking control of how cookies are categorized and described.
37:49
This ensures your consent banner reflects exactly what's happening on your site.
37:54
So it is beyond just scan results. You need to manage cookie data.
38:03
This is the step-by-step workflow we recommend.
38:07
First is start with a scan, then refine the results by categorizing, adding, and editing cookies.
38:16
You may notice that there's a step to add missing cookies.
38:21
So while Termly's scanner automatically detects most cookies, sometimes certain scripts or third-party tools aren't picked up.
38:29
So by manually adding those cookies, you stay compliant, build trust, ensure accuracy, and prepare for audits.
38:39
So in categorizing or editing the cookies,
38:43
so after a scan, review each cookie to confirm it's in the right category.
38:48
So this is under Consent Management and Cookies option here.
38:53
For instance, a marketing pixel may appear under Analytics. This is your chance to fine-tune the categorization.
39:01
So adjusting cookies here ensures accuracy and a smoother user experience. Think of this step as quality control.
39:10
So the scanner does the heavy lifting, and you simply validate categories to make sure everything aligns.
39:20
So to, sorry, the first step is to click the cookie you want to categorize or edit.
39:31
And then the next step is to add or change,
39:39
sorry, to add or change the category and also the fields that are not grayed out, and then Save.
39:53
Next is in adding a cookie manually. First, click the Add Cookie button as shown in the image
40:04
and then add the necessary cookie information fields.
40:07
Marks with asterisks are required, so be sure to complete those. So don't forget to save your changes.
40:15
So adding cookies manually ensures your website's cookie banner is accurate, complete, and ready for compliance.
40:21
So once this step is done, everything would be good and your website will stay ready for compliance.
40:35
Then that's it for the advanced cookie configuration. We're going to move to the API support.
40:48
The Termly API is valuable for partners because it enables seamless compliance integration, automates client onboarding,
40:58
and saves time with batch updates and cookie scans, so making agencies more efficient and clients compliant from day one.
41:08
So all API details and endpoints or support resources are in
41:13
Termly API documents, so you can visit docs.termly.io. To use the Partner API, you need an API key.
41:27
Termly API uses API keys to authenticate requests and ensure secure access to our services.
41:34
Currently, if you want to use the Partner API, you need to be issued keys manually by us.
41:41
So please reach out to us here at termly.io/agencies to get access, and once approved,
41:50
you'll receive a unique set of credentials, including both a public key and a private key.
41:56
So these keys are specific to your organization and should be stored securely.
42:04
Once you have your key, you can now make your request.
42:08
To make a request, you must include the following two HTTP headers.
42:12
There's a timestamp and authorization, which includes your public key and the signature.
42:20
But since we have a lot of partners reaching out or having a little difficulty with authentication, we have a script to easily access your endpoint without errors or other authentication errors, which we will provide.
42:35
And I'll show you example requests and how you can apply those scripts later. In Termly's API, we support batch request processing.
42:46
This means you can send multiple objects in one request. We have different result statuses.
42:53
For some scenarios, we have partial processing.
42:57
If some objects in the request fail, the rest will still be processed, and you'll see a 207 Multi-Status response.
43:07
For example, you send two objects, two of them failed, but four succeed.
43:18
You're going to have a response of 207, which means Multi-Status. We have
43:26
if all fail, it will respond with 400, which means Bad Request.
43:35
But there's an exception to this rule. In the authorization endpoint, it is all or nothing.
43:42
Which means if you send six accounts but your API key is only valid for five, none will be processed.
43:53
It will be a 403 response.
43:58
So let me share the sample request in Postman and one in JavaScript API calls.
44:05
Let me just, let me just reshare my screen.
44:20
First, I'm going to share with you Postman. Let me know if you can see my screen.
We can see it now. Yes.
44:30
Okay, thank you for confirming. So here we have a few examples.
44:37
In Postman, we have the banners endpoint, authentication endpoint, website scan report, and one POST website.
44:49
So in getting the endpoint, we have the script that we will provide.
44:59
You will only need to add your public key and your private key here that we will give you after,
45:12
and then everything here, including the two HTTP headers, will be here, all the authorization. You don't have to add
45:22
or remove code or something. Here, everything works perfectly.
45:31
You just need to add the public keys and the private keys and also the parameters, including the
45:40
account ID for the banners, and you will see all the information in each endpoint.
45:48
What are the queries or what you can query in each endpoint in the API documentation that you can visit.
46:00
So here, if we send this, you're going to get all the necessary details in the banner in your account.
46:13
We also have the authentication endpoint.
46:17
This is the most asked endpoint, which you will only need to
46:27
add the query or the parameter of the account ID and also
46:34
the script, which will be in the pre-request. It's the same. The script is going to be the same.
46:46
We're going to provide this, and you just need to paste it in the pre-request in Postman
46:55
and just click Send, and you're going to have the response, which is Success, which means you're authenticated.
47:04
You also have the GET website. In GET website, you're going to have to add your IDs and the domain name or the domain, the same thing.
47:18
You need to paste the script that we're going to provide in the pre-request and
47:26
just send, and you're going to get the result.
47:34
So here in the POST, we have the body, which we're going to send to
47:44
the API. You're going to get,
47:47
you're going to have to put the account ID, the name, the URL, scan period, everything here in
47:58
the body. You can get the information on what is required for the body in this endpoint in the
48:10
documentation, in the Termly API docs. The same thing.
48:16
Just add the pre-request script and then the body, and then just send. It will create your website and your account automatically.
48:28
And yes, so that's all for Postman. Let me reshare again for the JavaScript API call.
48:49
So here I have a few examples of JavaScript API calls,
48:56
but we also have for Python and Ruby. It will be uploaded in the Termly API documentation, so don't worry about it.
49:09
So here in this script, we already added
49:16
the necessary code for signing in any endpoint.
49:27
So what you need to do is just add the public key and your private key here, and let's go to the
49:39
function in getting an endpoint, for example, getting a website.
49:46
So all you need to do is the account ID, the IDs, and the domain. Let's go.
49:56
You just need to copy and paste this one and also the
49:59
other necessary script, for example, the timestamp, which is required for
50:08
the header. And yes, we can go to this endpoint, the
50:22
authentication. We also have the GET website, so let
50:35
me test it and see the response.
50:42
So here in this example, we're going to test the authentication, we're going to get the website and the scan report.
50:50
So all you need to do is just run this one, and you're going to see the response here.
51:03
In the logs here, websites are fetched successfully, and then the scan report,
51:14
and also the authentication is successful.
51:17
So this one, this code is going to be provided, so don't worry about it.
51:24
We have Python too, and same as Ruby. Everything here is ready.
51:33
All you need to do is, again, add your public key and the private keys, and I think that's all for the API.
51:43
Let me get back to you, Cami.
All right, perfect.
51:51
Thank you, Roge, for that.
51:53
So now let's go to some of the questions that you guys sent out on the Q&A card. The first one from Mark says, "What about Webflow?"
52:02
Any widgets planned in the future to manage this easier?
I think I can do that, Cami.
52:12
For now, we don't have a specific integration with Webflow similar to what we have with WordPress that allows you to simply click the Enable button and everything will work.
52:23
For other platforms such as Webflow, you will need to work with installing the consent banner
52:30
script, adding the Preference Center link to be able to add Termly to it. But that's a great feature request.
52:36
We're very happy to open a discussion with our product manager to be able to include it in our roadmap in the future.
52:45
Great, thank you.
52:46
The next one says, "How do we know that the Termly consent banner is working and not allowing the GTM tags, I suppose, to fire without going to Tag Manager?"
52:58
Yep, so with regards to Termly and then Google Tag Manager, it will be a very lengthy discussion.
53:05
But for this specific question, the first thing you would need to do is to make sure that you have added
53:11
the Termly template in your Google Tag Manager and make sure that the dedicated Termly trigger has been added to whatever GTM tags that you would like to be blocked.
53:23
Once you have those added, before publishing or making it live, Google Tag Manager offers the option to test it using its Google Tag Assistant.
53:34
So using that tool, you will be able to see which tags are firing whenever you click the Accept button and which tags are blocked whenever you click the Decline button on the Termly consent banner.
53:47
So once again, for any questions for this one, if ever you still have any difficulties installing,
53:56
first I would suggest following our dedicated guide here to Tag Manager implementation, and then as well,
54:03
we have a dedicated support team that you can contact for additional help.
All right, perfect.
54:13
The next one says, "Can you go over the setup in Google Tag Manager to confirm how we should coordinate the Termly consent banner?"
54:22
Okay, I'm going to answer that.
54:25
So there are three parts to coordinating Termly with Google Tag Manager. I'm just going to go through these briefly. So load Termly first.
54:34
Either you load it in the header section of the website with the Auto Blocker turned off, or you inject
54:41
it through the Google Tag Manager template, the Termly template that we offer in Google Tag Manager.
54:48
So you want to have the Termly script load before any other script if you choose option one, of course.
54:58
So adding Termly via the CMP template in GTM, use consent in GTM, not just triggers.
55:06
So have your triggers loaded, have your triggers load.
55:12
Don't let any third-party scripts, all third-party scripts that load through GTM need to have
55:19
the user-provided data trigger in them so they don't fire before consent is given.
55:26
And also test the before and after behavior.
55:29
So make sure that you open your website in an incognito mode. You don't accept any banners.
55:36
Check your local storage, check your network, if there are any scripts communicating in the Network tab.
55:46
You shouldn't see anything like that, and after you accept the banner, you should see them.
55:51
So this is, like, very brief, but if you'd like a step-by-step for your setup, I'd
55:58
be more than happy to review your GTM container and everything.
56:05
Just reach out to Cami, and she'll put you in contact with me.
All right, thank you, Rao.
56:13
Then we have, "How do you make sure that the website's global JS and CSS still load even if the user denies all consent?"
56:23
I'm going to also answer that. So your CSS and global JS are essential.
56:31
So we do that by only putting non-essential scripts under consent control.
56:37
So anything that is essential will not be blocked, including your CSS and global JavaScript.
56:44
Only third-party scripts.
56:46
So first-party scripts do not get blocked because those are essential for your website's performance.
56:53
Only third-party scripts such as analytics, marketing, et cetera, and also those that are unclassified.
57:01
So you don't have to worry about Termly blocking your CSS. It will not.
Yep.
57:07
Sorry, just to add on that, in some cases where websites are built using third-party platforms such as, you know, let's
57:16
say Wix or GoDaddy, sometimes those websites may host your global JS and CSS on third-party scripts.
57:25
So like what Rao mentioned, if those are your case and your website is hosting this on a third-party platform, one tool that you can use is the Domain Rules that were previously discussed.
57:35
Simply add the domain of the JS file and then CSS on it, tag it as essential, and Termly will not block it anymore.
57:51
I was saying, thank you for that, Ron.
57:53
And the last question that we have is from Trevor. It says, "This input of scripts seems really technical."
58:01
I know, I am not understanding why I need to do this API code and where to actually code it in Python or Ruby.
58:09
Do I need to hire a programmer to input this API?
Yep.
58:14
So to clarify your question, Trevor, the previously discussed codes by Roge, the ones on JavaScript,
58:22
Python, and Ruby, those codes are mostly used by our API partners that manage thousands of websites or hundreds of websites.
58:30
So instead of them logging in directly with Termly and managing those websites one by one, we do provide them an option to manage them using the API, which is much faster for them.
58:41
However, for our regular users or for our regular Termly users, you don't need to worry about it at all.
58:46
The functions that are available on the API are very much available on the UI as well.
58:53
All that you can use on the API will be seen on the Termly dashboard as well. So no need to worry about it.
58:58
If you're not an API partner that uses the code that Roge mentioned.
Okay, perfect.
59:04
Thank you very much for that, Ron, Rao, and Roge. And all right, everyone, that brings us to the end of the session and sadly to the end of our Partner Summit.