Skip to main content

Overview

The Meta Ads integration allows you to automatically sync your advertising data from Facebook/Meta Ads and send conversion information back to Meta to optimize your campaigns. This creates a powerful feedback loop that improves your ad targeting and ROI over time.

What This Integration Provides

Ad Spend Tracking

Automatically import your daily ad spend, clicks, and impressions for accurate ROI reporting

Conversion Postbacks

Send purchase data back to Meta to improve campaign optimization and attribution

Unified Reporting

See your ad performance alongside your funnel metrics in one dashboard

Multi-Account Support

Connect multiple ad accounts if you manage different businesses or campaigns

Setup Guide

Step 1: Connect Your Meta Ads Account

  1. Navigate to Settings → Integrations → Advertising
  2. Find Meta Ads and click “New integration” or “Manage integrations”
  3. Click “Connect your Meta Ads Account”
  4. You’ll be redirected to Facebook to authorize access
  5. Grant the necessary permissions for ad data access
You’ll need admin access to your Meta Ads account to complete the authorization.

Step 2: Select Your Ad Account

After authorization, you’ll see a list of all ad accounts you have access to:
  1. Review the available accounts (shown with account ID, name, and currency)
  2. Click Select next to the ad account you want to track
  3. The selected account will be highlighted with a blue checkmark
If you manage multiple businesses, you can create separate integrations for each ad account to keep reporting organized.

Step 3: Configure Conversion Tracking (Optional)

To enable conversion postbacks (highly recommended):
  1. Enter your Meta Pixel ID
    • Find it in Meta Business Manager → Events Manager → Data Sources
    • It’s a 15-16 digit number
  2. Enable Conversion Postbacks
    • Check the box to enable automatic postback sending
    • This sends purchase data back to Meta when customers complete orders
  3. Click “Update Integration” to save
Conversion postbacks require a valid Pixel ID. If you enable postbacks without a Pixel ID, the system will warn you.

Understanding Pixel Attribution

How It Works

ElasticFunnels uses a page-based pixel tracking system to ensure accurate attribution:
  1. Each page in your funnel can have its own Meta Pixel ID
  2. When a visitor lands on a page, we track which pixels they were exposed to
  3. When they make a purchase, we send conversion data to the correct pixel(s)

Why This Matters

Example: Multi-Business Scenario

Page 1 (Product A): Uses Pixel 111
Page 2 (Product B): Uses Pixel 222

If customer visits both pages and purchases:
→ Both Pixel 111 and Pixel 222 receive the conversion
→ Accurate attribution for partnership/referral funnels

Setting Pixel ID per Page

You can configure the Meta Pixel ID at two levels:
Set different Pixel IDs on individual pages in your funnel settings. This allows different businesses or partners to track their own conversions.Best for: Agency managing multiple clients, partnership funnels

Ad Spend Syncing

Automatic Sync Schedule

Your ad spend data syncs automatically every 2 hours. This includes:
  • Daily spend amounts
  • Click counts
  • Impression counts
  • Campaign names
  • Ad set information
Historical data is available immediately after connecting. Future data syncs automatically without any action needed.

Viewing Your Ad Data

After your first sync completes, you can view your ad performance:
  1. Go to Analytics → Ad Spend Reports
  2. Select your date range
  3. View spend, clicks, and ROI metrics
  4. Filter by campaign, ad set, or specific ads

Conversion Postbacks

What Are Conversion Postbacks?

Conversion postbacks send purchase information back to Meta when a customer completes an order. This helps Meta:
  • Optimize your campaigns for conversions (not just clicks)
  • Improve audience targeting based on who actually buys
  • Provide accurate attribution data
  • Enable features like automated bidding

What Data is Sent

When a conversion occurs, we send:
  • Purchase event
  • Order value and currency
  • Order ID
  • Customer information (hashed for privacy)
  • Click identifier (fbclid)
All customer data is hashed and encrypted according to Meta’s privacy requirements. We never send raw personal information.

When Postbacks Are Triggered

Postbacks fire automatically when:
  1. ✅ Customer clicked a Meta ad (fbclid present)
  2. ✅ Customer visited a page with a Meta Pixel
  3. ✅ Customer completed a purchase
  4. ✅ Integration has postbacks enabled
  5. ✅ Pixel ID matches the page they visited
The system intelligently determines which pixel to fire based on which pages the customer visited. If they saw multiple pixels, all relevant pixels receive the conversion.

Managing Multiple Integrations

If you manage multiple businesses or clients, you can create multiple Meta Ads integrations:

When to Create Multiple Integrations

  • Managing different client accounts (agencies)
  • Separate businesses with different websites
  • Different brands under one ElasticFunnels account
  • Testing vs. production campaigns

