From inquiry or booking to the confirmed sale.
Keep the click connected from the first contact or the booking to the confirmed sale.
See this use caseConfirmed sale feedback for Google Ads
Apointoo keeps the Google Ads click connected to the lead through forms, WhatsApp, and booking flows, then sends the confirmed sale value and currency back to Google Ads. Correct the value or retract a refunded sale when the outcome changes.
Free self-service workspace. Demo requests are reviewed within 48 hours.
ILLUSTRATIVE PRODUCT FLOW — NOT CUSTOMER PROOF
From the ad to the confirmed sale
A lead event tells Google Ads that someone raised a hand. The journey may continue through a form, WhatsApp, or a booking flow, and the business confirms the sale later. Until those records stay connected, Google Ads does not receive the confirmed buyer outcome.
A lead event says someone raised a hand. That is all that arrives.
The journey may pass through a form, WhatsApp, or a booking flow before the sale happens.
Until click and sale stay joined, Google Ads does not receive the confirmed buyer.
A lead is not a sale.
The mechanism
From the click to the corrected sale, in one connected record.
A snippet in your frontend stores the ad identifier at the moment the lead arrives. No consent means no send.
Form, WhatsApp, booking: the click stays attached to the lead at every step.
When the business confirms the sale, value and currency enter the same record as the click.
The confirmed sale returns to Google Ads as a conversion. The campaign can learn from buyers, not only from form fills.
Value changed: correct it. Sale refunded: retract the conversion within the 55-day window.
Boundaries
For whom
Keep the click connected from the first contact or the booking to the confirmed sale.
See this use caseConfirmed sales per campaign, from the click to the real outcome.
See this use caseKeep leads connected until the business confirms the result.
See this use caseThese lines describe supported journeys, not customer results.
Adjacent offers
Reserve with Google publishes merchant booking links into Google. Booking chat supports booking conversations. Both are shipped offers; neither is a step in the Google Ads return loop.
Publishes merchant booking links into Google.
See ReserveSupports booking conversations.
See the chatDeveloper tools
JavaScript snippet to capture the click in web journeys. WordPress plugin to capture in WordPress. TypeScript SDK to build custom booking and intake flows. Every path follows the same consent rule: no consent, no send.
“The click promises. The sale proves.”
Capture once. Confirm the sale. Send the outcome to Google Ads. Meta return is next — not available today.
Create a free self-service workspace. For assisted or custom evaluation, request a demo. Requests are reviewed within 48 hours.
03
The confirmed sale returns to Google Ads as a conversion.
See the Google Ads integrationThe sale teaches the ad.
For assisted evaluation, deployment, or a custom scenario: describe your case. We review within 48 hours and reply by email.