Does your ad report count enquiries or repeated actions?

Define one result before comparing reports

A form submission, a person asking for help and a completed job are different results. Before asking AI to summarize advertising performance, write down which result each number represents. An assistant can reconcile records, but it cannot turn a tracked action into a customer simply by labelling it a lead.

Check the count setting for each action

Google Ads lets you choose counting settings separately for conversion actions. Every counts each recorded conversion for that action after an ad interaction. One limits the count for that action per ad click. Google describes One as useful for leads and Every as useful for sales. One is not a unique-person count across your entire business. Changes affect future reporting rather than rewriting past data.

Per-action One versus Every counting and prospective changes. The repair-shop scenario and time calculation are illustrative. Google Ads: conversion counting options

Work through a sample customer journey

Imagine a fictional repair shop tracking an estimate request and a booking request as separate actions. After one ad click, a customer submits the estimate form twice and requests a booking. Counting One for each action can still produce two conversions, although the office has one customer conversation. The review should explain that difference rather than force every dashboard total to match.

Prepare a review pack before changing settings

Record each action name, trigger, data source, counting setting and responsible person. Compare sample submissions with the enquiries your office received. Flag repeated events, missing records and separate actions describing the same journey. Use reference numbers instead of unnecessary personal details. Check the existing tags and any Analytics imports before adding another integration. The output is a short proposed-change list for the advertising owner to approve, not an automatic rewrite of campaign measurement.

Keep the comparison honest

Record the old setting and the date of an approved change. Annotate subsequent reports so a lower conversion count is not mistaken for an immediate loss of customers. Preserve historical figures and track qualified enquiries and booked work separately. Test the report with sample repeated submissions and different action types. A native setting may be sufficient; custom automation is useful only if ongoing reconciliation justifies it.

Measure the time saved separately

In an illustrative month, four reconciliations taking 30 minutes each use two hours. Reducing each to 15 minutes releases one hour of staff capacity, not proven ad savings or extra revenue. Compare that with setup, software and review costs. Exovara can help connect advertising definitions with office records so spending decisions reflect the work your business actually wins.

Discuss an implementation

This guide applies across Canada. We provide remote AI consulting for businesses in London; it does not describe a local client or a staffed office.

AI consulting in London · Explore the service · Compare setup options