BlogCompliance guide

What a CMP does, and when your website needs one

A consent banner is the visible part. Script control and choice records are the work behind it

Tawthiq team4 November 20263 min read

A central consent panel connects to browser tiles through gated paths

A consent management platform, or CMP, collects visitors’ privacy choices and helps apply them to the tools on a website. The banner is its visible interface. Behind it, the platform may store choices, control scripts, send consent signals and keep a record of the notice a visitor saw.

Capabilities vary. Some products only display a notice, while others connect the choice to vendor behaviour. Ask what happens after a visitor presses reject, not just how many banner colours you can change.

A CMP does not decide whether a purpose is lawful or make a website compliant on its own. Your business still needs to identify its processing, explain it and configure the platform correctly. This is an implementation guide, not legal advice.

Start with your tools and purposes

Write down the scripts, plugins and embeds your website uses. Include analytics, advertising pixels, chat widgets and embedded media. Record when each loads, what information it receives and why your business uses it.

Decide the lawful basis for each processing purpose. Under the PDPL, consent is the general rule, subject to stated exceptions (articles 5 and 6). Do not classify every third-party tool as necessary just because removing it would make reporting less convenient.

Where you rely on consent, the Implementing Regulations require clear purposes, freely given consent and records that allow later verification. They also require separate consent for each purpose (article 11 of the Regulations). Translate those purposes into controls people can understand, rather than presenting a list of unfamiliar script filenames.

Decide whether a platform saves work

A small website without optional tracking may not need a CMP at all. It still needs to assess its personal-data processing and provide the relevant information. A banner that asks for permission to do nothing adds confusion rather than protection.

A custom solution can suit a simple site if someone maintains its script controls, saved choices and records. Count that maintenance as part of the decision. A consent interface that nobody checks after launch will drift as the website changes.

A CMP becomes useful when several vendors depend on the same choices, marketing changes tags often, or more than one site needs consistent settings. It can reduce repeated implementation work, but only for the integrations and loading routes it actually supports.

Test the behaviour before choosing

Try the platform on a staging copy with your actual scripts. Check whether optional tools remain blocked on the first visit and after rejection. If the product advertises automatic blocking, verify it with direct scripts and tag-manager tags separately.

Test purpose-level choices. Accept analytics while declining advertising, then inspect the requests. If you use Google tools, check how the platform sends Consent Mode signals and whether the chosen mode sends anything before consent.

Check the consent record too. You should be able to establish the time, choices and applicable notice version without collecting unnecessary extra information about the visitor. Ask how you can retrieve those records and what happens when you change providers.

Keep ownership after installation

Give visitors a persistent way to reopen preferences. Withdrawal must be as easy as giving consent, or easier (article 12 of the Regulations). Test that changing a choice stops the processing that depended on it, including on later pages.

Assign someone to review new vendors before they go live. Recheck the configuration after a redesign, a new plugin or a tag-manager release. Compare the live tools with the policy so the explanation matches the behaviour.

Use the website preparation guide for the inventory and policy work that a CMP cannot do for you.

References

  1. Personal Data Protection Lawsdaia.gov.sa
  2. PDPL Implementing Regulationsdgp.sdaia.gov.sa
  3. Google Consent Mode overviewdevelopers.google.com
  4. Five steps for your websiteBlog