Skip to content
Proofbell

Connecting Google Ads

Connecting Google Ads does two things: it lets us read the campaign and keyword behind each click, and it lets us send back what the resulting call was worth.

The second is what changes your results. Smart Bidding optimises towards whatever you tell it a conversion is — so telling it "a call happened" produces more calls, while telling it "this call became £14,000" produces more revenue.

Where this stands today. Connecting, choosing the account and creating the conversion action all work against real Google Ads accounts, and Google has accepted our conversions in its validate-only mode, which checks everything and records nothing. No conversion has yet been counted in a live account. That is why the Connections card says Partly working: the first real one is the step that changes it.

Connecting: four steps

Go to Connections, find the Google Ads card under Advertising, and press Connect. That opens the Google Ads page, which lists the four steps in order. Each shows a tick when it is done, a dashed number when it is the one to do now, and a red mark when it needs attention. The chip at the top of the page sums them up: Not connected, Not finished, Dry run, Sending or Needs attention.

  1. Google sign-in. Press Connect Google Ads. Google asks you to sign in and approve access on its own site — that is what makes it a genuine consent screen, and it is the one point where the product hands you off deliberately. You come back to the same page with the result at the top. Afterwards the step says when it was connected and by which of your Proofbell users, and shows the permissions Google granted. It does not show which Google login was used, because Proofbell does not ask Google who you are. A connection made before Proofbell began recording these says so, and reconnecting records them.
  2. Advertiser account. Choose from the accounts your Google login can reach. Each shows its customer ID, currency and time zone, which is what tells two similar names apart.
  3. Conversion action. Choose or create one — see below, this is the step to get right. Once chosen, the step names it and says whether Google will keep the value we send.
  4. Sending. Unlocked once the first three are done, and it starts in dry run: see Dry run comes first.

What we ask permission for

Two scopes, and nothing else:

  • Read your reporting — clicks, campaigns, keywords.
  • Upload conversions — the revenue a call produced.

We never change budgets, bids, creatives, targeting or campaign settings, and we never read your billing details. If you use a manager (MCC) account, connect with a login that has access to the client account you want tracked.

The conversion action

This is where uploads silently fail if it is wrong. Google will accept data against the wrong kind of action and then ignore it.

In Google Ads: Goals → Conversions → New conversion action → Import → Manual import using API or uploads. Not a website conversion, not a phone-call-from-ads conversion — those measure something Google observes itself, and cannot receive values from us.

Proofbell can create a correctly configured one for you during setup, which is the safer route. If you create it yourself, set the category to a lead type and leave "use the default value" off — the whole point is that each conversion carries its own value.

A brand-new conversion action takes time to become usable. Google needs minutes to hours to propagate it, and until then uploads are rejected with an error that looks permanent but is not. Proofbell retries automatically — you do not need to do anything except not panic at the first failure.

Dry run comes first, and stays until you switch it live

A new connection starts in dry run. Conversions are built and validated against Google's API, and the response is recorded, but nothing is written to your bidding data.

That is the default for a reason worth stating plainly:

  • A wrong value column in a CSV pushes fabricated revenue into a live algorithm.
  • A wrong currency assumption misstates every deal by the exchange rate.
  • Neither can be undone by deleting rows afterwards, because Smart Bidding has already learned from them.

So: import a batch, check the numbers on the attribution screen against your own CRM, and press See what would be sent in step 4 of the Google Ads page. It lists the latest 25 conversions prepared for Google: when the call or sale happened, the campaign behind the click where Google has told us it, the value, and what happened — checked, not recorded in dry run, recorded by Google once sending, or skipped, refused, retrying or given up with the reason. A value reads hidden if your role cannot see revenue. Opening the list sends nothing. Conversion delivery on Connections counts the same outcomes for every destination.

When you are satisfied, press Start sending for real in the same step. You are asked to confirm, because from that point Smart Bidding learns from what is sent. Stop sending in the same place turns it off again at once; anything already sent stays in the account.

The switch only appears once an advertiser account and a conversion action are chosen, and it will not turn on while the connection is missing Google's permission to upload, or while Google no longer accepts the sign-in (see below): a live switch on a connection that cannot send would only hide the problem, so the step says what is missing instead. The Connections card reads Dry run until you switch it, and Connected after; the Google Ads page's chip reads Sending.

What actually gets sent

Deliberately minimal:

  • the click identifier Google gave us when the visitor arrived
  • the conversion value and currency
  • when it happened
  • the visitor's consent for ad user data and ad personalisation, as they recorded it: given, refused, or unspecified if they made no decision

A caller's phone number is never sent to Google, in full or hashed, and neither is a recording, a name or an email. Google already knows which click it issued; it does not need to know who rang. There is no setting that changes this.

