Lead capture and sales follow-up
Keeps the origin of a lead attached all the way to a won or lost outcome and its reason, and measures performance by source. This is the add-on that has something to send back in the first place.
Google — sending business outcomes back
The real outcome — appointment held, quote accepted — is written into your workspace, then sent back to the ad platform. An accepted upload is no proof of a sale.
7 days, 20 answered calls, no card
Where the outcome advertising receives is written
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.
One serious caution, written in plain words in the research: the fact that the platform accepted an upload does not demonstrate that a sale can be attributed to it. Acceptance is technical; attribution is an interpretation. This page therefore promises no drop in your cost per acquisition. The authorisation is granted from your own ad account, with no key to create and no connector to program.
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
Here the reading happens on your side: your workspace is what knows whether the quote was accepted. The other three actions point at the ad platform, and their status is that of documentation that was read without an access being installed.
| Action | Status | What that means |
|---|---|---|
| Read | Zenvox native mode | The outcome is read in your workspace, which holds the truth: request qualified, appointment held, quote accepted, amount collected. The advertising platform does not hold your commercial outcome and cannot report it back to you. |
| Create | To qualify | Sending an offline outcome is documented by the vendor. What still has to be established before anything is built: access to the destination, the exact authentication method, and the change dated 15 June 2026 that affects the older upload route. |
| Update | To qualify | The route for adjusting an outcome that was already sent — correcting an amount, shifting a date — was not verified during this review. Until it is, a corrected outcome stays accurate in your workspace and is not pushed anywhere. |
| Cancel | To qualify | The retraction route was not verified either, and the case comes up often enough to matter: a contract cancelled after signature, or the same outcome counted twice. One rule is settled in advance — a lead and a sale are not added together as two separate revenues. |
What is included, what needs an add-on
Your base answers, qualifies, books and passes the request along: it already produces the outcome this page is about. Tying that outcome back to where it came from, and then sending it to an ad platform, belongs to the acquisition add-on. Running the campaigns is a further job again, with its own rights.
The authorisation, and what holds the truth
Sending outcomes back touches data about real people and an advertising account. Five points are worth settling before the first line of code.
- An authorised account and a destination are named on your side, and the exact authentication method is established from the official setup guide before anything is built
- A measurable outcome is defined with you — appointment held, quote accepted, amount collected — because an upload with no definition behind it means nothing
- A currency is written explicitly alongside every amount sent
- Your workspace holds the truth for the outcome; the platform holds the truth for delivery and for whatever it decides to attribute
- The data, account and consent rules that apply are identified before activation, and the register of what was sent stays open to you
No promise of return comes with this connection: commissioning it, reconciling it and watching it are real work, and an accepted upload does not demonstrate an attributed sale.
A plumber. The call comes in from a search ad, the quote goes out the next morning, and the customer signs three weeks later. The outcome is read in the workspace; sending it back is still to be qualified.
CustomerHi, my water heater is leaking in the basement.
ReceptionistLet me take your name and a callback number first. Is the water running right now, or is it seeping?
CustomerSeeping, but it has got worse over the last couple of days.
ReceptionistUnderstood. I am noting the address and the age of the unit if you know it, and holding a visit. The plumber confirms the amount on site — I do not quote one over the phone.
The request keeps its origin the whole way through. When the owner marks the quote accepted in the app, that outcome — dated, valued, attached to the right lead — is what is ready to travel back to the platform the day the upload is qualified.
If the connection is not there
Without the outcome upload, your measurement does not disappear: it stays with you, and that is most of what an owner actually wants to know.
- Your workspace shows, by source, how many requests became appointments and then contracts
- The reason for a loss is kept, because the reason is what explains a bad month
- An export lets you reconcile those outcomes against your advertising reports by hand
- The day the upload is qualified, it is added on top without changing how you mark a file won
Questions about this connection
Will sending my outcomes back lower my cost per acquisition?
This page promises no such thing. The fact that the platform accepted an upload does not demonstrate that a sale can be attributed to it: acceptance is technical, attribution is an interpretation.
Where is the outcome written?
In your workspace, which holds the truth: request qualified, appointment held, quote accepted, amount collected, each attached to the click it came from. The ad platform does not hold your commercial outcome and cannot report it back to you.
What still has to be established before the upload is built?
Access to the destination, the exact authentication method, and the change dated 15 June 2026 that affects the older upload route. Until that is done, a corrected outcome stays accurate in your workspace and is not pushed anywhere.
What if a contract is cancelled after signature?
The retraction route was not verified, and the case comes up often enough to matter. One rule is settled in advance: a lead and a sale are not added together as two separate revenues.
If I plug nothing in, do I lose my measurement?
No, it stays with you. Your workspace shows, by source, how many requests became appointments and then contracts, the reason for a loss is kept, and an export lets you reconcile those outcomes against your advertising reports.
Where to next
See where the lead comes from, what sales follow-up does with it, or open the full software list.
Google — sending business outcomes back