HubSpot
Closed deals come back as conversions the ad account can bid on.
HubSpot runs the pipeline; Apointoo teaches the ads. Deal-stage changes flow into Apointoo, map onto canonical events, and travel to your advertising platforms with the original click attached.
Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.
The pipeline knows. The ad account never hears.
By the time a deal reaches Closed won, the original ad click is weeks old and forgotten. HubSpot reports the pipeline; Google Ads still optimizes on the form fill.
Stages you choose become events; delivery status writes back
You map HubSpot stages to Apointoo events once. Marketing-qualified becomes qualified_lead, Closed won becomes sale_paid, reversals retract. Apointoo writes apointo_last_event and delivery status back to the contact, so RevOps can audit without leaving HubSpot.
What it sends to Google Ads
How the data flows
- HubSpot contact or deal changes
- Webhook reaches Apointoo
- Stage mapping turns it into an Apointoo event
- Event matched to the original ad click
- Outcome sent to Google Ads, Meta, LinkedIn
How the connection works
Authorize HubSpot with read scopes for contacts and deals only.
Pick the pipeline and map its stages to Apointoo events.
Connect at least one advertising destination.
Attribution comes from Apointoo Capture or from HubSpot contact properties.
Delivery results write back as apointo_* properties on the contact.
What it reads
Event mapping
| From | Apointoo |
|---|---|
| New contact | lead_created |
| Marketing-qualified stage | qualified_lead |
| Appointment stage | appointment_booked |
| Closed won | sale_paid |
| Reversed or reopened deal | refund_retraction / correction |
Frequently asked questions
Closed deals come back as conversions the ad account can bid on.