A clinic owner in Mississauga launches Search ads for dental implants. After the first reporting cycle, Google Ads shows 200 clicks and zero conversions, while the agency asks for a larger budget. The owner's real question isn't whether the ads received traffic. It's which searches produced booked consultations, and whether the account can learn from those outcomes.
Without reliable Google Ads conversion tracking, that answer doesn't exist. The platform can't use a dependable signal for automated bidding, the business can't reconcile leads against its CRM, and offline bookings remain disconnected from the clicks that generated them. The problem becomes more urgent for Canadian advertisers because Google's planned June 15, 2026 transition will move offline conversion imports and enhanced conversions for leads uploads to the Data Manager API, blocking legacy uploads through the Google Ads API (Google's Canada Ads conversion tracking guidance).
This guide treats tracking as operating infrastructure, not a tag you install once and forget. It covers conversion actions, website and app setup, GA4 and offline data, enhanced conversions, server-side tagging, consent mode, silent measurement failures, diagnostics, and ongoing optimisation for Canadian local and e-commerce advertisers.
Why Conversion Tracking Matters Before You Spend Another Dollar
Every advertising dollar needs an outcome attached to it. A click is only a visit. A conversion records the business action that makes the visit commercially meaningful, such as a completed purchase, qualified lead, booked appointment, or phone call.
For the Mississauga clinic, a form submission may be an early signal, but a booked consultation is closer to the revenue event. If the CRM records the booking and Google Ads records nothing, the campaign appears empty even though the business may be receiving valuable demand. If Google Ads records every form interaction as a primary conversion, the campaign may optimise toward low-intent submissions instead of appointments.
The operational cost of missing signals
A campaign without a properly configured primary conversion action loses the feedback needed for automated bidding. Target CPA and Target ROAS strategies need conversion data and, where applicable, conversion values to make useful optimisation decisions. When the action is misclassified, duplicated, or never reaches Google Ads, the bidding system receives an incomplete account of performance.
That affects reporting as well. A clinic owner asking which keyword produced booked consultations needs a chain that connects the ad interaction, landing page event, lead record, appointment outcome, and final import. Without that chain, the team is left comparing clicks, form fills, and manually maintained spreadsheets.
Practical rule: Build the conversion and data pipeline before increasing budget. More traffic doesn't repair missing measurement. It only creates more unverified activity.
Canada-specific preparation
Google officially supports store visit conversions in Canada, which matters to businesses that depend on physical visits and local lead generation (Google's Canada conversion tracking page). Google also says Consent Mode can model conversions when users don't grant ad or analytics cookie consent, provided the implementation is correct and the account meets the relevant eligibility requirements. For each country and domain grouping, Google identifies a daily threshold of 700 ad clicks over a 7-day period for eligibility (Google Ads Consent Mode requirements).
Privacy compliance adds another layer. Canadian organisations should coordinate tagging decisions with their privacy counsel and consent-management process, including Quebec's Law 25 and applicable federal privacy requirements. A technically accurate tag that fires without the required permission can create a governance problem, while a consent-aware setup can preserve measurement through the mechanisms Google makes available.
The implementation below is designed around the API transition, so a new setup won't depend on legacy upload instructions that are scheduled to become unusable.
What Google Ads Conversion Tracking Actually Counts
Think of an ad click as a cash register ringing. It tells you that someone entered the buying process. A conversion action is the receipt, the record that confirms the person completed something you care about.
Google Ads separates several ideas that are often mixed together. Conversion source describes where the event originates, such as a website tag, app event, imported CRM outcome, or store visit measurement. Conversion action type describes what happened, such as a purchase or lead. Conversion status describes whether Google Ads is receiving and processing the signal.
Click-through and view-through actions
A click-through conversion occurs after someone clicks an ad and completes the defined action within the selected lookback window. For Search, the default click-through window is 30 days, although the account can use a different setting. A view-through conversion applies to eligible Display or YouTube exposure where the person saw an ad, didn't click, and converted within one day under the default window described in the setup guidance.
| Attribute | Click-Through Conversion | View-Through Conversion |
|---|---|---|
| Ad interaction | The user clicks the ad | The user sees the ad without clicking |
| Typical inventory | Search and other click-based interactions | Display or YouTube exposure |
| Default window | 30 days for Search | One day |
| Main interpretation | Direct response after an ad click | Conversion after an impression without a click |
| Audit question | Did the click lead to the action? | Did the impression receive too much credit? |
The practical distinction matters because a view-through conversion can make an awareness campaign look more directly responsible for a lead than the user journey supports. Review the window against the campaign's purpose instead of accepting every default.
For a broader framework on how different systems assign credit, compare the marketing attribution models guide.
Primary and secondary actions
A primary conversion action is included in the campaign's main Conversions reporting and can influence Smart Bidding. A secondary action remains useful for analysis, but it doesn't directly guide bidding. Add-to-cart, brochure downloads, and lower-intent button clicks often belong in the secondary group when a completed purchase or qualified lead is the actual objective.
You'll find these controls under Goals > Conversions > Summary. Open the conversion action, review its settings, and check the action's optimisation category, count method, value, windows, and attribution model. The edit panel and attribution model dropdown are where small defaults can create large reporting differences.
The terminology matters throughout an audit. “Recording” means Google Ads is receiving activity. “No recent conversions” means the action exists but hasn't recently received a qualifying event. “Tag not verified” points to an implementation or validation issue. Treat those statuses as diagnostic clues, not as performance conclusions.
Setting Up Tracking for Websites and Apps
Start with the conversion action, not the tag. In Google Ads, open Tools > Conversions, choose New conversion action, select Website, and enter the domain when prompted. If the scan doesn't produce the event you need, create the action manually so the business rule remains explicit.
Website configuration
Name the action so another person can understand it without opening the settings. “Booked consultation” is more useful than “Form event 2.” Select the category, such as Purchase, Lead, or Sign-up, then decide how Google should count it.
- Every: Use this where each completed transaction has value, such as e-commerce purchases.
- One: Use this where one lead or appointment should represent one valuable interaction from the ad journey.
- Value: Choose a fixed value only when the business has a defensible value estimate. For purchases, pass the actual transaction value from the data layer.
Google Ads will provide a conversion ID and conversion label in the installation instructions. Save both in the account's tracking specification. The ID identifies the Google Ads account, while the label identifies the conversion action used by the tag. Those identifiers become important when you later configure enhanced conversions or connect imported events.
You can install the Google tag and event snippet directly in the site code, or use Google Tag Manager. In GTM, create a Google Ads Conversion Tracking tag, enter the conversion ID and conversion label, and trigger it only when the confirmed conversion event occurs. A custom data layer event is usually safer than a loose thank-you-page trigger when the same page can load through multiple paths.
Test in GTM Preview and Tag Assistant before publishing. Complete a real test journey, inspect the event, confirm the tag fired once, and check that the value, currency, and transaction identifier are present when required.
The same principle applies to apps, but Firebase becomes the event source.
App event configuration
Link the Firebase project to Google Ads under Tools > Linked accounts. Enable automatic event recording where appropriate, then mark relevant events, such as in_app_purchase and first_open, as conversion events in Firebase. Review whether each event should feed primary bidding or remain secondary for analysis.
For iOS, configure the attribution key required for the app measurement setup and validate the post-iOS-17.4 implementation with the development team. The platform-specific plumbing differs from web tagging, but the reporting destination is shared: events ultimately populate the Google Ads conversion action list.
That shared destination is why naming, ownership, and identifier management matter. Record the conversion ID, label, event name, category, count rule, value logic, consent condition, and responsible system in one implementation document. Correcting an identifier once is faster than debugging several tags, app events, and CRM jobs that point to different actions.
Connecting GA4 and Importing Offline Conversions
A form submission is only the first signal. GA4 records the initial event, the CRM records whether the lead became qualified or booked, and Google Ads needs the final outcome attached to the conversion action used for bidding.
In GA4, identify the relevant events and mark them as key events. In the Google Analytics admin area, link the property to the correct Google Ads account, then inspect the imported conversion configuration in Google Ads. Confirm that the intended event maps to the correct conversion action. Check for a duplicate native Google Ads action tracking the same user behaviour, since duplicated imports can inflate reporting and bidding signals.
The Data Manager is now the planning surface for these connections. As covered in the migration timeline above, legacy upload paths stop accepting data on June 15, 2026. Build the production workflow around the Data Manager API rather than instructions for older Google Ads API uploads. The Google Canada conversion tracking guidance should be checked alongside your implementation plan for the current account requirements.
Offline data fields
Your CRM or booking system needs a stable connection between the lead and the ad interaction. The payload should identify the conversion action, record the conversion time with its timezone, and include the value and currency when those fields drive reporting or bidding. Depending on the selected matching method, it may also include a click identifier or approved first-party user information.
| Field | Format | Example |
|---|---|---|
| Click identifier | Stored identifier from the ad journey | CRM field containing the captured click ID |
| User identifier | Approved first-party identifier, handled according to consent requirements | Normalised email or phone value |
| Conversion time | Consistent date and time with timezone | CRM timestamp for qualified lead |
| Conversion value | Numeric business value when used | Revenue or approved lead value |
| Conversion action | Exact Google Ads action reference | Booked consultation action |
For enhanced conversions for leads, normalise and hash user-provided information according to Google's requirements before transmission. Keep that transformation and the consent decision in the data pipeline. Sales staff should not edit upload files manually.
Use a delivery cadence that matches the sales cycle. Then review Data Manager job history, validation errors, rejected records, and duplicate handling. The reporting and analytics service overview can support reconciliation across advertising, CRM, and revenue data when several systems report different stages of the same lead.
Engineering or the CRM vendor needs the conversion-action map, payload specification, authentication responsibilities, retry rules, duplicate-handling logic, timezone convention, and failed-job owner before the migration deadline. A CSV export can remain an internal source format, but the production delivery path must be ready for API submission, monitoring, and controlled retries.
Enhanced Conversions, Server-Side Tagging, and Consent Mode
A Canadian advertiser can have a purchase in the CRM while Google Ads receives no usable signal. Cookie restrictions expose that gap, but the fix is an API-ready measurement chain that combines enhanced conversions, server-side Google Tag Manager, and Consent Mode. Prepare the implementation for the June 15, 2026 Data Manager API migration rather than building another legacy upload workflow.
Start with consent, then add first-party data
Enhanced conversions use hashed first-party information, such as an email address, phone number, or address, to improve conversion matching when cookie-based attribution is limited. Google describes this as privacy-safe transmission through website tags or imported offline events in Google's Canada Privacy Hub.
In Google Ads, open the conversion action, enter its settings, and enable enhanced conversions where the account supports the option. In GTM, open the Google Ads conversion tag, select Include user-provided data from your website, and map approved values through a User-Provided Data variable.
The checkbox does not authorise unrestricted collection. Your CMP must pass the visitor's consent state, and the tag must use that state before sending user-provided data. Test both consent-granted and consent-denied journeys, including form submission and confirmation-page behaviour.
Route and verify the signal
Server-side GTM places a controlled endpoint between the browser and destination platforms. The web container sends the event, the server container receives it, and the configuration decides which fields reach Google Ads. Set up the GA4 client and relevant Google Ads processing components in the server container. Confirm that the event retains the conversion ID, label, value, currency, and consent state.
April 2026 consent-mode threshold rules make implementation quality and account eligibility operational concerns, not settings to postpone. Use Google Ads Consent Mode documentation alongside the account's consent diagnostics, then record the result for each test path.
In GTM Preview, submit a test conversion with consent granted and inspect the Google Ads tag. Check that the expected user-provided data variable resolves and that the consent panel shows the required permissions. Repeat with consent denied. The tag should reflect the restricted state, and no unauthorised user data should enter the request. Also inspect the server container event for the conversion fields and consent values.
Canadian teams should document the purpose, lawful basis, data fields, retention policy, CMP configuration, and access controls before enabling enhanced conversions. Include the organisation's privacy review, including Quebec's Law 25 and PIPEDA obligations where they apply. The chain is ready only when the business can explain what it collects, why it sends it, and how a visitor's choice changes processing.
Mistakes That Quietly Break Your Numbers
Installing a tag doesn't prove that the account measures reality. A dashboard can look healthy while the business counts the same outcome twice, assigns credit to the wrong campaign, or trains bidding on actions that don't represent revenue.
Four silent failure patterns
Double-counting happens when a native Google Ads tag and an imported GA4 event fire for the same purchase or lead, and both actions sit in the primary Conversions column. The fix is to choose one authoritative primary action and move supporting duplicates to secondary status or remove them.
Broken import links appear when the CRM stores no usable click identifier, sends the wrong conversion action, or changes the event name without updating the API mapping. A sales-qualified lead can exist in the CRM while Google Ads receives nothing.
Tag delay errors occur when the conversion event fires before the required Google tag, consent signal, or conversion linker state is available. Test slow page loads, form validation, single-page application navigation, and confirmation screens rather than testing only a fast desktop journey.
Misaligned goals arise when a campaign optimises toward page views, button clicks, or unqualified enquiries because those actions were marked primary. The account then reports activity as success, and Smart Bidding follows the signal it receives.
Attribution needs a deliberate choice
Last-click reporting can be easy to read, but it compresses a longer journey into a single interaction. Privacy restrictions and incomplete cross-device signals make that simplification even less reliable for many accounts. Use the attribution model dropdown, compare platform reports with CRM outcomes, and interpret assisted interactions as context rather than allowing them to inflate primary performance.
Your dashboard isn't automatically wrong. It may be answering a different question from the one your finance or sales team is asking.
Symptoms include conversions that feel too high, campaigns that look unprofitable despite closed business, or a sudden gap between form submissions and sales-qualified records. Treat those symptoms as an audit trigger. The next step is to trace one conversion from ad click through browser event, consent state, CRM record, and Google Ads receipt.
Troubleshooting When Conversions Disappear
When the Conversions column flatlines, don't begin by changing bids. Begin at the event source and move downstream in order.
A practical diagnostic sequence
Confirm the browser event. Open Tag Assistant or GA4 DebugView, complete a genuine test journey, and verify that the Google tag and conversion event fire on the intended page or data layer event.
Inspect the conversion action. Under Goals > Conversions > Summary, open the action and confirm it records conversions, belongs to the correct account, and is configured as primary when the campaign should optimise toward it. A secondary action can still exist while remaining outside the campaign's main bidding signal.
Check campaign selection. In the campaign's conversion goals, verify that the active campaign uses the action you tested. Account-level goals and campaign-specific goals can produce different reporting outcomes.
Review the Data Manager job log. For offline imports, inspect failed records and payload diagnostics. After the API transition, mismatched click identifiers, timezone drift, and malformed fields are practical places to look first.
Test consent and enhanced data. Confirm the CMP passes the expected consent state, the tag respects denied choices, and the User-Provided Data variable contains properly normalised values only when permitted.
Resolve discrepancies instead of averaging them away
Google Ads and GA4 won't necessarily show identical totals because they can use different event definitions, attribution settings, reporting windows, and processing logic. Compare the exact conversion action, date range, campaign scope, and event name before concluding that one platform is broken.
For lead businesses, compare Google Ads against the CRM's qualified and booked stages. For purchases, compare transaction identifiers and order records. Review the Conversion adjustment panel when a sale is cancelled, refunded, or later corrected.
If the account still fails after the implementation checks, open the Google Ads Help menu and submit a conversion diagnostics form ticket. Include the conversion action name, test timestamp, affected campaign, tag diagnostics, Data Manager job details, and the exact error message. A structured ticket gives support something testable instead of a general report that “conversions disappeared.”
Optimization Habits for Local and E-Commerce Advertisers
Conversion tracking should be managed like a revenue system. Local and e-commerce accounts need different primary actions, but both require regular checks that the data feeding bids still represents the business outcome.
Local service accounts
For a clinic, contractor, or professional service, separate an enquiry from a qualified opportunity and a booked appointment. Keep low-intent actions, such as brochure downloads or partial form starts, as secondary unless the business has a clear reason to optimise toward them.
Review call-conversion settings regularly, test phone numbers on mobile and desktop, and reconcile booked appointments against CRM imports through the Data Manager API. Check that appointment status changes don't create duplicate imports, and maintain audience exclusions so existing converters aren't repeatedly treated as fresh prospects.
A useful local workflow is:
- Primary goal: Booked consultation, qualified call, or completed lead form.
- Secondary signals: Appointment request, direction request, engaged visit, or form start.
- Offline outcome: Qualified, attended, or revenue-producing appointment, depending on the sales process.
- Review point: Compare the Google Ads action with the CRM stage, not only the web form count.
For conversion-rate work, pair tracking diagnostics with the practical recommendations in this guide to improve conversion rate on a website. A perfect tag can't compensate for a confusing form, weak offer, or slow follow-up.
E-commerce accounts
Use a purchase action that receives the actual transaction value, currency, and transaction identifier. Distinguish new and returning customers in the business logic where the account can support that segmentation, and use value rules only when the weighting reflects a genuine commercial priority, such as margin or product mix.
Micro-conversions can enrich analysis without taking over bidding. Add-to-cart, checkout start, and email signup actions commonly work as secondary signals, while completed purchases remain the primary outcome.
Run a recurring technical review that checks:
- Enhanced-conversion data is sent only under the approved consent conditions.
- Consent Mode parameters still align with the organisation's privacy process.
- Transaction identifiers prevent duplicate purchase reporting.
- Customer Match lists are re-exported and governed through the current consent and data policy.
- The conversion action used by the bid strategy is still the one the finance team trusts.
Juiced Digital offers paid advertising support with an AI dashboard that brings performance and lead-source data from platforms including Google, Meta, TikTok, and LinkedIn into a shared view. For a Canadian business preparing its tracking architecture, that kind of cross-channel reporting can support reconciliation without replacing the source-level diagnostics described above.
Juiced Digital can audit your Google Ads conversion tracking, prepare the Data Manager API migration, and connect website, CRM, consent, and revenue signals for local or e-commerce campaigns. Visit Juiced Digital to request a practical tracking audit and discuss the implementation work your account needs before the 2026 transition.
