Show your cookie banner on HubSpot, Webflow or Shopify pages
One line of code shows the same Omea Consent banner on pages HubSpot, Webflow, Framer, Unbounce or Shopify serve under your domain.
Many sites are more than WordPress: a HubSpot blog at /blog/, landing pages from Unbounce, a shop on Shopify. Those pages don’t run WordPress plugins – so they don’t get your cookie banner. With Omea Consent Pro, one line fixes that.
Add the banner
- Find the pages Run a cloud scan under Omea Consent › Scanner. Pages served by another system appear under Pages without the banner.
- Copy the line In that section, under Show the banner on these pages, click Copy.
- Paste it into the other platform’s head Paste the line into the
<head>of those pages, as high as you can – before any analytics or marketing code. - Scan again Run the cloud scan again. The pages should no longer be listed.
The line looks like this, with your own domain:
<script src="https://www.example.com/wp-json/omea-consent/v1/embed.js"></script>
On a multilingual site with Polylang, the line includes ?lang= with your default language.
Where to paste it
| Platform | Where |
|---|---|
| HubSpot | Settings › Content › Pages › choose the domain › Templates › Site header HTML – covers landing pages and the blog on that domain |
| Webflow | Site settings › Custom code › Head code, then publish |
| Framer | Site settings › General › Custom code › Start of <head> tag, then publish |
| Unbounce | Open the page › Javascripts › Add new, placement Head |
| Shopify | Online Store › Themes › Edit code › theme.liquid, right after <head> |
| Others | Look for Head code, Header HTML or Custom code in <head> in the page or site settings |
What the line loads
The same banner, texts and colours as your WordPress site, plus:
- the Google Consent Mode v2 defaults and updates,
- the Microsoft UET and Clarity and HubSpot consent signals,
- the consent log – choices made on those pages are recorded on your WordPress site.
Because the consent cookie and storage are shared, one choice covers both the WordPress pages and the others.
Where it runs
The script runs only on your own host (with or without www), so nobody can copy it to another site. To use it on subdomains too – for example shop.example.com – turn on One choice across subdomains. It does nothing on your WordPress pages, which already have the banner.
The script is cached for five minutes, so changes to your banner reach the other pages quickly.