Add a cookie consent banner to a Laravel app

Cookbook · platform · Last verified 12 November 2026 · View raw markdown (for agents)

In short: paste the live snippet directly after the opening <head> of the Blade layout every page uses (in a fresh app that is resources/views/welcome.blade.php; in yours, the shared layout file), above the other lines in <head> (@fonts, @vite).

Confirmed on a Laravel app: the snippet is the first script in the rendered page's <head>.

You need #

• A Cookie Compliance AppID and the live snippet from MCP install.getSnippet or dashboard Integrations → Manual Integration (a new app uses /v2/hu-banner.min.js; an existing app keeps the URL in that snippet). A domain added in the dashboard is published automatically; if the status check still says the app is not published yet, or after later edits, click Publish Now, then copy the snippet. A snippet copied before publishing must be copied again. No account yet? Sign up (free plan, no card); with MCP, call help.startSignup.
• Edit access to the Blade layout that renders <head> (the file with @yield/{{ $slot }}, shared by your pages).

Where it goes #

1. Copy the live snippet (see above).

2. Open the Blade file that renders <head> for your pages (your shared layout; in a fresh app the starter page resources/views/welcome.blade.php).

3. Paste the snippet directly after <head>, before the <meta> tags, @fonts, @vite and your analytics:

   <head>
       <!-- Cookie Compliance: first script on the page (paste live snippet here) -->
       <script>
           var huOptions = { "appID": "YOUR_APP_ID", "currentLanguage": "en", "blocking": true, "globalCookie": false };
       </script>
       <script src="https://cdn.hu-manity.co/v2/hu-banner.min.js" type="text/javascript" charset="utf-8"></script>
   
       <meta charset="utf-8">
       @fonts
       @vite(['resources/css/app.css', 'resources/js/app.js'])
       <script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXX"></script>
   </head>
   

4. Your trackers stay as they are. Keep the banner as plain tags in the layout, outside @vite and your JavaScript bundle.

If the snippet is currently at the end of <head> or before </body>, move it up to directly after <head>.

What the order controls #

The banner holds recognised trackers that load after it until the visitor chooses, in regions whose rule requires consent first. A script placed above the snippet runs straight away, and a script you mark data-hu-category="1" is treated as essential. What runs before consent is your decision, so keep analytics and pixels below the snippet.

Confirm the result #

Build or render the site, then view the page source of the output (not the browser's Elements panel): the huOptions script and hu-banner.min.js are the first two <script> tags in <head> of the rendered page, with no async or defer, and your analytics tag comes after them.

Then run the browser checks in plain-html in a private window (banner shows, no tracking cookies before the visitor chooses in a region whose rule requires consent first, trackers start after Allow) and, for the full procedure, verify-install. Test from a region your strictest rule covers (for example the EU), or confirm region rules are off.

Gotchas #

• More than one layout. If some pages extend a different layout, add the snippet to each layout's <head> the same way.
• Keep a single consent banner. Remove any other one, so visitors see one clear choice.
• Use your own AppID, and copy the snippet again after switching banner engine in the dashboard: changing the setting alone does not update a pasted snippet.

More help #

• Where to put the Cookie Compliance snippet — the placement rule, for the site owner.
• Banner not displayed — what to check when the banner does not show.