Hot tubs sell at your LOU counter. Google Ads never hears about it.
"The hot tub buyer said they saw our ad, but Google Ads shows nothing." In a LOU store the sale is rung up at the counter in LOU Retail POS, days after the click, with nothing linking the two. We carry the click from your website into the LOU customer record and send invoiced sales back to Google and Meta, so campaigns learn from spas, stoves and service contracts that closed.
Free30 minutesNo obligation
Evosus LOU · what breaks
What goes wrong when your sales live in Evosus LOU
- 01
"Our ads sell hot tubs, but Google can't see it"
A spa or fireplace sale is invoiced in LOU after a showroom visit, so Google Ads only counts the web form. Bidding keeps buying cheap form fills instead of the shoppers who walk in and buy a spa or stove at your counter.
- 02
"Whoever answers the phone types the lead in"
Your website catches the consultation request or pool-opening call, then staff key the customer into LOU by hand. The click ID dies there, so you can't tell which campaign booked the job.
- 03
"Meta has no idea anyone bought online"
LOUcommerce's admin panel documents a Google Analytics switch and no field for the Meta Pixel or a tag manager. Unless someone added code we can't see, the chemical, filter and accessory orders your ads drive go uncounted in Meta, so it optimizes blind.
- 04
"Analytics says we made more online than LOU does"
Evosus says every LOUcommerce refund belongs in LOU Web or LOU Retail POS, never in the storefront. Nothing we found passes that return back to Analytics, so online return on ad spend looks better than your books.
Evosus LOU · the fix
What changes after the fix — Evosus LOU
Campaigns graded on invoiced sales
Google and Meta see the hot tub, stove or service contract you rang up in LOU, valued from the invoice, so bidding chases buyers rather than browsers.
Every ad lead traceable in LOU
The click ID and campaign ride along from your website form or tracked call into the customer you create in LOU.
Online revenue that matches LOU
LOUcommerce purchases fire once per order across Google Analytics, Google Ads and Meta, and returns rung up in LOU are subtracted from what you report.
Evosus LOU · architecture
What Evosus LOU actually lets you hook into
LOU is built around POS, service routes, inventory and accounting, not ad tracking. Here's what Evosus documents, and what we confirm with your LOU team.
- 1
LOUcommerce Google Analytics setting
The storefront admin panel has an Analytics option to enable Google Analytics. We check it records purchases with value, not just page views.
- 2
Custom domain or LOU-provided domain
Evosus says LOUcommerce can run on your own domain or one it provides. On a separate domain, a visit from your main site can split into two sessions.
- 3
No documented Pixel or tag manager slot
The admin documentation lists Custom CSS and templates, but no header script, Meta Pixel or Google Tag Manager field. We confirm with Evosus rather than assume.
- 4
Report exports in Excel, CSV and PDF
Evosus says all LOU reports export. Invoice and customer exports become the source for offline conversion uploads.
- 5
LOU API by request
API access is requested through a form on the Evosus site, and the data it exposes isn't published. We find out before planning automated uploads.
- 6
No ad platform integrations listed
The integrations page names Heritage, Carecraft, Pool360, Avalara and QuickBooks Online. Nothing for Google Ads, Meta or Zapier.
Evosus LOU · diagnose
Where Evosus LOU tracking breaks, in the order we check
Start with the handoff from your website to LOU, because that's where most dealers lose the ad click for good.
- 01
Find where ad leads enter LOU
Form, phone or walk-in, and who keys them in.
- 02
Check whether a click ID reaches the customer record
Submit a test lead from an ad-tagged URL and open the customer in LOU.
- 03
Test a LOUcommerce purchase end to end
Confirm the Google Analytics purchase fires with the order total, on which domain, and whether Meta sees anything.
- 04
Compare new-customer invoices with ad-reported conversions
Over a closed month, export from LOU.
- 05
Look for refunds and duplicate customers
Returns done in LOU Web or POS, and repeat buyers who checked out with a different email and became a second customer.
Evosus LOU · prove
The QA evidence — Evosus LOU
Run on real leads and orders in your live LOU account and storefront, not a demo company.
Source of truth
Evosus LOU invoices and LOUcommerce orders: sales by date, customer and amount, with returns as processed in LOU Web or LOU Retail POS
- A test lead from an ad-tagged URL, with the click ID confirmed on the LOU customer record.
- One POS invoice uploaded and accepted in Google Ads as an offline conversion.
- The same sale received by Meta as a physical-store event through the Conversions API.
- Exactly one LOUcommerce purchase per order in Google Analytics, Google Ads and Meta.
- A return processed in LOU Web subtracted from reported revenue.
- Repeated 30 days later and after any change to the storefront domain or template.
Evosus LOU · free audit
What we check in the free audit
- Find where ad leads enter LOU
- Check whether a click ID reaches the customer record
- Test a LOUcommerce purchase end to end
- Compare new-customer invoices with ad-reported conversions
- Look for refunds and duplicate customers
Checked against
Evosus LOU invoices and LOUcommerce orders: sales by date, customer and amount, with returns as processed in LOU Web or LOU Retail POS
Free30 minutesNo obligation
Evosus LOU · when not to buy
When you don't need this on Evosus LOU
Plenty of LOU dealers are better off spending the money elsewhere.
- If you don't run paid ads and your business is route customers and walk-in chemical sales, there's nothing to attribute.
- If LOUcommerce only serves existing customers who arrive from your digital doorhanger links, ad tracking on it adds little.
- If your route calendar is already full before spring openings, fix capacity before buying more leads.
Evosus LOU · what we deliver
The event map on Evosus LOU
Website lead or tracked call
Spa consultation requests, service calls and quote forms captured on your own site with the click ID.
Customer created in LOU
The qualified step: the record staff open for that lead, with the click ID stored where we confirm LOU can hold it.
Service job scheduled
Pool openings, closings, chimney sweeps and repairs booked on the LOU schedule, sent as a booked-job signal.
Showroom sale invoiced
The money event: a POS invoice for a new customer, valued from the invoice total and matched to the original click.
LOUcommerce order placed
An online purchase with its order value, sent from one owner so Google and Meta each count it once.
Excluded or reversed
Returns rung up in LOU Web or POS reversed where each platform allows it; route customers paying invoices through their customer profile kept out of acquisition.
Written guarantee
95%+ tracking accuracy
Measured against Evosus LOU invoices and LOUcommerce orders: sales by date, customer and amount, with returns as processed in LOU Web or LOU Retail POS. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Evosus LOU questions, answered
Not that we found. The LOU integrations page lists Heritage, Carecraft, Pool360, Avalara and QuickBooks Online, and LOUcommerce documents only a Google Analytics setting.
Evosus's admin documentation doesn't show a Pixel or tag manager field, so we confirm with your LOU team first. If there isn't one, purchases go to Meta server-side from your order data instead.
We capture the Google click ID when the lead comes in, keep it with the LOU customer, and upload the invoiced sale as an offline conversion. Enhanced conversions for leads can match by hashed email too.
Evosus has you process LOUcommerce refunds in LOU Web or LOU Retail POS, not in the storefront, and we found no documented way for those returns to reach Analytics. We send them as refunds where each platform accepts it.
Not to start. LOU reports export to CSV and Excel, which is enough for regular uploads; API access is something Evosus grants on request if we automate later.
More on Evosus LOU
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Evosus LOU, and what their bookings feed
- Route4MeRoute4Me knows which quotes became serviced stops. Your ads still count every form fill.
- TurnoYour ads win Airbnb hosts, then they disappear into Turno
- FieldRoutesYour FieldRoutes widget sells pest plans online. Google Ads can't tell which ads sold them.
- BuildOpsYour BuildOps pipeline knows which ads won contracts. Google and Meta don't.
- ServiceMonsterServiceMonster shows the invoice. Google Ads can't tell you which click booked it.
- CorrigoYour best accounts work through Corrigo. Google Ads never hears about them.
- BreezewayYour ads land vacation rental clients. Breezeway never tells Google which ones.
- VonigoVonigo conversion tracking: the schedule is full, but which ads booked the truck?
Free · 30 min
Find out which ads actually sell in your LOU store
Free30 minutesNo obligation
