CRM integrations
Turn sales-pipeline stage changes into Meta CAPI conversions. The same model works for Salesforce, HubSpot, Zoho and Pipedrive.
How it works
Your sales team works deals through pipeline stages in the CRM. AdsPing watches for stage changes and, when a deal reaches a stage you've mapped, sends the configured event (e.g. Purchase or Lead) to Meta's Conversions API with the deal contact's email/phone. Meta's bidder learns which clicks became real revenue — even when the sale closes days later, offline.
Every emit waits a 60-second debounce so an accidental drag-and-drop never fires a conversion, and is de-duplicated against Meta's pixel events so you never double-count.
Setup flow
The flow is the same across every CRM:
- Connect — open your pixel → Integrations → choose your CRM → Connect. You authorize AdsPing with OAuth in your own CRM account.
- Pick a pipeline — choose the sales pipeline where your Meta leads land.
- Map stages — map each stage to a Meta CAPI event (e.g. Closed Won → Purchase). Set a value, or use the deal's own amount.
- (Salesforce only) install the app — Salesforce has no built-in webhook, so a one-click managed package install lets it send stage changes to AdsPing. The other CRMs need no extra step.
Supported CRMs
- Salesforce — Opportunity stages → CAPI. Production + sandbox. One-click app install.
- HubSpot — Deal stages → CAPI. App-level webhook, no extra setup after connect.
- Zoho CRM — Deal stages → CAPI. Works across all Zoho data centers (US, EU, IN, AU, JP, CN, CA, SA, UK).
- Pipedrive — Deal stages → CAPI.
Match quality (EMQ)
Each forwarded event carries whatever contact data the deal has — email, phone and name. AdsPing shows an estimated Event Match Quality score (0–7) per event so you can see how well Meta will match it. To get the highest score, make sure your CRM deals have a contact with an email and phone attached.