How conversion tracking works
Three pieces have to line up. First, somebody decides what counts as a conversion: a completed enquiry form, a call from the website, a message, a purchase. Second, something on the site notices that the action happened and fires an event — a tag, a snippet of code, a plugin on the form. Third, the platform that sent the visitor matches that event back to the click it recorded earlier, using an identifier stored when the person arrived.
Skip the third step and you have analytics but not attribution: you know a sale happened, but not which ad, keyword or post produced it. That matching is why click identifiers turn up in ad URLs, why platforms offer a server-side route for events that browsers block, and why an offline conversion — a deal closed on the phone weeks later — has to be imported back into the account rather than caught in a browser.
Why conversion tracking matters
Every decision downstream depends on it. Automated bidding learns only from the conversions it is shown, so if a good share of them never arrive, the system optimises towards the ones it can see. Budget shifts, paused keywords and creative choices all inherit that same distortion without anyone noticing.
It also changes the conversation with a client or a manager. Without it, the honest report is traffic and cost; with it, the report is enquiries and cost per enquiry, which is the figure people outside marketing actually care about. That matters more than usual in Nepal, where a great deal of demand ends in a phone call, a Viber message or a walk-in, so a setup counting only form submissions will understate the work badly.
Where conversion tracking goes wrong
Counting the wrong thing is the biggest failure and the hardest to notice. A thank-you page that can be reloaded, bookmarked or reached directly inflates the count. Treating a visit to the contact page as a conversion records intent rather than outcome. Marking every small interaction as a conversion teaches the bidding system to buy the cheapest and least valuable ones.
Then there is double counting — a native tag and an imported key event both recording the same sale, or a browser pixel and a server event that were never deduplicated. Duplicates always flatter, which is why they survive so long unquestioned. A setup that worked at launch also decays quietly as forms are redesigned, checkouts replaced and plugins updated, so a check nobody runs is a check that eventually fails.
How to get it right
Write down what a conversion means for the business before touching a tag, and separate the actions that show real commitment from the ones that are only steps along the way. Give each action a value, even an estimated one, so the platform can tell a small enquiry apart from a large one instead of treating them as identical.
Fire conversions on the event itself rather than on a page view wherever that is possible, test with the platform’s own debugging tools before trusting a single figure, and mark useful but minor actions as secondary so they inform reporting without steering the bidding. Then recheck after every site change. The mechanics differ by platform, and the detail for search, shopping and Performance Max campaigns sits with Google Ads conversion tracking.