How do I set up conversion tracking?

The distinction matters because analytics arrives with page views working automatically and conversions requiring deliberate setup. A business that pasted the tracking code and stopped has a system counting visits and nothing else, which means every subsequent question about which marketing produced customers is unanswerable.

Start by listing what a visitor could do that is worth something. Submitting the contact form, tapping the phone number, tapping an email address, starting the intake form, and booking if you have scheduling. Those are the actions that indicate intent, and each is a separate thing to record rather than one general goal.

The form submission is the most important and the most commonly misconfigured. If your form shows a confirmation on the same page rather than redirecting, there is no new page load for analytics to notice, which means the default approach of counting arrivals at a thank you page records nothing. That situation requires firing the event from the code that handles the successful response, which is a line in the script rather than a setting.

Phone taps matter more than owners expect for a local business, since a substantial share of enquiries arrive that way and none of them appear as form submissions. Making the number a link rather than plain text is the prerequisite, and once it is a link the tap can be recorded like any other click.

Mark the important ones as key events in your analytics, which is a separate step from recording them. An event that fires and is not marked will count in the event list and will not appear in conversion reporting, which is where most people look. This is an administrative toggle and it requires the event to have fired at least once before it appears.

Verify each one by performing it yourself and watching the realtime report, rather than assuming configuration means function. Then repeat that check quarterly, because form notifications and tracking both break silently when hosting changes, a plugin updates, or a mail provider tightens its rules.

Add the source information if you can, so a conversion records which page it came from and which campaign brought the visitor. That detail is what turns a count into an answer about which effort produced anything, and it costs nothing beyond configuring the parameters when the event fires.

Then remember that conversion tracking captures what happened on the site and misses everything else. Referrals, walk ins, and people who found you through a listing and called directly never touch it, which is why asking every customer how they found you remains the more reliable record for a local business.

Give each conversion a name you will recognise in six months rather than accepting a default, because a report listing several generically named events is unreadable. Something describing the action and the page is enough, and renaming afterward loses the historical data.

Set it up before spending anything on advertising rather than alongside, since a month of unmeasurable spend cannot be reconstructed and the conclusions drawn from it are guesses that will inform the second month.

Record the source alongside each conversion where the platform allows it, since knowing that ten enquiries arrived is considerably less useful than knowing which pages and which campaigns produced them. That detail is configured when the event fires and cannot be added retrospectively to conversions already recorded.