>< Lynx Consentimiento · Technical cookie compliance

Real inventory, prior blocking, a correct banner, Consent Mode v2 and verification

Real
inventory by crawling your site, not a generic list
0
non-essential scripts before consent
=
accept and reject with the same visibility and the same clicks
CMv2
Consent Mode v2 verified in GTM, Analytics and Ads
Home
The problem
What is included
How it works
Who it is for
Questions

Why the banner you have probably doesn't work

Not because of the wording. Because of what the page loads before the user decides.

Everything loads before accepting

Analytics, the Meta pixel, the map, the YouTube video. The banner is there, but it blocks nothing. It is the most common failure and the easiest to prove with browser tools.

"Reject" hidden under "Settings"

Accept on a big button; reject two clicks and a grey panel away. The Spanish DPA's guidance calls this out explicitly, and so do inspectors.

Cookies you didn't know you had

Modules, themes and third-party widgets bring their own scripts without the owner knowing. The cookie policy lists four; the site sets twenty.

The banner was fixed and measurement broke

Blocking bluntly leaves Analytics and Ads blind. Consent Mode v2 exists to keep modelled measurement while respecting the user's choice, but it has to be configured and the signals verified.

Lynx Consentimiento fixes all four at once, and checks afterwards.

What Lynx Consentimiento includes

Technical implementation and verification. Legal validation of the texts belongs to your legal adviser.

Real inventory

Crawl of the site to identify every cookie, local storage entry and third-party script that loads, including those brought in by modules, themes or integrations without the owner knowing. We document what each one loads, for what purpose and when.

Prior blocking

Configuration so that nothing beyond the strictly necessary runs before consent: measurement tags, advertising pixels, maps, embedded videos, fonts and external resources. It is the point most implementations fail.

Consent layer

Notice with accept and reject equivalent in visibility and number of clicks, granularity by purpose, accessible withdrawal and a record of what was consented.

Consent Mode v2

Configuration of consent signals in Google Tag Manager, Analytics and Ads, verifying that they are transmitted correctly and that measurement behaves as it should in each state.

Documentation

Cookie policy written from the real inventory, with the table of cookies, purpose and duration. Review of the site's legal texts against the requirements of the Spanish LSSI-CE and LOPDGDD.

Verification

Post-implementation check with audit tools and review of network requests before and after consent, with a report of the final state.

Scope: technical implementation and verification service. It does not include legal advice and does not replace validation by a legal professional.

How it works

First look at what really loads. Then block, configure and verify.

01

Crawl and inventory

We go through the site as a new user and record every cookie, storage entry and third-party script, who sets it and when. That inventory is the basis for everything else.

  • Cookies
  • localStorage
  • Third-party scripts
02

Prior blocking and consent layer

We configure the consent platform (yours or the one we recommend) so nothing non-essential loads before the choice, with equivalent accept and reject and options by purpose.

  • CMP
  • Prior blocking
  • Granularity
03

Consent Mode v2

Consent signals in Google Tag Manager, Analytics and Ads, and a check that each tag behaves according to the chosen state.

  • GTM
  • GA4
  • Google Ads
04

Verification and documentation

Review of network requests before and after consenting, a report of the final state and a cookie policy generated from the real inventory.

  • Network requests
  • Report
  • Cookie policy

Who it is for

Sites and stores that measure, advertise and don't want compliance and measurement to get in each other's way.

  • Stores investing in Google Ads or Meta

    Without Consent Mode v2 properly configured, conversions stop being attributed and campaigns optimise blind. Here compliance and performance go together.

  • Sites with many modules and widgets

    PrestaShop, WordPress and WooCommerce accumulate third-party scripts with every module. The real inventory is usually a surprise.

  • Anyone who has received a request, or wants to get ahead of one

    If the DPA or a client has asked, or if you would rather not wait for them to, the verification report documents the state before and after.

Related services

Consent is one piece of your site’s measurement and security.

Google Ads campaigns

With measurement and consent properly set up, campaigns optimise on real data. We manage Ads with conversion tracking included.

See Google Ads

Lynx Auditoría Web

Headers, session cookies, third-party scripts and site exposure, reviewed from a security standpoint.

See the audit

Web maintenance

Every new module can bring a new script. Under maintenance we review the inventory whenever the site changes.

See maintenance

Frequently asked questions

Which consent platform do you use?
Will I lose data in Analytics?
Does this guarantee I comply with the law?
How long does it take?
Do you maintain it afterwards?

We look at what your site loads before anyone accepts anything

The URL is enough for the first crawl. We tell you what loads before consent and what it would take to fix it.

Contact us, don't be afraid.
Chat on WhatsApp