Solar Google Ads conversion tracking from click to CRM

The audit finding that surprises most solar operators is simple: Google Ads is doing exactly what you asked it to. The question is whether what you asked for is what you actually want.

A Google Ads account optimised against form submissions, which is the default for most solar landing pages, will pull in the cheapest form submissions in the auction. Those are not the same thing as the cheapest sat appointments. In the typical solar funnel, roughly half of the form fills never book a survey, so by optimising on form fills the account is spending budget to maximise a mix that includes a lot of noise.

The fix is to measure the thing that actually matters, which is the sat appointment, and feed that signal back to Google so the auction optimises for it. That is a four-stage tracking job, not a one-click toggle, and most solar accounts do only the first stage. The broader account build sits in google ads for solar contractors; this piece lays out the measurement layer.

What are the four stages of solar Google Ads tracking?

In order from least to most useful:

Stage 1: Click to form fill, in GA4. The basic install. A thank-you page fires a GA4 event, the event is imported into Google Ads as a conversion, the account optimises toward form fills. This is where most solar accounts stop. It is better than nothing, but it hides the real work.

Stage 2: Click to answered call, via a call tracking number. A dynamic phone number on the landing page swaps to a tracked number when the visitor arrived from a Google Ads click. Calls to that number ring through to your main line but are logged with the originating click. The call is marked as a conversion once it is answered for a defined duration (usually 30 seconds). For most solar accounts this doubles the number of conversions Google sees, because 40 to 60 percent of paid solar leads come by phone rather than form.

Stage 3: Click to sat appointment, via offline conversion import. The CRM flags a lead as a sat appointment at the moment the sales rep confirms the appointment was attended. That event, with the original gclid from the ad click, is uploaded back to Google Ads as an offline conversion. Google now has the real downstream signal and can optimise toward the ad clicks that actually produce sat appointments, not just form fills.

Stage 4: Enhanced conversions with first-party data. For every conversion, hashed first-party data (email, phone, name) is sent to Google alongside the gclid. When the browser's gclid cookie is missing or stale (Safari, incognito, iOS privacy), Google can still match the conversion to a click via the hashed data. Enhanced conversions typically recover 15 to 25 percent of attribution lost to privacy signals and are a 15-minute setup on most modern tag managers.

A solar account running all four stages has a materially different conversation with the ad platform than one running only the first. For the cost ranges each stage changes, see what solar leads actually cost on Google Ads.

How does call tracking work mechanically?

The visitor lands on the page. A piece of JavaScript on the page detects whether the visitor arrived from a Google Ads click (either via the gclid URL parameter or a session cookie). If so, the phone number displayed on the page swaps from your main business number to a tracked number from the call tracking provider.

When the visitor calls that number, the call tracking provider routes the call through to your business line, records the start time and duration, and attaches the original gclid as metadata. If the call lasts longer than the duration you defined (30 seconds, 60 seconds, whatever threshold you set), the call tracking provider sends a conversion event back to Google Ads with the gclid attached.

Common providers include CallRail, CallTrackingMetrics, and ServiceCore. All of them integrate with Google Ads via a native connector; setup time is usually under 30 minutes once the account is created.

The watch-out: swap the phone number on every surface the visitor might convert from, not just the hero. A footer phone number that stays static is where 20 to 30 percent of your calls will come from on a long page, and those calls are untracked. The dynamic number insertion script needs to find every phone number on the page.

Why does enhanced conversions matter for solar?

Enhanced conversions matter because Safari and iOS privacy signals break the gclid cookie for roughly a third of US web traffic. When a visitor clicks an ad on an iPhone, lands on your landing page, and fills a form two days later from a different browser session, the gclid cookie may already be expired or missing. Google cannot attribute the conversion to the original click, and the ad that drove the eventual lead gets no credit.

Enhanced conversions fix the attribution gap by sending Google a hashed version of the visitor's email and phone when they convert. Google compares the hash against hashed data from signed-in Google users and matches the conversion to the originating ad click even when the cookie is gone. The visitor's identity is never exposed to Google; the match happens on the hash.

