Guide
GA4 in JTL-Shop: revenue and cookie consent
JTL-Shop 5 has no ready-made connection to Google Analytics 4. A Google code snippet in the template only measures page views, not purchases, and often runs without cookie consent. The Shoplotse Google plugin reports product views, cart, checkout and purchase with revenue to Google, but only after consent in the JTL consent manager.
Why the Google code in the template is not enough
- Google only sees which pages are viewed. Purchases, revenue, cart and purchased products don't arrive, because only the shop itself knows the cart and the order.
- The code usually runs without consent in the cookie banner. That is not allowed under the GDPR.
- After a template switch or template update, the code is often simply gone.
- A code snippet in the template doesn't provide shipping costs, delivery time and returns for Google Search at all.
What Shoplotse Google gives you
- Clarity instead of gut feeling: You see where buyers come from (Google, Instagram, newsletter), which products are viewed often but rarely bought, and where visitors leave.
- Ads that pay off: With Google Ads you see which ad brings real revenue. Google can then optimise for buyers itself instead of just for clicks.
- Better results in Google Search: Brand, shipping costs per country, delivery time and returns appear as product data on the product page. Google uses them for merchant listings in search results.
- Opportunities: The plugin shows search terms for which your shop is shown often but ranks in positions 4 to 20 and is rarely clicked. A better page title often brings more visitors there quickly.
- Legally sound: Measurement only starts after consent in the cookie banner (Consent Mode v2). Customer names, email addresses and postal addresses never go to Google.
- No technical knowledge needed: The “Einrichtung” (setup) tab checks every step and tells you where to click. It also warns you if another plugin is already measuring and purchases would be counted twice.
All features
- Google Analytics 4: categories, search, product view, cart (add and remove), checkout, shipping and payment method and purchase with revenue, shipping and order number. Every order counts exactly once, even when payment happens before the order is completed.
- Server-side purchase: Optionally, the shop server reports the purchase to Google itself (Measurement Protocol). That way it isn't lost when a blocker intercepts the report in the browser or the customer doesn't come back after paying. All you need is an API secret from Analytics, with no tagging server of your own and no extra service.
- Google Ads: purchase conversion with order value, Enhanced Conversions (email, phone and address only SHA-256 encrypted) and dynamic remarketing with the product number.
- Google Tag Manager: You connect Meta, TikTok or Pinterest pixels including purchase tracking yourself in Tag Manager, without a developer and without changing the shop. All events are in the dataLayer in GA4 format, and the container only loads after consent.
- Product data: brand, GTIN (EAN), manufacturer part number, stars from your reviews, shipping costs per country, delivery time and returns. Anything your template already outputs is not added twice.
- Reports in the backend: visitors, revenue, channels, products, landing pages, search terms and “opportunities” from Analytics and Search Console, 28 days compared.
- Shopping check: checks your existing Google Shopping export format for typical errors.
Strengths and limits
- Strength: Measurement, Google Ads, product data and reports in one plugin. With other providers that takes two to three plugins, together €300 to €450 in the first year.
- Strength: Google numbers and “opportunities” right in the JTL backend, and a setup wizard at no extra cost.
- Strength: No changes to template files, tested with JTL-Shop 5.8.1 on PHP 8.3 and 8.4.
- Limit: Does not create conversion actions in Google Ads itself and does not upload offline purchases.
- Limit: No Google Shopping feed of its own and no sync with Merchant Center.
- Limit: Product data only with NOVA or a NOVA child template, backend only in German.
How setup works
- Upload the plugin in JTL-Shop under plugin manager and install it.
- In the “Einrichtung” (setup) tab, enter the licence key from your purchase email (starts with SL-).
- Enter the GA4 measurement ID (starts with G-). Optional: Google Ads conversion ID (AW-), Tag Manager container (GTM-) and the API secret for the server-side purchase.
- Enter shipping costs per country, delivery time and return period, and the plugin adds the product data.
- Optional: connect Search Console via verification tag and, for the “Berichte” (reports) tab, create a Google access with read-only rights.
- The “Einrichtung” (setup) tab shows green, yellow or red and explains every open item.
Questions and answers
What's the difference if I add Google Analytics directly to the website?
Either way, the numbers end up in Google Analytics. But a code snippet in the template only reports page views. Purchases, revenue and cart only arrive if the shop reports every step, and only a plugin can do that. On top of that there's cookie consent, which a code snippet in the template usually ignores.
Do I need the “Berichte” (reports) tab?
No, it's a convenience. It shows visitors, revenue, channels and search terms from Analytics and Search Console in the shop backend, so you don't have to look them up at Google. The real value is that the data reaches Google correctly and completely.
Does it work with my template?
Measurement works with any template. The product data for Google Search needs NOVA or a NOVA child template. Template files are not modified.
Does the plugin create a Google Shopping feed?
No. It checks your existing export format for typical errors, such as placeholders for condition and product category or a missing brand.
What about ad blockers?
Ad blockers often prevent measurement in the browser. With the optional server-side purchase, the shop reports the purchase to Google itself; all you need is an API secret from Analytics. This only applies if the customer consented in the cookie banner and Google has already recognised the visit. If an ad blocker blocks Google completely, the server can't assign the purchase to a visit either.
Do I need the AI Bridge or Claude for this?
No. Shoplotse Google is a standalone plugin and runs without AI. But both plugins can be used together in the same shop.
How does the licence work?
After purchase, the download link and licence key arrive by email. One key is valid for one shop, test copies such as localhost included. The AI Bridge key does not work for Shoplotse Google; each plugin has its own.
What does Shoplotse Google cost?
€49 one-time incl. VAT at launch, later €79. No subscription. How setup works is described in the docs at shoplotse.net/docs-google.html.
More guides
Last updated: 19 Oct 2026