Jimdo

Use the site-wide head code and switch off Jimdo's own tracking integrations.

Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.

Where the snippet goes

Jimdo lets you add code to the head of the whole website and, separately, to single pages. Use the site-wide head code setting; a page-level field only covers that page, so other pages load trackers without consent defaults. Head code may depend on your Jimdo plan; check Jimdo's help for the current menu location.

Install

  1. Copy the complete snippet for the correct ConsentEase website from Installation.
  2. Paste it as the first code in Jimdo's site-wide head code, above Google Tag Manager or any other tracking code.
  3. Do not add it through a GTM Custom HTML tag, and do not paste only the script line: the first block must set the defaults before Tag Manager starts.
  4. Save, open the published site and run the installation check.

Jimdo's built-in tracking integrations

Jimdo's built-in Facebook Pixel integration asks Jimdo's own cookie banner for permission. When that banner is switched off because ConsentEase replaces it, the pixel is treated as allowed and fires before any choice. ConsentEase cannot hold back a pixel that Jimdo starts itself. Remove the pixel from Jimdo's integrations and add it through Google Tag Manager with ad_storage consent required. Check other built-in Jimdo tracking integrations the same way. The installation check names Jimdo's built-in pixel when it sees this pattern.

Check more than the homepage

Open a few other pages, such as a contact page, and confirm the snippet sits at the top of the head there too. Conversion tags often fire on those pages.

Verify the published site

Use separate fresh browser contexts for no choice, accept, reject and custom preferences. Check tag consent requirements, network traffic, storage and reopening preferences. Test relevant routes and mobile layouts. A theme installation does not prove coverage of checkout, embedded frames or hosted third-party pages.

Related articles

Still need help?

Contact the ConsentEase team and include the website and steps you tried.