Set up Cookie Crumb
Cookie Crumb is the free plugin WorkMore Cookie Crumb: a consent banner that holds scripts, videos and pixels back until your visitors answer, a cookie scan, a consent log and a dashboard — all on your own site, complete on its own. WorkMore Cookie Crumb Pro, an add-on to it, keeps consent records in a database of your own and adds more ways to shape the banner; its steps are at the end of this page.
The plugin is a tool, not legal advice: which cookies need consent, how to ask and how long to keep a record depend on the law that applies to your site.
What you need
- WordPress 6.5 or newer and PHP 7.4 or newer.
- An administrator of the site. On a multisite network each site has its own banner, cookie list and consent log.
- The free plugin, from Plugins → Add New or its WordPress.org page. A site that installed it from this store before it was listed updates from WordPress.org on its own — it is the same plugin, under the same name.
1. Install the free plugin
- Plugins → Add New, search for WorkMore Cookie Crumb, Install Now, Activate.
- Open Settings → Cookie Crumb. A site that was never set up opens on Set up your cookie banner: four steps, and everything in them can be changed afterwards. Skip the setup takes you straight to the tabs.
Nothing changes for your visitors until you publish.
The plugin's screen has two looks, chosen under Settings → Interface: Standard, which a site starts with, and Classic, in the plain WordPress style. Your visitors get the same either way.
2. The four steps
- Look at the site. Press Scan the site. The screen opens a few of your pages in your own browser, the way a visitor who is not logged in gets them, and lists the cookies they set and what they load from other sites. It takes under a minute. While it runs, your pages' own trackers run once in your browser. Nothing is sent to an outside service.
- Sort what was found. Each cookie and script goes into a category or is left out. What the plugin recognises — Google Analytics, Tag Manager, Google Ads, YouTube, Google Maps, Meta Pixel, Facebook embeds, and the cookies of WordPress and WooCommerce — has its category already; choose one for the rest. A script in any category but the necessary one will be held back until a visitor allows that category.
- The banner. Choose how it asks — Ask first (recommended) holds scripts back until the answer; Notice only informs and holds nothing — and how it looks. Its words, its languages and the link to your policy are under Banner design afterwards.
- Publish. Publishing puts the banner on every page and holds the listed scripts back. The page caches of common caching plugins and hosts are cleared; if your host caches pages some other way, clear that cache after publishing.
3. Check what still loads before the answer
Open Cookie scan and press Scan again. Now that a banner is published, the scan also opens each page as a visitor who has not answered, and lists under Loaded before the visitor answered whatever still reached another site — with, for each, whether a rule can hold it:
- A script or an embedded frame can always be held: give it a category, add it and publish again.
- What a script that already runs sends by itself, and style sheets and fonts from another site, cannot be held by a rule: hold back the script that does it, or serve the file from your own site.
A scan cannot see what loads only after a click or a purchase, or what an ad blocker in your browser stops.
4. Let visitors change their answer
By default a small round button stays in a corner of every page and opens
the cookie settings window. Under Banner settings you can use your own
link instead, or as well: any link to #cookie-settings opens the window —
in a menu, a footer or a page — and so does the [wmcc_settings]
shortcode. The window shows the visitor their consent ID.
5. Read the consent log
Consent log shows how visitors answered — by kind, by category, over time — and page views, for the Time range you choose at the top of the tab: the last 24 hours, 7 or 28 days, 3 or 6 months, or two dates of your own. Point at a chart to read its numbers. Below, every answer is one record: paste a visitor's consent ID to find theirs, and Export CSV takes the list with you. The log keeps the last 90 days, and Storage says how much room the records take in your database. Settings → Privacy → Policy guide in WordPress has a paragraph about it that you can use in your privacy policy.
WordPress' own Dashboard has a widget, Cookie Crumb: consent, with the consent rate and the answers by kind over the last 28 days; Screen Options hides it.
Changing the banner later
Everything is a draft until you publish it. Change the cookie list under Cookies, the words and the look under Banner design — beside a live preview of your real site at desktop, tablet and phone widths — then press Publish banner. Each publish is a version, and every record names the version the visitor answered. Visitors are asked again only when a category that needs consent was added.
If something goes wrong
- Take the banner down, in the bar above the tabs: the banner is off and nothing is held back, at once. Your draft, cookie list and log stay.
- Deactivating the plugin does the same. Nothing in your content was changed, so there is nothing to undo.
- A page still shows the old banner: clear your page cache or CDN.
- The Consent log tab warns when visitors' answers are not reaching the
site — usually a security plugin or a firewall that closes the REST API to
visitors. Allow requests to
/wp-json/workmore-cookie-crumb/v1/.
Pro
- Buy a plan on the pricing page. Freemius, our merchant of record, emails your license key and a link to the add-on.
- Download the add-on from that email (the zip's name starts with
workmore-cookie-crumb-pro). Plugins → Add New → Upload Plugin, choose the zip, Install Now, Activate. The free plugin must stay installed and active: Pro is an add-on to it, and WordPress will not activate one without the other. - Paste the license key from your purchase email when the add-on asks. The same screen opens from Activate License under the add-on in the Plugins list, and from Settings → Cookie Crumb → Pro → Activate your license.
- Settings → Cookie Crumb now has a Health check tab and a Consent Offload tab, Banner design has more positions and sections of its own — a logo, a color for each part, button styles, rounded corners, your own CSS — and Add a service you use under Cookies lists more services. The Pro tab shows your license.
Send consent records to a database of your own
Open Consent Offload and choose where records go: a MySQL or MariaDB server, a PostgreSQL server, Supabase or a PostgREST, or a webhook of your own. Test the connection, then Make the table — or run the SQL the tab shows at the destination yourself — tick Send records to this destination and Save the connection. From then on a background task sends new records every five minutes; Send the records already in the log sends the earlier ones. While the destination is down the records wait in your site's log and are sent when it is back; a record sent twice is stored once.
Keep the password or key out of the database if you can: add
define( 'WMCC_PRO_OFFLOAD_SECRET', '…' ); to wp-config.php and leave
the field empty. Use a database user that may add to and read that one
table, and nothing else.
Updates and sites
- The add-on updates from Plugins → Updates while your subscription is active.
- If the subscription lapses, nothing breaks: your banner design stays, and consent records keep going to your database. What you set up stays editable. Updates, a new connection and sending earlier records wait until you renew — the Pro tab has the button.
- A license covers the number of sites of its plan, and local and staging copies of a site do not count. To move a license, deactivate it on the old site (Pro → Manage account) and activate it on the new one.
- Remove the add-on whenever you like: the free plugin's banner takes over at once, and its cookie list and consent log are untouched. Your design and your connection stay stored — unless you ticked the uninstall switch under Settings — and come back when you reinstall Pro. Records made meanwhile wait in the log, which keeps 90 days.
Uninstall
Deactivating never deletes anything. Uninstalling removes the consent log, the statistics and the settings only if you ticked Settings → Delete the consent log, statistics and settings when the plugin is uninstalled; it is off by default, because a consent log is a record you may be asked for. Export it first.