Google Ads
Google Ads Conversion TrackingCalls, forms, bookings or purchases configured as the conversion actions Google Ads should optimise toward.
Explore Google Ads →
Conversion Tracking
Know which clicks actually become leads and revenue.
Adlyvo sets up measurement for calls, forms, bookings, messages or WhatsApp where applicable, and purchases or revenue where applicable, with browser and server-side tracking connected to GA4, Google Tag Manager and your ad platforms, so optimisation is based on outcomes you can trust.
- Calls + forms + bookings
- Purchases + revenue
- Browser + server-side
- GA4 / GTM / ad platforms
What should be tracked?
Not every click should count as a conversion.
These are the outcomes worth measuring, and which ones should actually drive optimisation.
Service businesses
- Phone callsPrimary
- Form submissionsPrimary
- BookingsPrimary
- WhatsApp / chat clicks, where applicablePrimary
- Page or button clicks on their ownSecondary
Ecommerce
- PurchasePrimary
- Revenue / conversion valuePrimary
- Add to cartSecondary
- Begin checkoutSecondary
The tracking journey
Every conversion follows the same path.
One consistent path from the first click to the decision it should inform.
- 1Traffic source
Where the visitor actually came from.
- 2Website / landing page
What they land on after the click.
- 3User action
What they do on the page.
- 4Conversion event
The action is captured as a defined event.
- 5Analytics / ad platform
The event reaches GA4 and the ad platform.
- 6Lead / purchase visibility
The outcome is visible by source and campaign.
- 7Optimisation
Budget and bidding follow what is actually working.
Where tracking breaks
Running campaigns on conversion data you cannot fully trust?
- Forms firing before successful submission
The event triggers on a button click, not on a confirmed, submitted form.
How Adlyvo helps: Forms are tracked on the success state, not the click that starts them. - Phone-click events treated like completed calls
Tapping a number is counted the same as an answered, meaningful conversation.
How Adlyvo helps: Phone-click and call-outcome data are kept separate so bidding is not misled. - Add to Cart counted as Purchase
Early funnel steps get treated as if the sale already happened.
How Adlyvo helps: Purchase is set as the primary ecommerce event, with cart and checkout kept secondary. - Browser and server events not deduplicated
The same action is sent twice, once from the browser and once from the server.
How Adlyvo helps: Browser and server events are matched and deduplicated before reporting relies on them. - Wrong GA4 property or container
Events fire correctly but land in the wrong property, container or view.
How Adlyvo helps: The destination is checked as part of implementation, not assumed to be correct. - Primary and secondary conversions misconfigured
Low-value engagement competes with real leads and sales for platform optimisation.
How Adlyvo helps: Primary conversions are limited to the actions that represent real business value. - Platform data not matching because definitions differ
Google Ads, GA4 and the backend each count a conversion slightly differently.
How Adlyvo helps: One conversion definition is documented and used consistently across platforms.
Browser, server-side + GA4/GTM
Two ways an event can reach analytics and ad platforms.
Browser-side
- 01Browser
- 02GTM / Pixel / Tag
- 03Analytics / Ads
Server-side
- 01Browser
- 02Server endpoint
- 03Analytics / Ads
A server layer can improve resilience and control over the data sent to analytics and ad platforms. It does not make tracking perfect, and it does not bypass privacy or consent requirements. Browser and server events usually need to be deduplicated so one action is not counted twice, and GA4 and Google Tag Manager need to agree on the same event definitions before either one reaches them.
Event namingSuccessful action vs. button clickPrimary vs. secondarySource visibilityTest and validation
Platform-specific tracking paths
This page is the broad hub. These go deeper by platform.
Meta Ads
Meta Pixel / Conversions APIBrowser and server-side Meta events connected with event matching and deduplication.
Explore Meta Ads →Server-Side
Server-Side TrackingA first-party server layer added where it solves a real measurement need, not by default.
Explore Server-Side →
Call tracking
A phone click is not the same as a completed call.
- Phone-number click
- The number was tapped. It does not confirm a call happened.
- Call from ads
- A call was placed through a tracked number shown on the ad or page.
- Call duration / qualified call, where supported
- Some setups can show call length or a qualified outcome, not just that a call connected.
- Imported / offline call outcome, where applicable
- What happened on the call, fed back from a call-tracking tool or the team, where that data exists.
We do not present a phone-number click as a real phone conversation. They are tracked and reported separately.
Form + booking tracking
"Successful submission" is a stronger signal than "button clicked."
Tracking the click that opens a form can look active while forms silently fail behind it. A booking works the same way: the useful signal is a confirmed booking, not just a button press that starts the process.
Ecommerce purchase tracking
Purchase is the primary event. Everything before it is a signal.
Transaction success, not just checkout startPurchase value captured with the eventDuplicate purchases preventedPurchase set as the primary ecommerce eventAdd to cart / checkout kept as secondary signals
Offline + lead quality visibility
A conversion is more useful when you know what happened after it.
Click identifier (e.g. GCLID), where supportedOffline conversion importQualified lead stagesCRM feedback
We cannot promise perfect closed-loop attribution. The goal is visibility into what a conversion actually led to, where that data is available.
How Adlyvo sets up tracking
A clear process, scoped to what your website and platforms need.
- 01
Tracking audit
See what is currently tracked, and what is missing, duplicated or misconfigured.
- 02
Define meaningful conversions
Agree which actions actually represent business value before touching any tag.
- 03
GTM / GA4 review
Check the container, property and event structure the tags rely on.
- 04
Platform event setup
Configure the events and conversions each ad platform needs.
- 05
Browser / server implementation, where needed
Add a server layer only where it solves a real measurement gap.
- 06
Deduplication / validation
Confirm one action is not counted twice across browser and server.
- 07
Primary vs secondary configuration
Set which events should drive bidding and which should not.
- 08
Test real success actions
Trigger real forms, calls, bookings or purchases and confirm the event lands correctly.
- 09
Document what is being measured
Leave a clear record of what each conversion actually means.
Who this is for
Built for businesses that need to trust their conversion data.
- Run Google Ads or Meta Ads
- Do not trust the conversion numbers you are seeing
- Have call or form discrepancies
- Need GA4 and GTM set up properly
- Need server-side tracking
- Track bookings
- Sell ecommerce products
- Need offline or qualified-lead visibility
The right setup depends on your website, platforms and business model. We do not promise fixed outcomes.
Cost & why Adlyvo
Honest pricing, and why the setup can be trusted.
How much does conversion tracking cost?
Scope depends on your website and the platforms involved, and not every implementation needs every advertising platform.
Browser Tracking$300starting / setup
Browser + Server Tracking$700starting / setup
- Website complexity
- Platforms used
- Call, form and booking mix
- Ecommerce vs service business
- Server-side need
- Existing tracking state
What determines tracking accuracy afterward?
We do not offer a fake ROI number for tracking itself. Accuracy is maintained, not just switched on once.
- Event naming consistency
- Primary vs secondary setup
- Deduplication
- Ongoing validation
- Website changes over time
- CRM / offline feedback
- 01
Meaningful conversion definition
Primary conversions are limited to actions that represent real business value, not clicks or page views.
- 02
Browser + server-side capability
A server layer is added where it solves a real problem, coordinated with browser events, not layered on by default.
- 03
Platform-specific validation
Google Ads, Meta and GA4 setups are tested end to end, not assumed to work from configuration alone.
- 04
Lead / purchase quality visibility
Conversions are connected to what happened after them, where that data is available.
The person behind your measurement setup
Ahasan H. Akash
Founder & Owner
Ahasan focuses on making sure campaign decisions are based on conversion data that actually reflects the business. That means defining what a conversion should mean, implementing it correctly across GA4, GTM and ad platforms, and testing it before it drives budget.
Meet the ownerFAQ
Conversion tracking questions, answered.
Why do Google Ads and GA4 show different conversion numbers?
They count differently. Attribution rules, timing, duplicated tags, misconfigured events or a conversion that exists in one tool but not the other can all cause gaps. A single conversion plan, tested end to end, makes the differences explainable.
Which actions should be primary conversions?
The actions that show real business value, such as qualified calls, completed forms and bookings. Lower-value interactions, like clicks on a page element, are usually secondary, so bidding does not optimize toward them. We map these before implementation.
Do I need Enhanced Conversions?
Not always. It is an option that helps Google Ads match conversions using additional first-party data where the technical setup allows it. Whether it is worth adding depends on your setup and the lead data available, and it is covered on the Google Ads tracking page.
Can you track website phone calls and form submissions?
Yes. Calls, forms, bookings and purchases can be measured, depending on how your website and phone setup work. Priority conversion paths are tested before handoff.
When do I need server-side tracking?
Only when there is a real measurement need, such as signal loss or platform matching issues that basic browser tracking does not solve. It is not recommended by default, and the Server-Side Tracking page explains when it makes sense.
How does Meta Pixel and Conversions API tracking fit in here?
This page covers the shared measurement foundation. Meta Pixel and CAPI setup, matching and deduplication go deeper on the Meta Ads Conversion Tracking page, linked above.
How is ecommerce purchase tracking different from lead tracking?
Ecommerce tracking centers on the purchase event and its value, with add to cart and checkout kept as secondary signals. Lead tracking centers on calls, forms and bookings, reviewed for quality after the fact.
How do you prevent duplicate conversions?
Duplicate counting usually comes from firing an event on both click and success, or from unmatched browser and server events. Both are checked and deduplicated as part of implementation and testing.
Can old or missing conversion data be recovered?
Not retroactively in most cases. If events were missing or misconfigured, that historical data usually cannot be rebuilt. The focus is on getting the setup trustworthy going forward and documenting what changed.
Running ads but not sure which conversions you can trust?
Adlyvo can review your calls, forms, bookings and purchase tracking to identify missing, duplicate or misleading conversion data before it costs you more budget.