The business: a new car service centre (anonymised). A “won” customer is a paid workshop visit, recorded in the service centre’s existing booking or workshop software. The setup reads that data for tracking; it does not replace or add invoicing.
The problem: more leads did not mean more customers
At launch we were running many ad sets across Meta, TikTok and Google. Each had its own cost per lead, and none of the ad accounts could tell us which of those leads became paying customers.
At the same time, leads were arriving faster than the team could handle them, and many were junk. Some came from loose targeting. Some were calls meant for an elderly-care service with a similar phone number. More leads did not mean more customers. It meant more calls to answer before anyone knew which leads were worth the time.
Cost per lead could not settle this. Only the paid workshop visit could: which ad sets brought customers who paid, and what should the team do with everyone else? Tracking is how you answer that. It decides where the ad budget goes and how the team spends its day. The report is a by-product.
This study covers version 1, which cost under €100 a month in tools and which any small business can copy, and summarises what version 2 added.
Version 1: every lead source in one list, for under €100 a month
Version 1 brought every source of leads into one list and one dashboard:
- Meta, TikTok and Google ads
- The service centre’s online booking portal
- Phone calls
- WhatsApp messages
- Meta lead forms
The launch ran on ClickUp, ManyChat and Make. The tools paid for this project alone cost about $50 a month. That figure leaves out subscriptions we share across projects, such as our base Make account; adding Make Core at about €11 a month (Table 1) still keeps the stack well under €100.
Four links from ad click to paid visit
- Capture. Every enquiry keeps the identifier of the ad click that started it: Google’s click ID (gclid, or gbraid and wbraid on some Apple devices), Meta’s fbclid, TikTok’s ttclid and the UTM parameters.
- Record. Every enquiry, from a website form, the booking portal, a call, a WhatsApp message or a Meta lead form, lands in one list with its source.
- Close. When the customer pays for a workshop visit, that record is marked “won” with the invoice value.
- Return. The paid visits go back to Google Ads, Meta and TikTok as conversions with a value, and onto one dashboard.
Ads
- Meta, TikTok and Google ads
Lead sources
- Website form
- Booking portal
- Phone call
- WhatsApp (ManyChat)
- Meta lead form
One list
- One CRM list (ClickUp, via Make.com)
Won
- Paid visit in workshop software
Back to the ads
- Google Ads (Data Manager)
- Meta (Conversions API)
- TikTok (Events API)
- Looker Studio dashboard
The stack and what it costs
Most of the stack is free. The paid parts are the automation tool and a messaging tool for WhatsApp and social DMs, plus, if needed, more CRM seats and server-side tracking.
| Part | Tool | Price | €/month, monthly billing | €/month, yearly billing |
|---|---|---|---|---|
| Tags and consent | Google Tag Manager, Consent Mode v2, consent banner | Free (banner tools vary) | 0 | 0 |
| Website analytics | GA4 | Free | 0 | 0 |
| Ad conversions | Google Ads conversion tracking, call reporting, Data Manager; Meta Pixel and Conversions API; TikTok Pixel and Events API | Free | 0 | 0 |
| Dashboard | Looker Studio | Free | 0 | 0 |
| Automation | Make Core, 10,000 credits | $12 billed monthly, $9 billed yearly | 10.69 | 8.02 |
| CRM list | ClickUp Free Forever, or Core per user | $0, or $12 monthly / $9 yearly per user | 0, or 10.69 per user | 0, or 8.02 per user |
| WhatsApp and DM leads | ManyChat Pro, 2,500 active contacts (WhatsApp needs Pro) | $39 monthly, $29 billed yearly | 34.75 | 25.84 |
| Server-side tracking (optional) | Stape, server GTM hosting | Free up to 10,000 requests; Pro $20 monthly, $17 yearly | 0, or 17.82 | 0, or 15.15 |
Prices from the vendors’ own pricing and help pages, checked 16 November 2026, converted at 1 USD = €0.8911 (exchange-rates.org, 9 November 2026). Excluding VAT, ad spend and WhatsApp message charges.
Three sample budgets, monthly billing:
- Minimal (about €11): free Google, Meta and TikTok tools, Make Core and ClickUp Free. No WhatsApp.
- Version 1 with WhatsApp and two CRM users (about €67): adds ManyChat Pro and ClickUp Core for two people.
- With server-side tracking (about €85): adds Stape Pro.
Yearly billing lowers each figure. WhatsApp messages are charged on top of ManyChat Pro, at rates that vary by country. ManyChat’s Free plan (25 active contacts) is enough to test the Instagram, Facebook and TikTok DM flows before paying, but it does not include WhatsApp.
The build, step by step
1. Capture the click on every enquiry
Add hidden fields to the website enquiry form for gclid, gbraid, wbraid, fbclid, ttclid and the five UTM parameters, filled from the landing page URL and kept in a first-party cookie so they survive a second page view. If the booking portal accepts URL parameters or hidden fields, pass the same values to it. Set up Consent Mode v2 first: for visitors in the EEA, Google requires consent signals before its tags can be used for ads measurement, and ad_user_data is the signal that covers it.
2. Track calls as well as forms
Many enquiries arrive by phone. Turn on call reporting in Google Ads: Google forwarding numbers are available in many countries, Germany included, so calls from Google ads and from the website (with a dynamically swapped number) count as conversions at no extra cost. Calls from Meta or TikTok ads are not covered this way, so in version 1 staff log each answered call in the CRM list with the source the caller gives. Version 2 closed that gap with the phone menu.
3. Write every enquiry to one list
A Make scenario receives each website form by webhook and creates a ClickUp task with the contact details, click IDs, UTMs and enquiry type. If the booking portal can send a webhook or a notification email, Make picks up each booking the same way. Make’s Facebook Lead Ads module watches for new Meta lead form submissions and writes them to the same list. Calls logged by staff and WhatsApp conversations from step 4 land there too. Statuses follow the service centre’s process: new, contacted, appointment booked, visit paid, lost.
4. Qualify WhatsApp and DM leads with ManyChat
ManyChat answers WhatsApp messages and Instagram, Facebook or TikTok DMs, asks two or three questions (vehicle, service needed, preferred date) and passes the answers and the contact to Make. Only qualified conversations become CRM entries. WhatsApp needs the Pro plan.
5. Mark the paid visit
The paid visit already exists in the workshop software. Two ways to bring it across:
- If the software has an export or an API, a scheduled Make scenario reads paid invoices and matches them to the CRM entry by phone number, email or licence plate, then sets the status to “visit paid” with the invoice value.
- If not, staff change the status by hand when the customer pays. At small volumes that is enough.
6. Send the outcome back to Google Ads
Since 15 June 2026, Google has moved offline conversion and enhanced-conversions-for-leads uploads to its Data Manager and blocks them in the Google Ads API. For a small business the practical route is a Google Sheet: Make appends one row per paid visit (click ID, conversion name, time, value, and the customer’s email or phone), and a scheduled Google Sheets connection in Google Ads Data Manager imports it. Data Manager imports conversions from up to 90 days back on each run, so the sheet must be up to date before each scheduled run. Hash email and phone with SHA-256 before upload; Make can do this in the same scenario.
7. Send the outcome back to Meta
Meta discontinued its Offline Conversions API in May 2025 and now takes offline and CRM events through the Conversions API. Make has ready-made Conversions API modules, so the same scenario sends a “Purchase” event with the visit value and hashed contact data when a lead becomes a paid visit. Meta asks for offline events to be uploaded within 62 days of the conversion.
8. Send the outcome back to TikTok
TikTok’s Events API 2.0 accepts CRM events. Create a CRM event set in TikTok Events Manager, then have Make send each paid visit to the Events API with an HTTP request, including the ttclid. Without an API setup, TikTok also accepts offline events as a CSV upload in Events Manager.
9. One dashboard
A Looker Studio report joins ad cost (the Google Ads connector, plus Meta and TikTok cost exports) with the CRM sheet: cost, leads, booked appointments, paid visits and revenue per ad set, and cost per paid visit by channel. This is the view that answers the opening question: which ad sets bring paying customers. In the full build we outgrew this: we first prototyped a dashboard on Make’s data store, then built our own dashboard on our own hosting.
Demo data — not real results
| Ad set | Channel | Cost € | Leads | Booked | Paid visits | Revenue € | Cost per paid visit € |
|---|---|---|---|---|---|---|---|
| Google Search – brake service | Google Ads | 900 | 60 | 18 | 12 | 2,400 | 75.00 |
| Google Search – inspection | Google Ads | 700 | 45 | 12 | 8 | 1,500 | 87.50 |
| Meta – oil change offer | Meta | 600 | 80 | 10 | 5 | 700 | 120.00 |
| TikTok – workshop video | TikTok | 400 | 50 | 6 | 2 | 300 | 200.00 |
Demo data, shown to illustrate the dashboard layout. These are not a client’s results.
GDPR and consent: what to get right
- A consent banner that passes all four Consent Mode v2 signals and blocks marketing tags until consent is given.
- Data processing agreements with each tool that handles customer data (Google, Meta, TikTok, Make, ClickUp, ManyChat, Stape).
- Hashed email and phone numbers in every upload to Google, Meta and TikTok.
- A retention period for CRM entries that never become customers, and a privacy notice that names the tools.
This section is a practical checklist, not legal advice. Check the setup with a data protection advisor.
Is server-side tracking worth it?
More than 10,000 server requests a month?
YesDo most enquiries arrive by phone?
YesNot a priority: track calls first (forwarding numbers, phone menu paths).
NoIs Meta or TikTok a main channel, with browser events going missing?
YesWorth it: Stape Pro at about €15 to €18 a month.
NoNot a priority yet.
NoUse Stape’s free tier (up to 10,000 requests a month).
Stape pricing and free plan limit, checked 16 November 2026.
What version 2 added
Version 1 showed which ad sets brought paying visits. It did not stop junk leads from reaching staff, and the source of calls from Meta and TikTok ads still depended on what callers said. Version 2 added six things.
Phone menu paths per campaign
Each campaign got its own path in the phone menu (IVR), so every call arrives with its source and the caller’s intent before anyone picks up. Calls from Meta and TikTok ads were now tracked too, not only calls from Google ads. The phone menu service is a separate cost and not part of the €100 budget.
Licence plates checked against a public vehicle registry
Leads gave their licence plate, and the plate was checked against a public vehicle registry to qualify the lead before anyone called back. This works only where such a registry is public. In Germany it is not: the Kraftfahrt-Bundesamt’s central vehicle register (ZFZR) answers only individual applications that show a legal reason (§ 39 StVG), at €5.10 per vehicle, which rules it out for qualifying leads.
Customer journeys that filter junk leads
Automated customer journeys sorted leads before they reached staff, so the team spent its time on people who could become customers.
Intent-based and geo-targeted campaigns
Campaigns were set up around intent and location, and segmented by service type and car brand. Version 2’s tracking was custom work: API connections between the service centre’s ERP, ManyChat, the booking platform and other tools tracked conversions per ad set, per creative, or at any other level or path we needed. That tracking is what let us get the most from these campaigns and keep acquisition costs low.
A channel strategy
We decided when to steer people to a call and when to WhatsApp, how leads from each channel are qualified, and how sales and workshop work are organised around them.
Our own dashboard, on our own hosting
Version 1 kept lead and performance data in Make’s data store, behind a quick prototype dashboard. In version 2 we built our own dashboard in-house and moved that data off Make onto our own hosting.
| Area | Version 1 (under €100 a month) | Version 2 added |
|---|---|---|
| Lead sources | Meta, TikTok and Google ads; booking portal; calls; WhatsApp; Meta lead forms in one list | Same sources |
| Calls | Google forwarding numbers; other calls logged by staff with the source the caller gives | Phone menu (IVR) path per campaign: every call shows its source and intent |
| Lead qualification | ManyChat questions in WhatsApp and DMs | Licence plates checked against a public vehicle registry (where one is public); customer journeys that filter junk leads |
| Tracking | Click IDs and UTMs to the CRM; paid visits back to Google, Meta and TikTok | Custom API connections between ERP, ManyChat, booking platform and other tools; conversions per ad set, creative or any path |
| Campaigns | Ad sets across Meta, TikTok and Google | Intent-based and geo-targeted campaigns by service type and car brand |
| Dashboard and data | Looker Studio on the CRM sheet; in the full build, lead and performance data sat in Make’s data store behind a quick prototype dashboard | Our own dashboard, built in-house, with the data moved off Make onto our own hosting |
| Operations | One list, statuses follow the workshop process | Channel strategy: when to steer to a call or WhatsApp, how each is qualified, how sales and workshop work around it |
| Cost | About $50 a month for project-specific tools at launch (shared subscriptions excluded) | The phone menu service is a separate cost, outside the €100 budget |
Tracking decides where the money goes
Connecting ads to paid visits is not about a better report. It decides which ad sets get more budget and which get cut, which channel each customer is steered to, and what the team does with each lead. Each version produced its own evidence:
A figure like the first one tells you where to steer customers and who needs to be free to answer the phone.
Key takeaways
- More leads did not mean more customers. Only tracking to the paid visit shows which ad sets pay.
- Version 1 put Meta, TikTok and Google ads, the booking portal, calls, WhatsApp and Meta lead forms into one list for under €100 a month in tools. The tools paid for the launch alone cost about $50 a month.
- In 2026 the routes back to the ad platforms are Google’s Data Manager, Meta’s Conversions API and TikTok’s Events API.
- Calls need a source too: forwarding numbers cover Google ads; per-campaign phone menu paths cover the rest.
- Consent comes first: without Consent Mode v2, EEA measurement stops working.
Not sure which of your ads bring paying customers? Book a growth audit. We check what your tracking records today, where the chain from click to paid visit breaks, and what it takes to connect it.
Sources
Prices (vendors’ own pages, checked 16 Nov 2026)
- Make: Pricing (Free 1,000 credits; Core $9/month billed yearly for 10,000 credits); Make vs Zapier (Core $9 on annual billing); Best AI automation tools (Core from $12 a month).
- ClickUp: FAQs (Free Forever $0; Core $9 per user/month billed yearly); What is ClickUp used for (Core $12 per user/month).
- ManyChat: Pricing; Pro plan ($39 monthly, $29 yearly, 2,500 active contacts); How to choose a plan (Free 25 contacts; WhatsApp from Pro); WhatsApp (message charges on top of Pro).
- Stape: Pricing (Free up to 10,000 requests; Pro $20 monthly, $17 yearly); Free plan limit.
- EUR/USD rate, 9 Nov 2026: exchange-rates.org.
Platform documentation
- Google Ads Help: About offline conversion imports (move to Data Manager from 15 June 2026).
- Google Ads Data Manager Help: Connect a data source (Google Sheets) and Prepare your data for import (90-day window, refresh before each run).
- Google Ads Help: Import conversions using files (hashing).
- Google Ads Help: About call reporting and Track calls from a website.
- Google Analytics Help: Consent mode for EEA users.
- Meta for Developers: Graph API v20.0 changelog (Offline Conversions API discontinued May 2025) and Conversions API: using the API (62-day upload window for offline events).
- Make: Facebook Lead Ads app, Facebook Conversions API app, Facebook Conversions API for CRM app.
- TikTok: Events API 2.0 overview (CRM events), How to postback signals through Events API (CRM event set), About offline conversions (CSV upload).
Vehicle registry (Germany)
- Deutscher Bundestag, Wissenschaftliche Dienste: WD 7 – 080/22 (access to the central vehicle register).
- Deutscher Bundestag: Drucksache 21/671 (fee of €5.10 per vehicle for a register enquiry under § 39 StVG).