Does bipel.com use cookies?

bipel.com uses 2 cookies. The site uses Didomi as its consent management platform.

Does bipel.com use a cookie banner (CMP)?

Yes. bipel.com uses Didomi as its consent management platform. IAB TCF v2.3 consent signals were detected. Google Consent Mode v2 was not detected.

Which third-party trackers does bipel.com use?

bipel.com loads 5 third-party requests from 5 vendors, including cdn.by.wonderpush.com, Google LLC, measurements-api.wonderpush.com, Adobe Fonts, Didomi.

How many marketing and analytics cookies does bipel.com set?

bipel.com sets 0 marketing and 2 analytics cookies, alongside 0 strictly necessary cookies. Under GDPR and the ePrivacy Directive, non-essential cookies require prior consent.

bipel.com

Item: bipel.com
Rating: 68
Author: Passiro

https://bipel.com

Last scanned August 14, 2026

A cookie scan of bipel.com completed on August 14, 2026 found 2 cookies and 5 third-party tracking requests. The assessment covered 10 pages across 10 unique page templates. The site relies on Didomi as its consent management platform with IAB TCF v2.3; Google Consent Mode v2 was not observed. 5 third-party requests were detected from 5 vendors.

Claim & unlock

Third-party

Trackers

Vendors

Consent banner

Didomi

Scans

What this setup is missing

Google tags were observed, but Google Consent Mode v2 was not detected.
No Reject option on the first layer; declining requires extra steps.

Compliance by audience

European Union

✗ Not met

GDPR + ePrivacy · Prior consent (opt-in)

United Kingdom

✗ Not met

UK GDPR + PECR · Consent-based

United States

✓ Meets this model

CCPA/CPRA + state laws · Notice & opt-out

Canada

! Needs attention

PIPEDA + Québec Law 25 · Consent-based

Brazil

! Needs attention

LGPD · Consent-based

Scanned from the EU; sites may serve different banners or tracking to other regions. Verdicts reflect observed behaviour measured against each audience's rules.

Connection security

HTTPS supported

✓

Redirects HTTP to HTTPS

✓

HSTS

✓

Content Security Policy

✗

Cookies

2 cookies detected: 0 necessary, 2 analytics, 0 marketing

Total

Necessary

Functional

Analytics

Marketing

Unknown

Filter by category

Name	Domain	Category	Provider	Expiry	Secure	HttpOnly	Party
_pk_id.224.cc53 before consent	www.bipel.com	Analytics	Matomo	1.1 yr	–	–	1st
_pk_ses.224.cc53 before consent	www.bipel.com	Analytics	Matomo	Expired	–	–	1st

Browser storage set by the site

Name	Domain	Party
_wpinitialpermissionstate set by cdn.by.wonderpush.com/wonderpush-loader.min.js:1:303	https://www.bipel.com	1st	before consent
didomi_dcs set by sdk.privacy-center.org/sdk.0d3605ade78dc410aaa46a5c215a6d7cda4831f7.js:2:75949	https://www.bipel.com	1st	before consent
__wpfvdk set by cdn.by.wonderpush.com/wonderpush-loader.min.js:1:1078	https://www.bipel.com	1st	before consent

Third-Party Trackers

5 requests detected from 5 vendors: cdn.by.wonderpush.com, Google LLC, measurements-api.wonderpush.com, Adobe Fonts, Didomi

Analytics

Marketing

Necessary

Functional

Other

Vendor	Category	Type	Domain
cdn.by.wonderpush.com before consent	Analytics	script	cdn.by.wonderpush.com
Google LLC before consent Google Tag Manager	Analytics	script	www.googletagmanager.com
measurements-api.wonderpush.com before consent	Analytics	xhr	measurements-api.wonderpush.com
Adobe Fonts before consent Adobe Fonts (Typekit): web font delivery	Functional	script	use.typekit.net
Didomi Didomi tracker domain (source: Disconnect.me, category: ConsentManagers)	Unknown	script	sdk.privacy-center.org