How It Works

Each integration is independent:
  • Has its own ad account
  • Has its own Pixel ID
  • Has its own postback settings
  • Syncs separately
Name each integration clearly (e.g., “Client A - Supplements”, “Client B - Software”) to keep them organized.

Connection Status & Health

Status Indicators

Your integration status shows real-time health:
  • 🟢 Active - Integration is working, data syncing normally
  • 🔵 Syncing… - Currently pulling new data from Meta
  • 🔴 Error - Connection issue that needs attention
  • ⚪ Not Configured - Integration not fully set up

Last Sync Information

The integration card shows:
  • Last synced: How long ago data was last updated
  • Records synced: Number of records imported
  • Total spend: Recent spending tracked

Testing Your Connection

Use the “Test Connection” button to verify:
  • Your access token is valid
  • You have permission to access the ad account
  • Data can be retrieved successfully
If you see an error status, check if your Meta session has expired. Click the re-authenticate button to refresh your connection.

Troubleshooting

Common Issues

Possible Causes:
  • First sync hasn’t run yet (syncs every 2 hours)
  • No ad spend in the selected date range
  • Ad account has no active campaigns
Solution: Wait 2 hours for first sync, or contact support to trigger manual sync
Cause: Meta access tokens expire after 60 daysSolution: Click the blue “Re-authenticate” button on your integration to refresh your connection
Possible Causes:
  • Postbacks not enabled
  • No Pixel ID configured
  • Customer didn’t visit a page with your pixel
Solution:
  1. Verify Pixel ID is entered correctly
  2. Check “Enable Conversion Postbacks” is checked
  3. Ensure your funnel pages have pixel configured
Question: I have 5 ad accounts listed, which should I select?Answer: Select the ad account that contains the campaigns you want to track. You can create multiple integrations if you need to track multiple ad accounts.
Pixel ID: Tracking code on your website (one per business/website)Ad Account: Where you manage your ad campaigns in MetaRelationship: Multiple ad accounts can share one pixel if they’re promoting the same website.

Getting Help

If you encounter issues:
  1. Check the Status indicator on your integration
  2. Click “Test Connection” to diagnose issues
  3. Review the error message if one is shown
  4. Contact support with your integration ID

Best Practices

Optimization Tips

1

Set Up Conversion Postbacks

Always enable postbacks to help Meta optimize your campaigns for actual purchases, not just clicks.
2

Use Descriptive Names

Name your integrations clearly, especially if managing multiple accounts (e.g., “Main Campaign - US”, “Testing Account”).
3

Monitor Sync Status

Check your integration status regularly to ensure data is syncing properly and connections haven’t expired.
4

Test After Setup

Use the “Test Connection” button after setup to verify everything is working before running campaigns.

Pixel Configuration Strategy

Single Business:
  • Use ONE Pixel ID in your integration
  • Apply to all funnel pages
  • Simplest setup for most users
Multi-Business or Agency:
  • Create SEPARATE integrations for each client
  • Each integration gets its own Pixel ID
  • Keeps reporting and postbacks isolated
Partnership Funnels:
  • Set different Pixel IDs on different pages
  • Partner pages fire partner’s pixel
  • Main pages fire your pixel
  • Both get conversion credit

Frequently Asked Questions

Every 2 hours automatically. Your data is always up-to-date without manual work.
Yes! Click “Manage integrations” and then “Add integration” to connect additional accounts. Perfect for agencies or users managing multiple businesses.
No, Pixel ID is optional. It’s only required if you want to send conversion postbacks to Meta. You can still sync and view ad spend data without it.
No. This integration works alongside your existing pixel. It sends server-side conversion events that complement your pixel tracking.
Conversion postbacks appear in Meta Events Manager within 5-10 minutes. Ad spend data appears in ElasticFunnels within 2 hours of your first sync.
Create separate integrations for each client. Each integration can have:
  • Different ad account
  • Different Pixel ID
  • Independent postback settings
This keeps your client data properly separated.

Data Privacy & Security

What Data We Access

When you connect Meta Ads, we request permission to:
  • Read your ad account information
  • Access ad performance metrics (spend, clicks, impressions)
  • View campaign and ad set names
  • No access to modify or create ads

How We Store Your Data

  • Access tokens are encrypted and stored securely
  • Ad spend data is stored for historical reporting
  • Conversion data is hashed before sending to Meta
  • You can disconnect at any time and data will be removed

Compliance

Our integration follows:
  • Meta’s Platform Terms and Developer Policies
  • GDPR and privacy regulations
  • Secure OAuth 2.0 authentication
  • Industry-standard encryption

Next Steps