Conversion tracking,
each inquiry counted once.
We plan the events, set up Tag Manager and GA4 with consent mode, and test every event before your reports rely on it.
One inquiry,
from the click to the customer.
One demo request to Ordwell, an imagined company. Sample data, not a client’s.
The click arrives
A visitor clicks an Ordwell ad. Google Ads adds a click ID next to the campaign tags, and the page keeps both for the form.
The page carries it
Hidden fields hold the click ID and the channel. Nobody types them in.
The form is accepted, once
Only an accepted form pushes the lead event. A failed send or a reload pushes none.
One event, checked
Tag Manager sends generate_lead to GA4, where it counts as a key event, and fires each ad platform tag once.
The lead becomes a customer
The lead reaches your CRM with its channel. When sales marks the lead as a customer, the report credits it to generic search.
Back to the ad platforms
Agreed separately: the customer stage goes back to Google Ads by click ID; stages of leads from Meta ads go to Meta through its Conversions API.
One report shows
which channels bring customers.
Both columns come from your CRM: one record for each accepted form, with the channel the form saved. GA4 key events are the cross-check.
Conversion reportOrdwell · first quarter after launch · from your CRM · sample
| Channel | Inquiries | Customers |
|---|---|---|
| Generic search (Google Ads) | 38 | 1 |
| Organic search (SEO) | 21 | 3 |
| Meta (Retargeting ads) | 17 | 0 |
| LinkedIn (Sponsored content) | 9 | 4 |
| Brand search (Google Ads) | 8 | 5 |
| Partner referrals (Tracked form) | 4 | 2 |
| Channel unknown | 6 | 1 |
Ranked by inquiries
Generic search brings the most inquiries, then organic search and Meta.
Your accounts,
your data.
GA4 property
Set up in your company’s own Google Analytics account, with you as administrator.
Tag Manager container
Every tag, trigger and published version stays in your account.
Ad accounts
Conversion tracking goes into the ad accounts you already run, such as Google Ads and Meta.
Tracking plan and test log
The tracking plan and the record of each test are yours to keep and to pass on.
What we need from you
Access to the site and the accounts, your consent choice, and a CRM that records which inquiries became customers.
The setup in five steps,
one to three weeks.
Each step ends with a decision you make.
To start
Plan
- Tracking plan
You decideWhich actions count as an inquiry?
Setup
Build
- Tag Manager container
- GA4 key events
- Consent mode
You decideWho changes the site: your developers or ours?
Setup
Test
- Test log
You decideDo both banner choices behave as agreed?
Launch
Publish
- Published container version
You decideWhen does the new version go live?
Handover
Report
- Conversion report
- Walkthrough
You decideWhen do you first compare the channels?
The setup on its own.
Or with your CRM feeding your ads.
1The setup
Tracking you can rely on.
One site, one to three weeks, every event tested, and a report of which channels bring customers.
2Agreed separately
CRM stages back to your ads.
Qualified leads and customers, sent to Google Ads and Meta. Quoted on its own.
Want each inquiry
counted once?
Tell us where inquiries arrive today, which ad platforms you use and how your CRM records a customer. We will reply with our questions and what we would check first.
Discuss your projectFrequently Asked Questions
The setup for one site is a one-time project of one to three weeks. The price depends on how many forms, calls and booking flows need events, the ad platforms involved, your consent banner and whether our developers or yours change the site; estimate it or tell us about your site. Sending CRM stages back to the ad platforms is quoted separately, and a custom data warehouse or BI integration is not part of the setup.
A shared document that names every event, says when it fires and what it carries, which events are key events, what consent each one needs and where it is sent. Developers build from it, and the next person to change the site knows what must keep working.
GA4’s name for an event that matters to your business, such as a demo request sent as generate_lead. It is marked as a key event in the GA4 settings. Google Ads still uses “conversion” for the actions it reports on and bids for.
They count differently. Each ad platform credits its own ads, with its own attribution and conversion window, and consent choices limit what every tag can record. Your CRM counts the people sales actually spoke to. We make the differences explainable, then report on the CRM stages that matter.
Consent mode passes the visitor’s banner choice to Google tags. In basic mode, Google tags load only after the visitor consents. In advanced mode they load at once and, while consent is denied, send cookieless pings that Google uses to model the gaps. Which mode fits is your decision with your legal advisers; we implement it and test both banner choices.
Yes, as separately agreed work once the setup runs. Google Ads imports them as offline conversions through its Data Manager, matched by the click ID or, with enhanced conversions for leads, by a hashed email. It accepts a stage only if it is uploaded no more than 90 days after the ad click (63 days with enhanced conversions for leads) and inside the conversion action’s window, so with long sales cycles, bidding learns from an earlier stage, such as a qualified lead. Meta receives the stages through its Conversions API and credits them only in a much shorter window after an ad click.
You do. The GA4 property and the Tag Manager container are set up in your company’s own accounts, with you as administrator, and conversion tracking is added to the ad accounts you already run. We work in all of them with the access you grant. The tracking plan and the test log are handed over with them.
Usually for two changes to your forms: hidden fields that carry the click ID and the channel into your CRM, and one event the site pushes when your server accepts the form. Our developers can make them, or we write the specification for yours; who makes them changes the quote. If the form does not reach your CRM yet, connecting it is integration work, quoted separately.
