Cookie consent for Bagisto

Cookie consent for Bagisto, the Laravel-based shop — three Blade includes, a local runtime, Consent Mode v2 and pixel gating included. A component in your stack, not an embedded service.

or see all twelve platforms

Why Bagisto sites need consent that actually blocks

Bagisto is an open-source e-commerce platform built on Laravel, chosen by teams that want a modern PHP stack and full control over their shop rather than a hosted product. Its users are developers, or work closely with one.

Installing on Bagisto

Upload into public/

Copy the Cookie Craft folder into public/ inside your project.

Add three Blade includes

Into your theme’s storefront layout — the theme copy, not the package copy — with your paths already filled in.

Clear the view cache

Run php artisan view:clear. Realistic time: 5 to 15 minutes.

What’s specific to Bagisto

Edit your theme’s copy of the layout, not the package. Bagisto exposes the storefront layout in two places: resources/themes/default/…/index.blade.php, which is your theme copy, and a file under packages/Webkul/Shop/…, which belongs to the package. Editing the theme copy means your change survives a Bagisto update; editing the package copy means it does not.

Second, Bagisto has a separate admin layout — the banner belongs on the storefront only. Third, and this catches everyone on Laravel-family platforms: Blade compiles and caches views, so after editing you must run php artisan view:clear, or you keep looking at the compiled old template and conclude the includes did not work.

Included on Bagisto, not upsold

No feature is held back for a higher tier. One plan, everything in it.

Google Consent Mode v2

The four signals GA4 and Google Ads need to run properly in the EEA — analytics_storage, ad_storage, ad_user_data, ad_personalization — set from your visitor’s real choice.

GTM, Meta & TikTok

Google Tag Manager, Meta Pixel and TikTok Pixel get base placement and consent-aware loading — no snippets pasted into your Bagisto templates, no second plugin to gate them. Your tracking plan still defines the events and conversions.

One licence, one root domain

Bagisto is often part of a larger setup with a marketing site and staging environments — the single-root-domain licence covers the whole thing.

A guide for your exact site

Your install guide is generated with your real Bagisto paths already filled in, in twelve languages — no example.com placeholders to translate into your own setup.

Why it matters here

Bagisto teams are technical enough to have considered writing consent handling themselves — and technical enough to know how much work correct Consent Mode v2 signalling actually is. Cookie Craft is a component you drop into your own stack: PHP and JavaScript in your codebase, tables in your own database, no outbound calls on the visitor’s page.

What it does — and what it doesn’t

Cookie Craft does not scan your Bagisto site to discover cookies automatically, and it does not write your privacy policy for you. It gives you the mechanism: a banner your visitors actually interact with, real blocking of the scripts you configure, and correct Consent Mode v2 signals to Google. What you declare in it is up to you.

Consent for Bagisto, done properly.

Self-hosted, first-party, and everything included — €25/month or €240/year per root domain.