See what runs on your site. The scan crawls your domain's public pages, before and after consent, and builds the inventory.
Cookie consent you can prove, not assume.
Soyio Cookies detects the cookies your site uses, publishes a banner with your branding, and holds optional scripts until the visitor decides. Every decision is recorded against the exact version they saw.
Organizations that work with Soyio:
The problem
Do you know which cookies your site uses, and when they turn on?
Your site shows the cookie notice as soon as someone arrives. But before the visitor gets to read it, analytics and advertising scripts may already be running. You're asking permission for something you've already done.
- 01Scripts run before the answerIf the site isn't prepared, analytics and advertising turn on while the notice is still open.
- 02The notice asks, but the answer changes nothingThe visitor rejects and the scripts keep running, because nobody connected them to that decision.
- 03Nobody has the full list of cookiesThe inventory froze the day the notice was installed. The site kept adding tools.
- 04The decision can't be provenIf the preference only lives in the visitor's browser, there's no way to show what they accepted, when, or on which notice.
tienda.example.com
NetworkBefore the decision
A cookie notice only makes sense if the site does what the visitor chose.
What cookie consent is and which categories exist
Cookies are small files a site stores in the visitor's browser. Many are created by third-party scripts, such as analytics or advertising tools. Cookie consent is the visitor's decision about which ones turn on, made by category rather than with a blanket yes or no.
Essential
The ones the site needs to work. Always active.
Functional
Remember the visitor's choices.
Analytics
Measure how the site is used.
Marketing
Used for advertising and campaigns.
Personalization
Tailor the experience to each visitor.
Banner design changes the decision
A dark pattern is an interface trick that pushes people to decide against their own interest: hiding the reject button, pre-ticking boxes, or painting “accept” in color and “reject” in gray. They raise acceptance, but not the acceptance the person chose.
An experiment in France with about 4,000 participants compared different banner designs. Asked directly, about 31% said they would rather reject cookies.
Half of participants admitted they accepted out of habit.
| No reject option | 4% |
|---|---|
| Neutral banner | 17% |
| Reject as visible as accept | 34% |
| Preferred to reject when asked directly | 31% |
Source: Bielova et al. (2024), “The Effect of Design Patterns on (Present and Future) Cookie Consent Decisions”, USENIX Security.
A “yes” out of habit isn't a preference. It's fatigue.
Your site asks permission before using cookies, and can prove it.
The banner is the first thing your organization tells each visitor about how it handles their data. Soyio Cookies lives inside Consent. It brings together the site's inventory, the banner, script blocking, and the record of every decision alongside the rest of your organization's authorizations.
An inventory your team reviews. Each cookie arrives with a suggested category and provider. Your team confirms, edits, or adds before publishing.
Nothing runs without permission. Optional scripts wait for the visitor's decision and only turn on for the categories they accepted.
Accept and reject, on equal footing. Accept all, reject, and customize appear with the same visual weight.
Every decision, provable. Each decision is tied to the exact banner version that person saw, with an integrity hash.
Where they accept and where they don't. Each site's summary shows acceptance by category, so you can review the banner before the next publication.
How Soyio Cookies works
In four steps: what runs on your site, how the banner looks, what waits for the decision, and what gets recorded.
Soyio checks your site and shows you everything that runs
Enter your domain and Soyio detects every cookie, with a suggested category, provider and duration. Your team reviews and decides.
Read the docs (in Spanish)dashboard.soyio.id
Main storeActivetienda.example.com
DetectionAppearanceContentInstallation
Cookie detection
RescanScanning pages · 12 of 20Scan complete · 6 cookies detected
| Cookie | Category | Provider | Duration |
|---|---|---|---|
| session_id | Essential | First party | Session |
| sy_consent | Essential | Soyio | 1 year |
| chat_session | Functional | First party | 24 hours |
| _ga | Analytics | 2 years | |
| _gid | Analytics | 24 hours | |
| _fbp | Marketing | Meta | 90 days |
Category suggested by the scannerCategory confirmed by the teamConfirm suggestions
You fit the banner to your brand and publish it
Choose a format, match colors and text to your brand, and publish. Each publication is saved as a version.
Read the docs (in Spanish)The banner is published in Spanish and English.
tienda.example.com
Your scripts wait for the visitor to decide
Optional scripts don't run until the visitor decides, and only accepted categories are activated. Install it with a script tag or Google Tag Manager.
Read the docs (in Spanish)tienda.example.com
Visitor's decision
- Analytics
- Marketing
<script type="text/plain"
data-soyio-category="analytics"
data-src="https://www.googletagmanager.com/gtag/js"></script>On holdRunning<script type="text/plain"
data-soyio-category="marketing"
data-src="https://connect.facebook.net/signals/fbevents.js"></script>On holdRunningGoogle Consent Mode signals
- analytics_storagedeniedgranted
- ad_storagedeniedgranted
- ad_user_datadeniedgranted
- ad_personalizationdeniedgranted
Every decision is recorded, and you see how visitors respond
Each decision stores the date, the banner version and the chosen categories, with an integrity hash. The summary shows how visitors respond on each site.
Read the docs (in Spanish)dashboard.soyio.id
Cookie transactions
tienda.example.com
| ID | Decision | Categories | Date |
|---|---|---|---|
| ccact_7Jd4Rw | Accepted all | Jul 21, 02:41 PM | |
| ccact_2Lm8Pq | Rejected all | Jul 21, 02:38 PM | |
| ccact_9Xk2Qm | Customized | Jul 21, 02:32 PM | |
| ccact_5Tn1Vz | Accepted all | Jul 21, 02:27 PM |
Cookie transaction
Customizedccact_9Xk2Qm
- Captured
- Jul 21, 2026, 02:32 PM
- Expires
- Jul 21, 2027, 02:32 PM
- Accepted
- Essential and Analytics
- Rejected
- Functional and Marketing
- Origin
- tienda.example.com/checkout
- Published version
- v4
Receipt proof
Integrity hash
9f3ac21e7b04d5e8a1c6f2093b7e4d18c5a0f6e2b9d34c71a8e5f0c2d6b39a47
Previous record
4c1ea2b97d30e5f8…
Masked dataIP 190.•••.•••.3Browser [hidden]
From a notice that asks to a site that respects the answer.
| Area | Cookie notice on its own | With Soyio Cookies |
|---|---|---|
| Which cookies exist | Whatever was noted when the notice was installed | An inventory from a scan you can schedule |
| Before the decision | Depends on how each script was loaded | Optional scripts on hold and Google signals denied |
| If the visitor rejects | Scripts may keep running | No optional script tied to a category turns on |
| When the notice changes | The previous decision stays stored | A new version is published and the visitor is asked again |
| What was recorded | The preference in the visitor's browser | The decision, the version they saw, and an integrity hash |
More articles to read
Frequently asked questions
Transparency is part of treating data fairly. These are the most common questions. If you have others, contact us.
It's the visitor's decision about which cookies turn on in a site, made by category: essential, functional, analytics, marketing, and personalization. For it to mean anything, the site has to wait for that decision before turning on optional scripts.
It's the part of Consent dedicated to a website's cookies. It shows the banner, records each visitor's decision, and keeps optional scripts from running before there's permission. Those decisions sit alongside the rest of the authorizations your organization manages.
Each optional script is tied to its category, with a Soyio tag in the code or with consent checks in Google Tag Manager. A script that isn't tagged runs anyway. That's why installation includes reviewing how each one loads.
Because Consent Mode is a signaling layer, not a block. A tag that runs with denied signals can still send cookieless pings. Soyio Cookies manages the signals and also keeps optional scripts on hold.
If they reject everything, only essential cookies stay active. They can reopen their preferences from the site's persistent control or from a footer link. If they withdraw a permission, the page reloads without those scripts.
Each publication creates a new version. Visitors who decided on an earlier version see the banner again.
Yes, more people reject. In Bielova et al. (2024), people who decided with a banner like that were more satisfied with their decision and saw it as fairer. That's the acceptance that holds up over time.
Soyio Cookies uses Google Consent Mode v2 in Basic mode. If the visitor rejects analytics, Google's tools don't load or send data from that visit. Your metrics reflect the people who accepted, and the summary shows how many they are and in which categories.
With a single script the problem is the same: if it loads before the decision, the notice arrives too late. And the scan shows whether it really is just one.
A transaction with the date, the site, the published banner version, the accepted and rejected categories, the origin, the page, and an integrity hash that lets you check the record wasn't altered.
No. Knowing which cookies exist doesn't require reading what they contain, so the scanner doesn't read or store it.
START TODAY
Make your site ask permission before using cookies, and be able to prove it.
Let's talk about what runs on your site today. If the banner isn't live yet, even better: getting it right the first time costs much less.
Contact usSubscribe to our newsletter
Privacy is making headlines
A weekly roundup of privacy, regulation, and technology news that could affect your business.
Subscribe (LinkedIn, opens in a new tab)