Add Velo
to PrestaShop.
Install the Velo cookie banner and Google Consent Mode v2 on PrestaShop with one line in your theme's head template. Most installs take a few minutes when you already have admin access to the site. If you run Google Tag Manager, that route is on this page too.
Instructions and image sources reviewed 3 November 2026.
Paste one line
into head.tpl.
Add your site’s snippet to the site-wide head, then publish and test the result. If your measurement tags already run through Google Tag Manager, use the route below.
Already running Google Tag Manager? Take that route instead ↓
Three steps · about five minutes
-
01
Copy the line
Copy the complete installation snippet for this site from your Velo dashboard. The example below shows the format; replace your-site-id before using it. Keep the API endpoint supplied by your dashboard.
<script src="https://cdn.veloconsent.com/v1/velo.js" data-api="https://app.veloconsent.com" data-velo-site="your-site-id" async></script> -
02
Edit your theme’s head template
In a child theme of your active theme, copy templates/_partials/head.tpl from the parent theme and paste your complete Velo snippet just after the head_charset block, above the hook_header block where modules add their tags. Save, then clear the cache under Advanced Parameters → Performance. Editing the parent theme works too, but a theme update overwrites it.
PrestaShop · theme head template
{* In your child theme: templates/_partials/head.tpl, copied from the parent theme *} {block name='head_charset'} <meta charset="utf-8"> {/block} {* Paste the complete Velo snippet from your dashboard here. *} {* …the rest of the parent's head.tpl, unchanged… *} {block name='hook_header'} {$HOOK_HEADER nofilter} {/block}Verified configuration reference · 3 November 2026 Configuration reference checked against the platform documentation. This is not an admin screenshot.
Platform documentation ↗ -
03
Publish and check the live site
Save and publish the change using the platform steps above, then clear any site or CDN cache. Open the published URL in a fresh browser session. Check the banner where your region rules require it, test accepting and rejecting, and verify consent defaults and updates before your measurement tags run. Confirm the site appears as installed in your Velo dashboard.
Live interface capture · 23 September 2026 The real banner on veloconsent.com, captured on 23 September 2026. Your banner’s copy, layout and region settings may differ.
Velo live site ↗View full size ↗
If the banner does not render after the edit, it is almost always the cache: clear it under Advanced Parameters → Performance, then hard reload. Then check that the child theme is the active one and that the snippet sits above the hook_header block, where modules add their own tags.
Still comparing options? See every supported platform.
Or add the tag
in Tag Manager.
Already have a Google Tag Manager web container on this site? Add Velo from the Community Template Gallery and configure it there. If you need to install the container first, use your platform’s supported integration and check it on the published URL.
- 01Add the Velo CMP templateTemplates→Tag Templates→New→Search Gallery
- 02Create the tagTags→New→Velo CMP template
- 03Review the advanced optionsAdvanced→url_passthrough→ads_data_redaction
- 04Fire it on Consent Initialization – All PagesTriggering→Consent Initialization – All Pages
- 05Enable the consent overviewAdmin→Container Settings→Enable consent overview
- 06Preview, then publishPreview→Submit→Publish
Velo CMP · tag configuration
- Velo site ID
- Copy the exact site ID from your Velo dashboard.
- Banner theme
- Light or Dark
- Velo API endpoint (optional)
- Use the API endpoint shown in your Velo installation settings.
Field names checked against the published Velo CMP template. Use your own site ID and API endpoint.
Velo CMP template ↗PrestaShop questions,
answered.
What teams installing on PrestaShop ask first.
Which PrestaShop version does this cover?
The steps fit PrestaShop 1.7, 8 and 9 with the Classic theme, Hummingbird or a theme built on either, which keep the page head in templates/_partials/head.tpl. PrestaShop 1.6 themes keep it in a different template, so the Tag Manager route is the simpler path there.
My shop already shows a cookie banner from a module.
Disable that module under Modules → Module Manager so Velo is the only consent layer running. Two banners confuse visitors, and only Velo wires the decision into Consent Mode and the audit log.
Why is the banner not showing after the edit?
Almost always the cache: clear it under Advanced Parameters → Performance, then hard reload. If it still does not render, check that the child theme is the active theme and that its head.tpl sits at templates/_partials/head.tpl, the same path as in the parent theme.
Will it slow the site down?
The dashboard snippet loads asynchronously. As with any script, measure its effect on your site and check your tag order; asynchronous loading alone does not guarantee consent defaults run before other tags.
Can an AI assistant do this for me?
Yes. Copy the prompt in Install with agents, just below, into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries the steps on this page, the order the tags have to load in, and the checks the agent has to run before it tells you the job is done.
Or hand it
to an agent.
Copy the prompt into Claude, ChatGPT, Cursor or whichever assistant you already use. It carries everything on this page: both routes, the order the tags have to load in, and the checks that prove it worked.
Paste this prompt into your assistant, then provide your site ID and the complete installation snippet or GTM settings from your Velo dashboard.
Working with an agent that reads the web? Point it at veloconsent.com/llms.txt and /install.md for the same context in plain text.
