Who This Is For / When to Use
Use this workflow action if you:
Run Facebook or Instagram ads
Want accurate conversion tracking despite iOS 14+ privacy restrictions
Use Kyrios workflows for forms, appointments, or orders
Need server-side event tracking without relying on cookies
What Is Facebook Conversion API in Kyrios
Facebook Conversion API (CAPI) is a server-side tracking method.
Instead of relying on browser cookies or the Meta Pixel alone, Kyrios sends events directly to Meta from the platform.
This improves:
Conversion accuracy
Event matching
Reporting reliability
Compliance with modern privacy controls
Prerequisites Before Setup
Before creating the workflow action, ensure:
You have access to Meta Business Manager
A Meta Pixel exists
Your domain is verified
Events Manager access is available
Step 1: Verify Your Domain in Meta
Domain verification is required for event authorization.
Open Meta Business Settings
Go to Brand Safety and Suitability
Select Domains
Click Add → Create a new domain
Complete domain verification
Step 2: Access Meta Events Manager
Open Meta Business Suite
Click All tools
Select Events Manager
Step 3: Select Your Pixel Data Source
In Events Manager, open Data Sources
Select your Pixel
Open the Overview tab
Step 4: Generate a Conversions API Access Token
Open the Settings tab of your Pixel
Scroll to Conversions API
Under Set up direct integration, click Generate access token
Copy and securely store the token
Step 5: Copy the Dataset ID
The Dataset ID is required for Kyrios workflows.
Stay in Pixel Settings
Locate Dataset ID
Copy the value
Step 6: (Optional) Set Up Meta Pixel for Browser Events
Meta Pixel complements server-side tracking.
In Events Manager, click Set up Meta Pixel
Choose Install code manually
Copy the base pixel code
Step 7: Add Meta Pixel to Kyrios Funnel
Open Sites > Funnels
Select the funnel
Open Settings
Paste the pixel code into Head Tracking Code
Click Save
Step 8: Enable Automatic Advanced Matching (Recommended)
Advanced matching improves event attribution.
Continue Pixel setup
Enable Automatic Advanced Matching
Select all recommended fields
Step 9: Create a Workflow Trigger in Kyrios
The workflow must start with a compatible trigger.
Supported triggers include:
Form Submitted
Survey Submitted
Customer Booked Appointment
Order Submitted
Step 10: Add Facebook Conversion API Action
Click Add Action
Select Facebook Conversion API
Choose Integration as connection type
Step 11: Configure Core Action Fields
Required fields:
Access Token (from Meta)
Dataset ID
Facebook Event Name (must match Meta event)
Event Type
Step 12: Setting Value & Currency for Purchase Events
When tracking revenue:
Set Event Type to Lead Event
Set Stage Name to Purchase
Enter Value
Select Currency
If the stage is not Purchase, value and currency are ignored.
Step 13: Enable Custom Mapping (Optional)
Custom mapping improves attribution by passing identifiers such as:
FBCLID
Lead ID
IGSID
System values are used if custom fields are missing.
Step 14: Testing the Conversion API Event
Testing requires a real trigger, not the “Test Workflow” button.
Open Test Events in Meta
Copy the Test Event Code
Paste it into the workflow action’s Test Code field
Trigger a real event (form submit, booking, order)
Step 15: Publish the Workflow
After validation:
Remove the test code
Save the action
Change workflow status from Draft to Published
Common Issues and Fixes
Events not appearing in Meta
Confirm the domain is verified
Check Domains in Allow List
Ensure Event Source URL is enabled
No data for appointment events
Only Customer Booked Appointment triggers are supported.
Appointment status changes do not send events.
Test events not showing
Ensure a real trigger fired
Confirm test code is removed after testing
Check Meta Diagnostics tab
FAQ
Why is lead data not being sent?
The workflow must start with a supported trigger such as Form Submitted, Survey Submitted, Appointment Booked, or Order Submitted.
Why does Meta show the event as “Custom Event”?
This can happen during testing.
Live traffic will report the correct event type.
Does Conversion API affect page speed?
No.
All events are sent server-side and do not impact page load time.
Can I use custom values for Access Token and Dataset ID?
Yes.
Custom values are fully supported in workflow fields.
Why can’t I use “Test Workflow” to validate events?
The Test Workflow button does not simulate Facebook Conversion API events.
A real trigger must occur.