Google does offer a call-based upload method, which matches a conversion on the caller's number and the time of the call instead of on the click. We do not use it, and it could not work for you anyway: Google matches it only against calls it tracked itself, through its own forwarding numbers, so it cannot find calls to your Proofbell numbers.

Consent, and strict consent

A visitor who refused ad storage or ad user data is never uploaded, whatever your settings, including one who refused after the call: the check is made when the conversion is sent. With strict consent switched on for the website, a conversion is also withheld while no decision is recorded for that visitor; with it off, which is the default, that visitor's conversion is uploaded and Google is told their consent is unspecified. Instructing us to upload is instructing a transfer of your customer's data to a third party, and you need a lawful basis for it — the setting exists so the platform can help you honour that rather than quietly ignoring it. The switch is under Account settings → Setup → Consent, one per website. More on how each platform is treated is under Connections.

"Not finished"

We hold valid credentials but no advertiser account or conversion action has been chosen, so nothing can be uploaded. It is called out because most tools show a green tick for this state and then push nothing for weeks. The card on Connections says Not finished and its button reads Finish setup. The Google Ads page's chip says the same, and the outstanding step carries the dashed number with its list already open.

Reconnecting

Safe at any time, and sometimes necessary — Google expires access if a password changes or permissions are revoked. Reconnecting keeps your existing settings: the advertiser account, timezone and conversion action all survive, and only the credentials are replaced. That also means reconnecting is not the way to use a different account.

Choosing a different account

If you picked the wrong advertiser account, or the business has moved to another one, press Choose a different account in step 2 of the Google Ads page. The list of accounts opens in the step with the one in use marked, and nothing changes until you pick another. When you do, you are asked to confirm, because from that moment:

  • Proofbell stops sending to the old account.
  • The connection goes back to dry run, even if it was sending for real, so the new account receives nothing real until you switch it on again yourself.
  • The conversion action is forgotten too, because it belongs to the old account. You choose or create one in the new account.
  • Conversions that were waiting to be sent to the old account are not sent, to it or to the new one: they were meant for the old account's bidding. They stay listed under Conversion delivery with that reason. Calls that convert from now on go to the new account.

Your Google permission is kept, so no new sign-in is needed. Nothing already sent is withdrawn: it stays in the old account, which has already learned from it. If Google cannot be asked for the list, the step says why and the account in use stays as it is.

Disconnecting

Disconnect Google Ads, under Stop tracking Google Ads beside the steps on the Google Ads page (below them on a phone), stops Proofbell using Google Ads altogether. After you confirm:

  • Proofbell asks Google to remove its access to your Google Ads, so it no longer appears under third-party access in your Google account. The page tells you if Google could not be reached; you can remove it yourself at myaccount.google.com/permissions.
  • The stored permission is deleted, and the advertiser account and conversion action are forgotten.
  • Nothing more is sent, including conversions that were waiting to be sent.
  • Connecting again later starts fresh: you choose the account and conversion action again, and it starts in dry run.

Conversions already sent stay in Google Ads. Disconnecting does not withdraw them, and Google has already used them for bidding.

If you manage several accounts in Proofbell. Google removes access for every connection made with the same Google login at once. So while another of your Proofbell accounts still has Google Ads connected, disconnecting one of them removes Proofbell's copy of the permission but does not ask Google to remove access, which would stop the others too. The page says when that has happened; remove Proofbell at myaccount.google.com/permissions once none of your accounts need it.

"Needs reconnecting"

Google's consent screen lets you untick individual permissions and still finish. If the one that lets us upload conversions was unticked, the connection works for reading your campaigns and cannot send a single conversion. The card says Needs reconnecting in red. On the Google Ads page the chip says Needs attention, step 1 carries the red mark and says why, and its button becomes the orange Reconnect. Press it and leave every permission ticked; your settings are kept. The permission chips in step 1 show what Google granted, so a missing Data Manager is visible at a glance.

The same red step appears when Google no longer accepts the sign-in at all — the Google password changed, or Proofbell's access was removed in your Google account. The page learns that only by asking Google, so it can turn red a moment after it loads. Sending stays locked until you reconnect.

If the page says Google Ads could not be read

That message comes from Google refusing the request, and it says which of three things happened: the permission was revoked (reconnect), the login lost access to the account (reconnect with one that has it), or something on our side needs fixing, in which case the message says so and there is nothing for you to do but tell us.

Timezones, and why we ask

We store your Google Ads account's own reporting timezone, because Google's click data is bucketed by date in that timezone. Using ours instead would query the wrong day for any click near midnight and return nothing — which looks identical to a click Google filtered as invalid. Discovery captures it automatically.

Microsoft, Meta and others

Microsoft Advertising, Meta, LinkedIn and Google Analytics 4 each have their own connection, and each is at a different stage. Connections says what works today for every one of them, including the limits that matter most: Meta accepts a conversion for only six days after the call, and GA4 for only 72 hours.

Next Connecting Xero