HubSpot Conversion Leads

Connect HubSpot CRM to Meta Conversion Leads through SignalSight — authenticate your account, map contact stages, create a tracker, and stream funnel events back to Meta.

In This Page

SignalSight Conversion Lead streams contact-stage updates from HubSpot CRM to Meta in real time. When a lead moves through your pipeline — qualified, junk, won, or lost — those events flow back to Meta so campaigns optimize toward meaningful outcomes instead of raw form submissions.

Before you start

You need a SignalSight account and a Meta CRM Pixel set up in Events Manager. For Pixel ID and access token steps, see Meta (Facebook) CAPI Setup. New users can start with Account Creation.

Get Started

Your HubSpot account should have up-to-date contact data from the last 7 days before you begin. SignalSight reads contact stage changes from HubSpot — if contacts haven't moved through your pipeline recently, there won't be events to send during setup.

HubSpot CRM contacts list with recent contact records

After logging in to SignalSight, open the Tracker Creation Wizard under Signal in the left menu and follow the steps below.

Create a Tracker

Step 1 — HubSpot Source

  1. Select HubSpot CRM from the source list and give the source a name.
  2. Click Connect with HubSpot and sign in to your HubSpot account.
  3. Choose the HubSpot account you want to connect, then proceed to CRM source mapping.
HubSpot account selection during SignalSight OAuth connection

On the mapping screen, match your HubSpot contact fields to the SignalSight fields. The Event Name Prefix field controls how events are labeled when sent to Meta — for example, a Qualified stage becomes CRMContacts-Qualified and a Junk stage becomes CRMContacts-Junk. You can leave the prefix blank or enter a custom value.

Click Save and Next to continue to destination setup.

Step 2 — Meta CAPI Destination

Create a Meta Conversions API destination. You can enter your CRM Pixel ID and access token manually, or use Connect Facebook CAPI to sign in and select the Pixel from your account.

Note

The Pixel must be a CRM Pixel — not your website Pixel. In Events Manager, click Connect Data Sources, select CRM, then Connect. Create a new dedicated Pixel (recommended) so CRM events stay separate from your web Pixel.

Step 3 — Name and Complete

Name your tracker, review the source and destination summary, and finish the wizard. The tracker detail screen shows your connected HubSpot source and Meta CAPI destination.

Manage Your Source

Open your tracker at any time to update field mapping, review event history, or change the event name prefix. Use Edit Mapping on the HubSpot source to adjust both the field mapping and the CRMContacts prefix that precedes your event names.

What Happens Next

Once CRM events start flowing, complete the funnel setup in Meta Events Manager. The three guides below cover everything after tracker creation:

Frequently Asked Questions

Why does HubSpot need recent contact data before setup?

SignalSight sends events when contact stages change in HubSpot. If your CRM has no recent activity, there are no events to validate during Meta's integration review. Make sure contacts have moved through at least a few pipeline stages in the past 7 days.

What is the Event Name Prefix?

It prepends a label to every event sent to Meta. With the default CRMContacts prefix, a Qualified stage becomes CRMContacts-Qualified. You can customize or clear the prefix during source setup or later via Edit Mapping on the tracker detail screen.

Can I use my website Pixel for Conversion Leads?

No. You need a dedicated CRM Pixel configured in Events Manager. In Events Manager, click Connect Data Sources, select CRM, then Connect, and create a new Pixel separate from your website Pixel.