For agencies and freelancers

Cookie consent for every client site, from one dashboard

Paste one script on each site. Analytics and ad tags stay off the page until the visitor says yes. You run all your clients from one login and pay per site.

No card needed. No contract. Cancel whenever you like.

€2

per site a month, from 100 sites

3

client sites free for 30 days

30,000

pageviews a month for every site, in one shared pool

1

line of code on each site

Price

The more client sites you add, the less each one costs

You pay per site. Bill your clients what you like and keep the difference.

20 sites

1-9

€3.50

10-49

€2.90

50-99

€2.40

100+

€2

€2.90
per site a month
€58
a month in total
€580
a year, with 2 months free

How it works

A client site is set up in a few minutes

The same three steps on every site, whatever it is built with.

<script async src="https://www.consentify.app/api/gateway?token=pk_live_..."></script>


01

Paste one script

One line in the head of the site. It works on WordPress, Shopify, Webflow and sites you have coded yourself.

02

Hand over the tracking IDs

Remove Google Analytics, Meta Pixel and the others from the site, and enter their IDs in the dashboard. Consentify loads them from there.

03

Nothing runs before consent

Visitors get the banner. Tags load only after a yes, and every choice is logged, so you can show what was agreed to.

Moving from another consent tool? npx consentify-migrate swaps it out and carries the categories across.

Under the hood

One page load, line by line

Open the network panel on any site running Consentify and follow along. Every step below leaves a trace you can see yourself, which is a better argument than a list of adjectives.


  1. 01

    GET /api/gateway?token=pk_live_...

    200 · max-age=86400

    One request, cached for a day

    The banner arrives as a single file from the edge, so there is no round trip to an origin server before it can appear. The client tag ids are already inside it, baked in when the config was saved. In our database those ids sit encrypted with AES-256-GCM and are decrypted in memory only, while the file is built.

  2. 02

    (no third-party requests)

    waiting

    Nothing to block, because nothing has loaded

    Until the visitor accepts, the vendor tag is not on the page at all. There is no request to cancel and no cookie to clean up afterwards. Everything in the panel at this point belongs to the site itself.

  3. 03

    #csfy-root :: #shadow-root (open)

    mounted

    The banner mounts in its own root

    It renders inside an open shadow root. It inherits nothing from the site CSS and puts nothing into the global scope, which is what lets one setup survive thirty different themes without a single override per site.

  4. 04

    POST /api/gateway/save

    200 · on accept

    Accepting is the moment anything happens

    The allowed tags are injected, and the decision is written down: which categories were accepted, which were rejected, the policy version, and a hash of the IP. The raw address is never stored, so there is nothing sensitive to leak later.

  5. 05

    csfy_consent

    localStorage + cookie, 1 year

    The record belongs to the visitor too

    The choice is kept locally for a year, and the response carries a delete token. That token is what /api/gateway/delete needs, so a data subject request is answered by the visitor pressing a button rather than by someone querying a database.

Why agencies choose it

Made for people who run other people's sites


One login for every client

All sites, banners and consent logs in one dashboard. Your team gets 3 seats, and one more for every 10 sites.

One shared pool of pageviews

Every site adds 30,000 pageviews a month to the account. A client with a busy month draws on the ones having a quiet one.

No lock-in

Pay monthly, with no contract. If you leave, your consent logs and tag IDs come with you, and we help with the move.


Data stays in Europe

Consent records are stored in Europe, and IP addresses are hashed before they are saved.

A DPA ready to sign

The data processing agreement and the list of sub-processors are public, so your clients can read them before you start.

Tested every day

Every integration runs through our own cookie lab daily, so the cookie lists on your clients' sites stay correct.

Read the data processing agreement

Try it on 3 client sites first

Free for 30 days, no card needed. You only pay if you decide to keep going.