The setup is in Google Tag Manager or whatever tag manager the site uses. You add fields to the conversion event for email, phone, first name, last name, and address, all hashed before transmission. In Google Ads, under conversion settings, you enable enhanced conversions and link the event. The whole setup takes 15 to 30 minutes.

Recovery varies by account but typically runs 15 to 25 percent more attributed conversions on the same ad spend after enhanced conversions are enabled. That is 15 to 25 percent more signal for Google's bidding algorithms to use, which means better optimisation on the same budget.

How do offline conversion imports work for the sat appointment?

Offline conversion imports are where most solar accounts have the biggest open opportunity. The mechanics:

1. 01The ad click fires a gclid. The landing page captures the gclid in a hidden form field and stores it on the lead in the CRM.
2. 02The lead progresses through the CRM: form fill, qualified, appointment set, appointment confirmed, appointment attended (sat).
3. 03At the moment the lead becomes a sat appointment, the CRM fires an event that includes the gclid and the conversion value (if you choose to pass one).
4. 04The event is pushed to Google Ads via the Offline Conversion Import API (or via a CSV upload, which also works). The import can run daily or on each event.
5. 05Google Ads logs the sat appointment as a conversion attributed to the original ad click.

A CRM with native Google Ads integration (HubSpot, Pipedrive with the right add-on, Volt Relay) sets this up through a native connector in 30 to 60 minutes. A CRM without native integration needs a Zapier flow or a cron job that pushes the CSV, which takes 2 to 4 hours.

The gain, once the import is running: Google Ads can now optimise toward the ad clicks that produce sat appointments, which is the downstream signal that actually matches your business economics. In accounts we have moved from form-fill optimisation to sat-appointment optimisation, cost per sat appointment typically falls 20 to 35 percent inside 60 to 90 days as the algorithm reallocates spend.

What should the setup order be?

The sequence that works, from fastest return to slowest:

Week 1: Call tracking. Easiest single win. 30 minutes of setup, immediately doubles the number of conversions Google sees, and reveals which campaigns actually drive phone leads versus just form leads. Many solar operators discover that a campaign they thought was underperforming was actually their best campaign because 70 percent of its conversions came by phone and were invisible.

Week 2: Enhanced conversions. 15 to 30 minutes of setup. Immediate 15 to 25 percent lift in attributed conversions. Zero additional cost.

Weeks 3 to 4: Offline conversion imports for sat appointments. The biggest-impact fix and the one that takes the longest to set up and tune. Allow 30 to 60 days after turning it on for Google's bidding to learn against the new signal. Expect cost per lead to look worse in the first 2 to 3 weeks as the algorithm reallocates, then noticeably better by day 60.

Week 5 onward: Install conversions tracking. For accounts with enough volume to attribute reliably at the install level (usually 50 or more installs per quarter), import the closed-install event as a secondary conversion. This gives Google the fullest downstream signal possible, though it is only worth setting up once the earlier stages are solid.

Doing the stages out of order is one of the biggest wastes we see. Operators who set up offline conversion imports before enhanced conversions find that the gclid is missing on a third of their imports because the cookie was lost; the sat appointment imports therefore cover only two thirds of real sat appointments and the signal is weakened.

Where does the pipeline usually leak?

Three common failure points:

The gclid never reaches the CRM. The landing page form has a gclid field, but it is not set up to capture the URL parameter, or the parameter is stripped by a tracking pixel before the form sees it. The field is empty on 90 percent of leads. Fix: validate on five test clicks that the gclid lands in the CRM record.

The sat appointment event does not fire reliably. The CRM has a stage called 'sat appointment' but the sales rep forgets to mark the lead as sat half the time. The imports run against incomplete data. Fix: make the stage move happen automatically from the appointment calendar when the rep marks 'attended' or from an SMS confirmation to the rep after the appointment time passes.

The call tracking numbers are dynamic in the hero but static elsewhere. The main phone number on the 'contact' section or the footer is the business's real number, not a tracked one. Calls there do not attribute. Fix: audit every phone number on the landing page and make sure the swap script finds all of them.

Each of these is a 1 to 2 hour fix, and each one recovers signal that was already there and being lost.