Google Ads — leads in, outcomes back

A form filled inside the ad is written into Zenvox as a request to call back, and the real outcome — appointment held, quote accepted — travels back to the ad platform when you authorise it. The receptionist calls the lead back while the request is fresh, and your workspace shows which campaigns turn into appointments.

7 days, 20 answered calls, no card

Where your lead lands

The lead is written into Zenvox as a request worth qualifying: name, number, what they are after, the campaign it came from. The ad account stays yours, and nothing is written into it — receiving a lead is not managing campaigns, not creating an ad, not committing a budget. The receptionist calls while the subject is still fresh.

Access is granted through an authorisation you give from your own ad account: no key to create, no connector to program. Four tasks often travel under one name — receiving a lead, sending an outcome back, creating a campaign, launching it with a budget. Here the connection receives the lead and sends its outcome back; creating and launching a campaign carry their own authorisation and their own page.

A lead form opens inside the ad, and the person leaves a name, a number and what they need without ever leaving the search results. The trouble comes next: the form lands in an inbox and it sits there.

Sending the outcome back to Google

The outcome is written into your workspace: qualified call, appointment held, quote accepted, each attached to the click it came from. That is where it travels to the ad account from, and the account stays yours. Plug nothing in and the outcome does not disappear: it stays with you, and that is most of what an owner actually wants to know.

Zenvox sends the offline outcome to the destination you authorised, through the platform's own upload. Each upload carries the click it came from, the outcome definition, its date, and the amount with its currency, written explicitly. An outcome corrected in your workspace — amount revised, date moved — goes back as an adjustment; one that no longer holds, a contract cancelled after signature or an outcome counted twice, is withdrawn by a retraction. Each of those three moves is traced in the upload register, which stays open to you.

One rule is settled in advance: a lead and a sale are not added together as two separate revenues. And an upload accepted by the platform shows that it was received; attributing a sale to it remains an interpretation.

A platform learns from whatever you send back: send it form fills and it optimises for form fills. A midnight call about a flooded basement and a browsing question look identical in a report of form fills, and have nothing in common in an order book.

Read, create, update, cancel

The lead comes into your workspace, and that is where its outcome travels back to the platform from. Only one of the four actions touches the ad side; the other three are settled on yours, in your workspace, where the request lives until its outcome.

ActionWhat that means
ReadThe lead arrives at an address you set in your ad account, protected by a key you choose. Zenvox reads every field delivered — name, number, form answers, campaign, timestamp — and writes it into the request the moment it arrives.
CreateThe lead becomes a request in your workspace, with its campaign, its form, its timestamp and whatever consents were delivered with it, and that request is what the receptionist works from. Nothing needs creating on the ad side: an advertising platform does not hold appointments.
UpdateWhere the lead stands — called back, qualified, booked, lost — lives in your workspace, and that is where an outcome sets off from when it travels back to the platform, through the sending back described above.
CancelA withdrawal of consent and a deletion request are recorded and honoured in your workspace, with the register that goes with them, without depending on the advertising platform.

What is included, what needs an add-on

Answering the phone, qualifying and passing the request along is in your base, and advertising changes none of that. Receiving a lead that came from an ad, handing it to the right person and following it through to its outcome is the work of an acquisition add-on. Preparing and launching the campaigns themselves is something else again, and it does not switch itself on because a lead arrived.

Add-ons that work with your software

Lead capture and sales follow-up

Receives leads from the authorised sources, drops the duplicates, assigns an owner, follows up by stage, and keeps the origin attached all the way to a won or lost outcome and its reason.

My Google campaigns

Prepare and launch search campaigns from your services, your service area and your budget. Receiving a lead gives no rights at all over an ad account: they are two separate things.

The authorisation, and what holds the truth

There is no password to hand over here: the setup is done inside your own ad account, and it comes down to one address and one key.

  • You configure the form and the receiving address from your own ad account
  • A key that you choose travels with every delivery, and a delivery that arrives without the right key is refused
  • The origin is kept as delivered — campaign, form, timestamp, consents — because an outcome with no origin explains nothing
  • The same lead sent twice creates one file: a repeated delivery is recognised and makes no duplicate
  • Your ad budget stays with your ad platform; the connection does not touch it, and connecting adds no fee to your subscription
  • The ad account holds the truth for delivery; your workspace holds the truth for how the request moves along
  • For sending outcomes back, an authorised destination is named on your side and a measurable outcome is defined with you — appointment held, quote accepted, amount collected —, because an upload with no definition behind it means nothing
  • The data, account and consent rules that apply are identified before the first upload

The upload register stays open to you: every outcome sent back shows there with its date, its amount and the click it came from.

A roofer, two crews, autumn season. A search ad carries a lead form. The lead arrives while the person is still in front of their screen, and the receptionist calls back.

ReceptionistHello, I am calling you back about the roofing estimate you just asked for. Let me take your name and a callback number first, in case we get cut off.

CustomerYeah, hi. I have had a water stain on the ceiling since Saturday's storm.

ReceptionistI am logging that as an active leak. What is the address, with the postal code? And is it a sloped roof or a flat one?

ReceptionistThank you. I am marking the request as a priority and holding a slot for an estimate visit. The price of the repair comes from the roofer, once he has seen the roof.

The request reaches the owner with the campaign it came from, the address, the roof type and the active leak flagged. Nothing is written on the ad side, because there is nothing there to write to.

If the connection is not there

Without the connection, none of the receptionist's work is lost: the only thing that changes is the road the lead takes to get to you.

  • The calls that the same ad produces are answered, qualified and passed along as usual
  • The form on your own site drops the request straight into your workspace, with its origin
  • A lead that reaches you by email can be entered by hand without losing its timestamp or its campaign
  • Switching receiving on later changes neither your setup nor your budget
  • Without sending back, your workspace shows by source how many requests became appointments and then contracts, with the reason for a loss, and an export lets you reconcile those outcomes against your advertising reports

Questions about this connection

Does Zenvox manage my campaigns?

No: receiving a lead is not managing campaigns, not creating an ad, not committing a budget. The ad account stays yours, and nothing is written into it.

How does the lead arrive?

At an address you set in your own ad account, protected by a key you choose; a delivery that arrives without the right key is refused. Every field delivered is written into the request, with the campaign it came from and its timestamp.

What if the same lead arrives twice?

It creates one file: a repeated delivery is recognised and makes no duplicate. The origin is kept as delivered — campaign, form, timestamp, consents — because an outcome with no origin explains nothing.

Does connecting cost extra?

Your ad budget stays with your ad platform, the connection does not touch it, and connecting adds no fee to your subscription.

Will sending my outcomes back lower my cost per acquisition?

The platform learns from what you send back: appointments held and quotes accepted rather than form fills. The effect on your cost per acquisition depends on your campaigns, and an accepted upload shows it was received, not that a sale is attributed to it.

What if a contract is cancelled after signature?

The outcome is withdrawn from the platform by a retraction, and the upload register keeps a trace of it. One rule is settled in advance: a lead and a sale are not added together as two separate revenues.

What about a withdrawal of consent?

It is recorded and honoured in your workspace, with the register that goes with it, without depending on the ad platform.

Where to next

See what sales follow-up does with the lead, how campaigns get prepared, or open the full software list.

Google Ads — leads in, outcomes back

A form filled inside the ad is written into Zenvox as a request to call back, and the real outcome — appointment held, quote accepted — travels back to the ad platform when you authorise it. The receptionist calls the lead back while the request is fresh, and your workspace shows which campaigns turn into appointments.

Start your free trial7 days, 20 answered calls, no card