All connections
Proofbell connects to two different kinds of system, and the difference matters more than the logos. Ad platforms receive call revenue from Proofbell, so their bidding can optimise on it. CRMs supply revenue to Proofbell, so there is something to send. Until revenue reaches Proofbell — from a CRM, a CSV import or the API — an ad platform has nothing to optimise on.
What is connectable today
| Platform | Direction | How you connect | State |
|---|---|---|---|
| Google Ads | Receives revenue | Google sign-in, then choose the advertiser account and conversion action | Partly working — everything up to sending works against real accounts, and Google has accepted our conversions in validate-only mode; none has yet been counted in a live account. Full guide |
| Microsoft Advertising | Receives revenue | Microsoft sign-in, then choose the account and conversion goal | Partly working — proven end to end against Microsoft's test environment, not yet against a live account |
| Meta | Receives revenue | A system user token for your own ad account, or Facebook Login for Business | Partly working — works for an ad account your own business owns. A client's ad account needs Meta to approve our app first. Conversions are accepted for six days after the call. |
| Google Analytics 4 | Receives calls as events | Measurement ID and API secret, pasted — no Google sign-in | Partly working — connectable today; Google cannot confirm delivery, so you check it in Realtime |
| HubSpot | Supplies revenue | HubSpot sign-in, then closed deals are matched to calls; a deal updates its call's conversion rather than adding one | Partly working — a sync shows which deals would match, but does not yet write their values, and the app installs only in portals we have added. Use a CSV import for now; imported deals appear under Sales, and HubSpot's own will too once the sync records them. |
| Slack | Receives alerts | Slack sign-in by someone who can install an app in your workspace | Not yet for your workspace — Slack has not approved our app for other workspaces. Alert rules can post to a Slack webhook URL meanwhile. How alerts use it |
| LinkedIn Ads | Receives revenue | LinkedIn sign-in, then choose the ad account and conversion rule | Partly working — LinkedIn has no phone identifier, and we send no email address, so a call reaches LinkedIn only when the visitor arrived by clicking a LinkedIn ad |
| Salesforce | Supplies revenue | — | Not started |
| Xero | Supplies quotes (shown in Proofbell only) and paid-invoice revenue | Xero sign-in, then choose which organisation's quotes and invoices we read | Partly working — built, but not yet run against a real Xero organisation. How it matches quotes and invoices to calls |
Finding your way around the Connections screen
Connections in your dashboard is a grid of cards grouped under Advertising, CRM, Analytics, Finance and Notifications. Each card carries the platform's mark, one line on what connecting it achieves, and a status chip:
- Connected — it is set up and doing its job.
- Dry run — set up, and deliberately sending nothing real yet. Switch it live on the connection's own page when you are happy with what it would send.
- Not finished — you signed in, but something it needs is still unchosen: an advertiser account, a conversion action, a dataset. Nothing is being sent yet.
- Needs reconnecting or Expired — the connection has stopped, or cannot send. The card says why in a sentence, and the button reads Reconnect.
- Not connected — available, and nobody has connected it.
- Needs keys — we have not finished setting this platform up on our side. There is nothing for you to do; tell us if you want it.
- Coming soon — designed, not built. The card says so rather than hiding.
Connect opens that platform's own page, where everything for it lives — signing in, choosing the account (and, for Google Ads and Microsoft Advertising, choosing a different one later), turning dry run off, and disconnecting. Once it is connected the same button reads Settings and goes to the same place, so there is one page per connection and you do not have to remember which of two screens a setting was on.
Platforms that need you to sign in — Google Ads, Microsoft Advertising, Meta, LinkedIn, HubSpot, Xero and Slack — hand you to the platform's own site to approve access, and then hand you straight back to that connection's page in the dashboard with the result at the top of it: connected, or the reason it did not finish. If you cancel on the platform, or it refuses, you are returned the same way and told why in the platform's own words. Nothing is left on a screen somewhere else for you to find your way back from.
Each card states its own readiness, and it and this page are meant to agree — if they ever disagree, the dashboard is right and this page is out of date. Under a card, What works today, and what does not opens the platform's own limits in full.
Connections that expire
Meta and LinkedIn give a connection made by signing in a lease of about sixty days, with no way for us to renew it. The connection's page shows the date it runs until, and from fourteen days before it the card on Connections says so too. After that date it reads Expired, nothing is sent, and waiting conversions are held rather than thrown away — but Meta only accepts a conversion for six days, so a lapse longer than that loses the ones that age out. Reconnecting keeps the account and dataset you chose.
Choosing a different account, and disconnecting
Reconnecting keeps the account you chose, so it is not how you move to a different one. On the Google Ads and Microsoft Advertising pages, Choose a different account sits beside the chosen account's name. On Microsoft's it asks first, then shows the list of accounts again without another sign-in; on Google's it opens the list first and asks when you pick one. Either way it stops sending to the old account, forgets the account and its conversion action or goal, and puts the connection back in dry run even if it was sending for real. Conversions that were waiting to be sent to the old account are not sent anywhere, and say so under Conversion delivery.
Disconnect on any connection's page stops it altogether. For Google Ads and Microsoft Advertising that includes anything still waiting to be sent, and connecting again later starts in dry run with nothing chosen. Google Ads also asks Google to remove Proofbell's access; the Google Ads guide says when it does not. Neither action withdraws a conversion already sent: the platform has it, and has already used it.
Connecting Google Analytics 4
GA4 is the only destination needing no Google sign-in, because the credentials belong to your property rather than to us. Both values come from GA4 under Admin → Data streams → your web stream:
-
The measurement ID, which looks like
G-ABCDEFGHIJ. It is on the stream itself. Take care not to paste the property ID, which is a plain number. - A Measurement Protocol API secret, under Measurement Protocol API secrets on the same screen. You create it once.
Calls arrive as a generate_lead event by default, which is what Google Ads
expects when importing a lead from GA4. Collection goes via the EU endpoint unless you turn
that off.
Two things about GA4 that catch people out
GA4 cannot tell us your credentials are wrong. Its collection endpoint answers success for any measurement ID and any secret, and its validation endpoint ignores both — a deliberately made-up ID validates exactly like a real one. There is no request we can make, ever, that distinguishes a working pair from a typo. So check it yourself, twice:
-
Before going live, press Send a test event on the
GA4 page, then open Admin → DebugView in
GA4. An event named
proofbell_testshould appear within a minute. DebugView events stay out of your reports, so this adds no fake lead. If it does not appear, the measurement ID or the secret is wrong. -
After going live, when the next tracked call qualifies, open Reports → Realtime
and look for
generate_lead(or the event name you chose).
GA4 only accepts an event for 72 hours after the call. That is far shorter than the ad platforms allow, and it is the reason a CSV of last month's revenue can reach Google Ads and miss GA4 entirely. If GA4 matters to you, get revenue in sooner.
Connecting Meta
Meta has two routes, and which one you need depends on who owns the ad account.
- An ad account your own business owns: use Connect with a system user
token instead on the Meta page. In Meta's Business
Settings, create a system user, assign it the ad account and the dataset, and generate a token
with
ads_managementandbusiness_management. It does not expire. This is the route that works today. - A client's ad account: Connect Meta signs in with Facebook Login for Business. Meta only lets our app reach another business's ad account once it has approved the app (App Review), which has not happened yet — until it does, this route reaches only accounts belonging to the business that owns the app.
Then choose the ad account and the dataset. Both are needed: Meta posts offline conversions to a dataset, and a dataset is a separate asset from the ad account.
Three things about Meta to know before you switch it live
Six days. Meta accepts a conversion for six days after the call. Google and Microsoft allow ninety. A deal that closes later than that is never sent to Meta, so Meta suits businesses whose calls turn into money quickly.
No corrections. Meta has no way to correct or withdraw a conversion. If a deal's value changes or it is lost, Meta keeps the first figure it was sent.
No confirmation of a match. What we send Meta to match on is the ad click, where the visitor arrived from one. Meta reports that it received each conversion, never whether it found the person. Expect a match rate, not a complete picture. Meta is never sent the caller's phone number or an email address.
Consent: who is sent, and what each platform is told
Every conversion is checked against the consent your website's visitors gave, as we recorded it (see Install for how it is recorded). The check happens at the moment the conversion is sent, not when the call happened, so a visitor who withdraws consent in between is not sent. The visitor that counts is the one whose browser was shown the tracking number: the visit the conversion's ad click came from. A call with no web visit behind it has no decision recorded.
- Refused. A visitor who refused ad storage or ad user data is sent to no ad platform, on any setting. For GA4, refusing analytics storage has the same effect. The conversion is shown as skipped with the reason and is not tried again. A conversion already sent before the refusal stays with the platform: none of them can delete one, and withdrawing it would mean sending the visitor's click identifier again.
- No decision recorded. With strict consent on, withheld. With it off, sent with the ad click identifier.
- Consented. Sent with the ad click identifier, the same as above.
A caller's phone number is never sent to any advertising platform, in full or hashed, and neither is an email address, whatever the visitor chose and whatever your settings. There is no setting that changes this. Your own systems are different: a webhook or a warehouse export can include the caller's number, because it goes to you.
Strict consent is a setting on each website, under Account settings → Setup → Consent. It is off unless you switch it on. Off by default because, on a website with no consent banner, nobody has made a decision, so strict consent would withhold nearly every conversion and leave your ad platforms nothing to bid on. Switch it on if your banner is on every page and you rely on visitors' consent to send their conversions. It applies to conversions sent after the change; one already withheld is not sent later. Changing it needs a role that can manage connections as well as the website, and each change is recorded in the audit log.
What each platform is told about that consent:
- Google Ads is told the visitor's recorded answer for ad user data and ad personalisation separately: given, refused, or unspecified where there is no decision. It is never told consent was given unless the visitor gave it.
- GA4 is told the same where the visitor decided, and nothing where they did not, in which case GA4 uses what it saw on your website for that visitor.
- Meta, Microsoft Advertising and LinkedIn have no consent field in the way we send conversions to them, so nothing is stated. The rules above decide whether they are sent anything at all.
Dry run, and why every connection starts in it
A new connection sends nothing. It records what it would send, so you can look at the push history before anything reaches a live account. Turning dry run off is a separate, deliberate action on that connection's own page: Start sending for real on Google Ads and LinkedIn, Start sending to Meta on Meta, and Start sending to GA4 on GA4. Each asks you to confirm, and each refuses while the connection could not send anything — no account, dataset or conversion action chosen, a permission missing, or an expired connection — and says which. Stopping is never refused.
This is not caution for its own sake: a conversion upload cannot be retracted. Once a platform has a conversion with a value attached, it is in that account's bidding history. Sending a test figure to a real ad account is a thing you cannot undo, so the product makes it a decision rather than a default.
Checking that conversions are actually arriving
The Conversion delivery panel on the connections page shows what happened to every conversion we sent, per platform, over the last 30 days. It is the answer to "is Google actually receiving these", and it is worth a look after you turn dry run off.
Most of what you see there is normal. Skipped means we did not send a conversion because the call carried nothing that platform could match it to — no click id, no usable identifier — which is ordinary for calls from people who did not arrive from an advert. Refused means the platform rejected it, and sending the same thing again would be refused again. Retrying and waiting both mean it is still in progress.
Given up is the one to tell us about. It means a conversion failed enough times that nothing will try again, so the platform never received it — and unlike the others, it will not resolve on its own. The panel shows the most recent reason underneath, and sending us that line is usually enough for us to say what happened.
A waiting figure with an old date beside it is the other thing worth mentioning: a queue that is moving has recent items, and one that has stalled has items from last week.
How many platforms your plan includes
The number of connected ad platforms is capped by plan; the cap and its exact wording are on What each plan includes. Reconnecting a platform you already have never counts as a new one, so fixing an expired token cannot be blocked by the cap.
What about BigQuery, Snowflake or Redshift?
Those are not connections in this sense — we hold no credential for your warehouse and there is no sign-in button. Your warehouse fetches from us. See Warehouse sync.