PulseConsent
Ask properly. Block honestly. Visitors in Europe and Quebec are meant to be asked before your site runs anything beyond the essentials. This is the banner that asks, in your brand, and the blocking that holds until they say yes.
Start from what is really there. The scanner does the remembering.
Before the banner can be honest, the inventory has to be. The scanner inspects your site, finds the cookies and iframes actually present, and resolves them to named vendors, including the ones nobody remembers adding.
- Four categories: necessary is always on, the rest are asked
- Your colours, your words, your button labels
- Top, bottom or centre: your call
- Show it everywhere, or only where GDPR-style rules apply
- Every config change kept: history, not overwrites
Then hold the line. Scripts wait for the yes.
Every outside script your site loads — an analytics tag, an advertising tracker, an embedded video, a chat widget — is listed with a category. A listed script stays off the page until the visitor says yes to that category. Ours included.
- Every outside script your site loads, listed with a category
- A listed script stays off the page until someone says yes to its category
- The scanner reads your site and names the vendors it finds
- Unresolved cookies get categorized by hand, in the open
- Change your mind on the banner: scripts re-gate immediately
Consent your visitors can believe. Because it is enforced, not implied.
Blocking, not theatre
A script in the catalogue does not run until a visitor says yes to its category. The banner is a gate, not a decoration over business as usual.
A catalogue built from evidence
The scanner inspects your actual site (cookies, iframes) and resolves them to known vendors, so the catalogue starts from what is really there.
Configs with a memory
Banner configurations are never overwritten: each change is kept, so what visitors were shown last March is still on the record.
Built with analytics, not beside it
Pulse’s own analytics script sits in the same catalogue under the same rules. Our measurement waits for consent like everyone else’s.
Ask like you mean it. The beta is open now.
If your website only runs the essentials, probably not. It is the extras that trigger it: analytics, an advertising tracker, an embedded video, a chat widget. Privacy rules in Europe and Quebec expect visitors to be asked before those run, and they tend to follow the visitor rather than the organization, which is why a Canadian charity with European readers can be caught by them. Whether they reach yours is a question for your counsel; what we can tell you is that this is the machinery for asking.
We claim the mechanics, not a certificate: per-category choices, real script blocking until consent, a scanner that finds what your site actually sets, and configuration history that is never overwritten. Whether your whole program complies is a question for your counsel; this gives them good answers.
Yes. A script listed in the catalogue cannot run until the visitor says yes to its category. Decline marketing, and the advertising trackers stay off the page: no Meta pixel, no ad tags, no tracking embeds. That includes our own analytics script.
Run the scanner. It inspects your site, finds the cookies and embedded frames, and resolves them to known vendors with a category. The stragglers you categorize by hand, visibly.
Colours, headline, body copy, button labels and position are all yours. One small Mercleo attribution line remains on the banner; we would rather tell you that here than have you notice it on launch day.
There is a switch for exactly that: show it everywhere, or only to visitors in GDPR-style regions. Many Canadian organizations choose everywhere, on the theory that respect travels well.