Overview
When you connect Meta (Facebook) to Everflow, you unlock better ad performance and complete campaign visibility. Here's what you get: Everflow automatically sends your conversion data to Meta using their Conversions API, which means Meta's algorithm receives real conversion information to optimize your campaigns. Plus, you get granular tracking and analytics to quickly identify winning campaigns and eliminate money-losing ads.
This integration helps you build accurate audiences faster on Meta while giving you the data insights needed to scale profitable campaigns and cut losses quickly.
Prerequisites
Before setting up the Meta integration, ensure you have:
- A Meta Business Manager account with admin access
- An active advertising account in Meta
- A partner and offer created in Everflow
- JavaScript tracking implemented (click and conversion scripts on your landing and thank you pages)
A Step-By-Step Guide
Use the Conversions API Gateway method to generate your access token, as this is the recommended and tested approach.



Set Up Your Conversion Goal
- E-commerce brands: Purchase
- Lead generation: Lead
- App companies: App Install
Optional: Add Purchase Data (For E-commerce)
Add User Data for Better Audience Matching
You don't need to add hashing macros like {adv1>LC_SHA256} for Meta CAPI postbacks. Everflow auto-hashes all macros in the CAPI payload before it's sent. For non-Meta integrations where you need to hash data yourself, the macro syntax lives in Your Guide to Parameters & Macros → Hashing Macros.


Track & Optimize Performance
Monitor Key Metrics with Partner Report
Action Triggers:
- High ROAS (4:1 or better): Scale this campaign immediately
- Low ROAS (under 1:1): Pause and investigate
- Good volume, poor conversion: Check landing page or offer
Analyze Winners with Dimensional Analytics
Get Granular Insights with Flex Report
Essential Tracking Setup
For accurate attribution, ensure fbclid is properly passed:
- Direct Linking: The EF.click script automatically captures fbclid from URLs
- Not Direct Linking: Add &fbclid={fbclid} to your affiliate tracking links
Optimization Strategy
Daily Monitoring
- Check Partner Report for ROAS performance
- Identify campaigns spending money with poor returns
- Pause underperformers immediately
- Increase budgets on high-ROAS campaigns
Weekly Analysis
- Run Dimensional Analytics to find winning combinations
- Create new campaigns using best-performing elements
- Test new landing pages with proven creatives
- Review full funnel event performance
Scaling Winners
When you find a campaign with strong ROAS (3:1 or better):
- Increase daily budget gradually (20-50% increases)
- Create similar campaigns with slight variations
- Test the winning creative on different landing pages
- Expand to similar audiences in Meta
Troubleshooting
If conversions aren't showing up in Meta:
- Missing fbclid: Verify the fbclid appears in your click redirect URL
- Wrong Event Source URL: Double-check the URL in your postback configuration
- Incomplete postback: Ensure all required fields are filled
- Poor match quality: Add more user data fields (email, phone, etc.)
Debug Your Setup
For Meta-specific error codes, check Meta's developer documentation - [Click Here]
FAQ
Tracking Multiple Meta Ad Accounts & Ad Sets
If you run ads to the same offer from multiple Meta (Facebook) business accounts, you may want to see exactly which ad set and ad drove each user so you can optimize placements accordingly.
Meta supports dynamic parameters that pass the ad set and ad identifiers on the click. Append them to your partner tracking link in Meta:
Restricted Events in Protected Categories
Meta restricts certain events from being tracked back to Meta for privacy reasons. This applies to events in protected categories — for example, health and wellness — and starting in 2025 Meta limited access to some of these standard events.
To keep sending conversion data while respecting these restrictions, the recommended approach is to transition the affected events to a custom event naming scheme. This change applies only to events delivered to Meta — the event names in your Everflow dashboard and other ad platforms are unaffected. A common mapping is: