Shopware integration
Shopware server-side tracking, from the first ad click to the paid order
The script goes in your storefront, the paid order reaches LeadJourney through Flow Builder, the Admin API or Zapier, and the revenue goes back to Meta, Google and Microsoft Ads.
- Live in 21 minutes
- Server-side, first-party
- Hosted in the EU, DPA signed
Rated by the teams who connected their stack
How the data moves
- Touchpoints and spend flowing in
- Conversions and revenue going back
- Organic search
- Organic social
- AI search
AI Attribution Engine
LeadJourneyServer-side tracking, every channel in one journey- Server-side tracking of every visit
- Multi-touch attribution per customer
- Paid orders sent back to the ad platforms
ShopwareWhere the orders are paid- Orders
- Customers
- Sales channels
The loop closes in the ad account. Every paid Shopware order goes back to the platform that created the customer, so bidding optimises on revenue instead of add to carts.
Trusted by 100+ lead generation businesses, agencies and freelancers
The gap
Shopware can show you a source per order. It cannot show you the journey or the spend.
A tracking plugin writes the campaign onto the order in the admin, and GA4 counts the purchase. Both are useful and neither answers the question the budget is decided on: which campaign produced the customers, at what cost, across the whole path.
Shopware tracking as most shops run it
A source on the order, a purchase in GA4, and a spreadsheet
- The tracking plugin records the parameters that were on the URL at that visit, so a customer who comes back later through a brand search overwrites the ad that introduced them.
- The source sits on the order in the admin. There is no spend in Shopware, so cost per order and ROAS are built in a spreadsheet beside the export.
- GA4 counts the purchase, in its own models, its own window and its own sampling, and its numbers stop agreeing with the order list within a week.
- The storefront tags run in the shopper's browser, so a blocked script, a declined consent banner and Safari's storage limits each cost you sources.
- Attribution starts on the storefront. A click that landed on a campaign page or a blog on another domain never joins the order.
- Every ad plugin fires its own pixel, so Google, Meta and Microsoft each count the same order for themselves and the reports add up to more than you sold.
- A repeat order carries whatever brought it back. The channel that acquired the customer is not in the report, and neither is the customer's lifetime value per channel.
- Nothing goes back to the ad account with the order value, so bidding optimises on carts and checkout starts.
Shopware with LeadJourney
One journey per customer, from the first click to the paid order
- Every storefront visit is recorded server-side and first-party at 95%+ accuracy, so a blocked tag or a declined banner does not cost you the source.
- The anonymous first click is kept and stitched to the customer at checkout, so first click, last click, linear and position based models all become available.
- Clicks that land on a campaign page or a blog outside the storefront are followed into the shop and onto the order.
- Spend is pulled from Google, Meta, Microsoft and LinkedIn Ads, so ROAS and cost per order are calculated per campaign on paid order value.
- The order carries its sales channel, so a B2B storefront, a B2C storefront and a marketplace are read apart instead of summed.
- Repeat orders are credited to the channel and campaign that acquired the customer, so lifetime value is reported per channel.
- Organic search, organic social, referral and AI search (ChatGPT, Perplexity, Gemini) are separate channels next to paid.
- The paid order goes back to Google, Meta, Microsoft and LinkedIn as an offline conversion with its value, matched on the click ID.
How it works
Shopware orders in, attributed revenue back out
Both directions run on their own once the script is in the storefront and the order is being handed over. The first is what makes Shopware attribution work across the whole journey. The second puts the paid order where the budget is decided.
1 Shopware revenue attribution from the first click to the paid order
The journey is recording before the shopper reaches a category page.
Ad clicks, click IDs, campaign parameters and every storefront session are recorded server-side across paid, organic and AI search.
Shopware hands the order over the moment it is paid, through a Flow Builder webhook, the Admin API or a Zap.
The order is matched to the journey that produced the customer, from the first anonymous click to the paid order.
Revenue, ROAS, cost per order and repeat order value, per channel, campaign, ad and sales channel.
2 The order goes back to the ad platform that earned it
So bidding optimises on paid orders instead of checkout starts.
An order is paid, a first time customer is created, a returning customer orders again.
LeadJourney turns it into a purchase event with the order value and currency, matched to the click ID that started the journey.
The event reaches the platforms server to server, as an offline conversion rather than a browser pixel.
Bidding learns which clicks become paying customers, so budget moves to the campaigns that sell.
The return path
Paid Shopware orders, back in the ad account that earned them
A checkout start is not a result. Once the transaction is paid, LeadJourney sends that outcome and its value to the platform that produced the click, so bidding learns from orders rather than from carts.
- Google AdsOffline conversion import
Orders matched on gclid, with the order value for value based bidding
- MetaConversions API
Order paid and first order, with order value and currency
- Microsoft AdsOffline conversions
Orders matched on msclkid, with the order value
- LinkedIn AdsConversions API
Orders matched on li_fat_id, with the order value
You choose what counts as a conversion
Map any order event to any platform event. Order paid, first order, repeat order, or all three.
Value based bidding gets the real order value
The order total travels with the event, so tROAS strategies optimise on what was paid instead of a flat conversion value.
Sent server to server
No pixel to fire on the finish page, so a declined banner or an ad blocker cannot remove the conversion.
Reporting
The questions the Shopware admin cannot answer
Every one of these is a report in LeadJourney rather than an export. Shopware stays the source of truth for orders, and LeadJourney supplies the journey that produced them.
Which campaign produced the orders we shipped last month, counting the first click and not only the last?
What does a new customer cost us in ad spend, per channel and per sales channel?
Which channel brings the customers who order again, and which brings the ones who buy once on a discount?
How much revenue did our B2B storefront take from paid search, separately from B2C?
How many orders started in ChatGPT, Perplexity or Gemini last quarter?
Which landing pages turn ad clicks into paid orders instead of abandoned checkouts?
LeadJourney and Shopware tracking
Where a Shopware tracking plugin ends and LeadJourney starts
A UTM plugin writes a source onto the order and GA4 counts the purchase. Both are right about their own slice. Neither has the journey, the spend or a way back to the ad platform.
| Capability | Shopware plus a tracking plugin | With LeadJourney |
|---|---|---|
| Where the source comes from | Shopware plus a tracking pluginThe parameters on the URL of that visit, read in the storefront and written onto the order. | With LeadJourneyEvery visit recorded server-side on your own domain, so the source survives a blocked tag, a declined banner and a return visit weeks later. |
| Attribution models | Shopware plus a tracking pluginLast click, one source per order. | With LeadJourneyFirst click, last click, linear and position based over the whole journey, switchable in the report. |
| The click before the storefront | Shopware plus a tracking pluginNot seen. A click that landed on a campaign page elsewhere is not joined to the order. | With LeadJourneyCaptured on any page carrying the script, followed into the storefront and stitched to the customer at checkout. |
| Ad spend, ROAS and cost per order | Shopware plus a tracking pluginNo spend in Shopware, so ROAS is a spreadsheet next to the order export. | With LeadJourneySpend pulled from Google, Meta, Microsoft and LinkedIn Ads, so ROAS is live per campaign on paid order value. |
| Multiple sales channels | Shopware plus a tracking pluginOrders carry their sales channel in the admin; the marketing report does not. | With LeadJourneyRevenue and ROAS per sales channel, so a B2B storefront is read apart from B2C rather than summed. |
| Repeat orders and lifetime value | Shopware plus a tracking pluginEach order carries its own source, so a repeat order is credited to whatever brought it back. | With LeadJourneyRepeat orders credited to the channel and campaign that acquired the customer, so lifetime value is reported per channel. |
| Purchase events back to the ad platforms | Shopware plus a tracking pluginEach ad plugin fires its own pixel in the browser, and each platform counts the order for itself. | With LeadJourneyOne server-side purchase event per paid order to every connected platform, with the order value, matched on the click ID. |
| Organic search, social and AI search | Shopware plus a tracking pluginA link without campaign parameters lands as direct or referral, and an AI assistant's citation is a referrer line rather than a channel. | With LeadJourneyOrganic search, organic social, referral and AI search are their own channels next to paid, with ChatGPT, Perplexity and Gemini named. |
| Refunds and cancellations | Shopware plus a tracking pluginNetted in the Shopware statistics, accurately. | With LeadJourneyRead alongside the order, so the revenue a campaign is credited with is the revenue you kept. |
| Consent and GDPR | Shopware plus a tracking pluginShopware's own cookie configuration covers the storefront, and every third party tag you add is yours to configure. | With LeadJourneyFirst-party by design and processed in the EU, with a data processing agreement. |
Keep Shopware and its plugins. Add the journey and the spend.
Shopware stays the system of record for orders and the place your team works. LeadJourney records the journey in front of the storefront, joins the spend from every platform you buy on, and hands the paid order back to the ad account that earned it.
MCP server
Chat with your Shopware revenue data
The same journeys, spend and paid orders are also served over MCP. Ask in Claude or ChatGPT, and the answer comes from your own numbers.
LeadJourney MCP connected, try any tab
Which campaigns produced our closed revenue last month?
Based on your LeadJourney data, 3 campaigns produced 148,200 EUR of closed revenue last month:
- Google Ads, Brand
- 38 leads, 9 closed deals, 61,400 EUR. Shortest path to signature.
- LinkedIn, Retargeting
- 21 leads, 6 closed deals, 48,900 EUR. Seven touchpoints on average.
- Meta, Lookalike DACH
- 54 leads, 5 closed deals, 37,900 EUR. Cheapest qualified lead.
Want this as a weekly summary in Slack?
Ask anything about your lead journeys
Where did our three biggest deals this quarter come from?
Your 3 largest deals this quarter all started somewhere the last click never showed you:
- 42,000 EUR
- First touch LinkedIn Ads, closed 63 days later after a webinar signup.
- 28,500 EUR
- First touch Google organic, paid click on day 11, demo on day 19.
- 21,800 EUR
- First touch a Meta video view, form filled from email six weeks on.
Want the full touchpoint list for any of them?
Ask anything about your closed deals
Which landing pages turn LinkedIn traffic into qualified leads?
3 pages take your LinkedIn traffic, and the qualified rate between them runs from 4% to 18%:
- /demo/attribution
- 18% qualified from 214 visits. Highest intent page on the site.
- /guide/server-side
- 9% qualified from 612 visits. Most journeys stall after the download.
- /pricing
- 4% qualified from 488 visits. Second most traffic, lowest intent.
Want the same breakdown for Google Ads traffic?
Ask anything about your landing pages
What did each channel cost per qualified lead last week?
3 channels spent budget last week. Cost per qualified lead ran from 41 EUR to 187 EUR:
- LinkedIn Ads
- 41 EUR per qualified lead. 2,300 EUR spent, 56 qualified.
- Google Ads
- 88 EUR per qualified lead. 4,400 EUR spent, 50 qualified.
- Meta Ads
- 187 EUR per qualified lead. 3,740 EUR spent, 20 qualified.
Want an alert the moment a channel passes 120 EUR?
Ask anything about your cost per lead
What do the journeys that close have in common?
3 signals show up in most of your closed deals and in almost none of the lost ones:
- Pricing page, 2+ visits
- In 71% of closed deals. In 12% of the ones that never closed.
- Demo within 14 days
- In 64% of closed deals. Median 9 days from the first click.
- Second contact
- In 58% of closed deals. A colleague of the lead arrives on site.
Want these three scored onto every lead in your CRM?
Ask anything about your lead journeys
Setup
Connected to Shopware in about 21 minutes
One script in the storefront, one handover for the order, no development project.
- 1About 5 minutes
Add the tracking script to your storefront
Paste the LeadJourney script into your storefront theme, or deliver it through the tag manager you already run. It records sessions, campaign parameters and click IDs on every page, category and product alike.
- 2About 10 minutes
Hand the paid order over
On the Evolve plan and up, Flow Builder does it with no code: trigger Checkout, Order, Placed, action Call URL, your LeadJourney endpoint. On Community Edition, use the Admin API or a Zapier, Make or n8n step, which reads the order and posts it the same way.
- 3Same day
Map order events to platform events
Choose which order events count as a conversion and which carry revenue. From then on every paid order flows back to the platform that earned it with the order value attached, and a first order can be told apart from a repeat one.
Original reviews
What our customers wrote, word for word
4.9 out of 5 across 11 public reviews. Quoted as they were left, shortened only by dropping whole sentences.
- 5 out of 5 starsGoogle
“Before LeadJourney, we had no reliable tracking concept for our five-figure ad spend. We were manually building spreadsheet and CRM reports, inaccurate and time-consuming. Within two days, everything was set up. For the first time, I know exactly what I pay per lead and which campaigns actually bring in the best-qualified prospects.”
Florian BuckCEO, Klickkraft GmbH “With LeadJourney we are able to track all our leads and connect them with sales and attribution data to make better decisions. In the first month of using it we scaled from 0 to 100k revenue from paid ads only.”
GetreachBacklinks Marketplace (SaaS)- 5 out of 5 starsG2
“LeadJourney finally fixed my Marketing Analytics. It goes way beyond basic Ad Tracking Software. The Customer Journey Report saves hours of digging, and capturing everything from Offline Conversions to AI Search Tracking makes it the Best B2B Attribution Platform available.”
Sascha LenzMarketing Manager
- 5 out of 5 starsTrustpilot
“Connected LeadJourney for 2 clients, setup took literally 20 minutes each. The data became more accurate, the reports actually make sense. Now clients look at the dashboard and the 'why don't the numbers match?' questions are gone.”
Alexander SamarPerformance Marketing Agency - 5 out of 5 starsGoogle
“With LeadJourney, we have finally found a tool that provides us with the data we need to scale our performance marketing campaigns. The most important KPI is no longer lead price but cost per qualified lead.”
Steffen SiesingCEO, Bilanzmanufaktur GmbH
- 5 out of 5 starsG2
“The ability to track both online and offline conversions in one unified dashboard has given us insights we never had before. Our ROI has improved dramatically since we started integrating LeadJourney with our CRM. We're finally able to see the full customer journey, and it's been a game changer for our strategy.”
Andre WitzelFounder, Trading.de - 5 out of 5 starsTrustpilot
“The ability to seamlessly integrate data from multiple channels and see real-time insights has significantly improved our campaign results. We now focus on metrics that truly matter, like ROI and qualified leads.”
Nikita YatsunCEO, RLV Media GmbH
Read the reviews where they were left
FAQ
What Shopware merchants and agencies ask first
If yours is not here, our team answers in the chat within a few minutes.
Is there a LeadJourney app in the Shopware Store?
Not today, and the page says so rather than implying one. Shopify is our one native shop integration. Shopware connects with what the platform already gives you: the tracking script in the storefront, and the paid order handed over by a Flow Builder webhook, the Admin API or a Zapier, Make or n8n step. No plugin development and no core changes.
Does the Flow Builder webhook work on Community Edition?
No. The Call URL action belongs to the Shopware Commercial extension, from the Evolve plan upwards, so a Community Edition shop cannot use it. That is why the setup names two paths: with Flow Builder it is a no-code flow, and without it the Admin API or an automation step reads the order and posts it. Both end with the same payload in LeadJourney.
What is server-side tracking in a Shopware shop, in practice?
The tag in the storefront records the visit against your own domain and the visit is then processed on the server rather than in the shopper's browser. What changes for you: a blocked script, an ad blocker, Safari's storage limits and a consent banner nobody clicked stop deciding whether the source of an order exists. The order itself arrives from Shopware, so it is never a browser event at all.
How does LeadJourney match a Shopware order to an ad click?
The journey is recorded from the first anonymous visit, on the storefront and on any other page carrying the script. When the order is handed over, it is matched to that journey, and every later order from the same customer joins it. Nothing has to be stored in a custom field for this to work.
Does LeadJourney write anything into Shopware?
No. The direction is one way: orders and refunds come out, nothing goes in. Your storefront, your checkout and your custom fields are unchanged, and Transparent Logs show every record that moved and when.
We run several sales channels. Are they reported apart?
Yes. A Shopware order carries the sales channel it was placed in, so revenue, ROAS and cost per order can be read per channel instead of summed. For a shop running a B2B storefront next to a B2C one, that is usually the first report worth opening: the two have different margins and almost never the same best campaign.
Are repeat orders attributed too?
Yes. A returning customer's orders are credited to the channel and campaign that acquired them, so lifetime value is reported per channel rather than as a first order snapshot. First and repeat orders can also go back to the ad platforms as separate events, which is how a new customer campaign is optimised on new customers.
Which Shopware events can I send back to Google and Meta?
Any event you map: order paid, first order, repeat order, or all of them. Each carries the order value and currency, and it reaches Google Ads as an offline conversion import matched on gclid, Meta through the Conversions API, Microsoft Ads matched on msclkid and LinkedIn through the Conversions API.
Is this compatible with GDPR and the German consent rules?
LeadJourney is first-party by design, processes and stores data in the EU and signs a data processing agreement. It is not a way around consent: what it does is make sure the data you are allowed to collect is not lost to a blocked third party script. Which tracking you may run without consent is a legal question for your own counsel, and the script respects the decision your consent tool records.
Do I need a developer?
The script is one paste into the storefront or one tag in your tag manager. On the Evolve plan the order handover is a Flow Builder flow with no code; on Community Edition an automation step does it. Most shops are reporting inside 21 minutes, and our team will do the setup with you on a call, with your agency if you work with one.
More integrations
More payments integrations
Connected the same way, attributed in the same dashboard. The rest of your stack reports right next to this one.
95%+ accuracy, hosted in the EU
See which campaigns produce Shopware orders with LeadJourney
Put the script in your storefront, hand the paid order over once, and watch every order line up against the campaign that brought the customer.
