Where do I find my Facebook Access Token and Pixel (Dataset) ID?

In Meta Events Manager, open your Data Source, go to Settings, generate an Access Token, and copy the Dataset ID (Pixel ID). Use these values in the BizStackPro workflow action.

What should I do if I see “No attribution data found”?

Add your Pixel code in the Page Builder’s Head Tracking Code (instead of only global settings), confirm your workflow triggers are correct, and test again using Meta’s Lead Ads testing tools.

🥳 Celebrate Our Launch With a $200 LIFETIME Discount OFF The Premium Plan Use: BIRTHDAY2024

This offer expires 9/30/2024, at 11:59 PM EST

BizStackPro all-in-one digital marketing platform dashboard.

Facebook Conversion API Integration for Lead Events – BizStackPro Help

Facebook Conversion API Integration for Lead Events

Q: What is the Facebook Conversion API (CAPI) integration?

The Facebook Conversion API lets BizStackPro send events to Meta server-side. This improves tracking reliability and helps Meta optimize lead ads using CRM pipeline activity—not just form submissions.

Q: How does CAPI help with Facebook lead ads?

When someone submits a Facebook Instant Form, the contact syncs into BizStackPro. As you move that lead through pipeline stages, BizStackPro can send Lead Events back to Meta so optimization focuses on lead quality and outcomes.

Q: What is Custom Value Mapping?

Custom Value Mapping lets you override default values and pass specific identifiers like FBCLID (for funnel events) or Facebook Lead ID (for lead events) to improve attribution accuracy.

Send CRM pipeline events from BizStackPro back to Meta using CAPI—so Facebook can optimize for lead quality, not just lead volume.

Browse Help Center See All Plans & Features

Improving Your Ad Results by Tracking What Happens After the Lead

You may be generating leads from Facebook ads, but not all leads are equal.

The Conversion API (CAPI) allows you to send real outcomes—like qualified leads, booked calls, or closed deals—back to Meta.

Without this feedback, ad optimization is based only on form submissions, not actual results.

This guide will show you how to connect your pipeline data so your ads improve based on lead quality, not just volume.

Once you understand how CAPI lead events work, follow the steps below to connect Meta, build workflows, and send conversion data from your BizStackPro pipeline.

What This Integration Does

Facebook Lead Ads are great at generating submissions—but CAPI Lead Events help Meta learn which leads actually move forward in your process. BizStackPro can send server-side “CRM events” when a lead hits meaningful milestones in your pipeline.

Capture new Facebook Instant Form leads in BizStackPro
Create/Update an opportunity and place it into a pipeline stage
Send Lead Events to Meta as the opportunity moves through stages
Improve optimization by training Meta on quality signals (Booked, Qualified, Won, etc.)

Follow along: You’ll build two workflows — one to capture leads and one to send conversion events as stages change.

Funnel Events vs. Lead Events

Funnel Events: Actions that happen on your website/funnel (page view, form submit, purchase, etc.). These are typically tied to website traffic.
Lead Events: Events sent when contacts/opportunities move through your BizStackPro pipeline (New → Qualified → Booked → Won, etc.). These help Meta optimize based on outcomes.

Tip: If you run Facebook Instant Forms, Lead Events are usually the “missing link” that helps Meta learn what a good lead looks like after submission.

Step 1: Get Your Meta Pixel (Dataset) ID + Access Token

Open Meta Business Suite → go to Events Manager.
Select your Data Source (Pixel/Dataset).
Go to Settings and copy the Dataset ID (Pixel ID).
In the same area, generate an Access Token.
In BizStackPro, confirm your Facebook account, Page, Ad Account, and Form mapping is connected under Settings → Integrations.

Pro tip: Keep tokens organized. If you rotate tokens later, update the token inside every workflow action that uses it.

Step 2: Build Two Workflows

Workflow 1: Capture Facebook Leads

This workflow creates/updates the contact and opportunity when a Facebook Instant Form is submitted.

Trigger: Facebook Lead Form Submission
Actions: Create/Update Contact, Create/Update Opportunity, set Pipeline + Stage
Optional: Apply tags, assign owner, send confirmation email/SMS
Optional CAPI action: Use Facebook Conversion API to send an initial event if your setup requires it

Follow along: Trigger on Facebook Lead Form Submission → create/update the opportunity → place it into your starting stage (example: New Lead).

Workflow 2: Send Lead Events on Stage Changes

This workflow sends CAPI events when an opportunity moves stages (Qualified, Booked, Won, etc.).

Trigger: Pipeline Stage Changed
Action: Facebook Conversion API
Event Type: Lead Event
Required: Pixel/Dataset ID + Access Token
Test: Move a test lead through stages and confirm events appear in Events Manager

Example: When stage changes to Booked, send a “Booked” CRM event to Meta. When stage changes to Won, send a higher-quality event for optimization.

Custom Value Mapping (When You Need It)

Custom mapping is used when you need to override defaults and pass specific identifiers or attribution values into your CAPI action for better matching.

FBCLID: Often used for funnel/website attribution
Facebook Lead ID: Useful for lead events and CRM matching
Other parameters: Use only what’s necessary and supported by your workflow action

Pro tip: Add mapping only after your baseline setup is working—then improve accuracy iteratively.

Troubleshooting

No attribution data found: Add Pixel code in the Page Builder → Head Tracking Code (not only global settings), then retest.
Events not firing: Confirm your triggers are correct (Lead Form Submission / Pipeline Stage Change) and the workflow is published.
Wrong Pixel/Dataset: Double-check you’re using the correct Data Source ID from Events Manager.
Testing: Use Meta’s lead ads testing tools and move test leads through stages to confirm each event appears.

Follow along: After each change, open Events Manager and verify the latest CRM events were received. Don’t change multiple variables at once—test in small steps.

Want better lead quality from your Facebook ads?

When Meta receives pipeline outcomes (not just form fills), optimization improves—so you can focus on the leads that actually convert.

🚀 See All Plans & Features

Opens in a new tab.

Frequently Asked Questions

What is the Facebook Conversion API (CAPI) integration?

It sends server-side events from BizStackPro to Meta so your tracking is more reliable and ad optimization improves.

How does CAPI help with Facebook lead ads?

It allows Meta to optimize based on pipeline outcomes (Qualified/Booked/Won), not only form submissions.

Where do I find my Access Token and Pixel (Dataset) ID?

In Events Manager (Data Source → Settings), generate an Access Token and copy your Dataset ID (Pixel ID).

What is Custom Value Mapping?

It lets you override defaults and pass identifiers like FBCLID or Facebook Lead ID for stronger matching and attribution.

What if I see “No attribution data found”?

Add Pixel code in the page builder’s Head Tracking Code, verify triggers, then retest.

📚 Browse More Help Guides

Optimize Lead Ads Using Real CRM Outcomes

Capture the lead, move it through your pipeline, and send those stage changes back to Meta with CAPI. That feedback loop helps Facebook learn what “qualified” really means for your business.

✅ View Plans & Features

Better tracking. Better optimization.

📚 Browse More Help Guides

Disclaimer: This site is NOT endorsed by Google, Facebook or YouTube in ANY WAY. All trademarks & Logo / branding are the property of their respective owners. Please Note: This site was created in BizStackPro by Ken George II (An Affiliate of BizStackPro) and may contain affiliate links.