apointoo.
Integrations
CRMPlannedSource + writeback

HubSpot

Closed deals come back as conversions the ad account can bid on.

HubSpot runs the pipeline; Apointo teaches the ads. Deal-stage changes flow into Apointo, 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 Apointo events once. Marketing-qualified becomes qualified_lead, Closed won becomes sale_paid, reversals retract. Apointo writes apointo_last_event and delivery status back to the contact, so RevOps can audit without leaving HubSpot.

What it sends to Google Ads
lead_createdqualified_leadappointment_bookedsale_paidrefund_retraction
How the data flows
  1. 01HubSpot contact or deal changes
  2. 02Webhook reaches Apointo
  3. 03Stage mapping turns it into an Apointo event
  4. 04Event matched to the original ad click
  5. 05Outcome sent to Google Ads, Meta, LinkedIn
How the connection works
01

Authorize HubSpot with read scopes for contacts and deals only.

02

Pick the pipeline and map its stages to Apointo events.

03

Connect at least one advertising destination.

04

Attribution comes from Apointo Capture or from HubSpot contact properties.

05

Delivery results write back as apointo_* properties on the contact.

What it reads
contact.creationdeal.creationdeal property changes (stage, amount)
Event mapping
FromApointo
New contactlead_created
Marketing-qualified stagequalified_lead
Appointment stageappointment_booked
Closed wonsale_paid
Reversed or reopened dealrefund_retraction / correction
Frequently asked questions
Does Apointo replace HubSpot?

No. HubSpot keeps the full customer record. Apointo receives stage changes and returns delivery proof.

Which stages become conversions?

Any stages you map. There is no forced lifecycle model; the mapping is yours.

What exactly gets written back?

apointo_last_event, apointo_last_sent_at, apointo_delivery_status, apointo_destination, and apointo_error_code. Nothing else.