Overview

When you run Facebook or Instagram ads to attract new families, you need a way to track which ads actually lead to enrollments. The Meta Conversion API helps you send accurate enrollment data back to Meta so your ad campaigns can optimize and improve over time.

This article covers how to set up automations that send conversion events to Meta, and explains the new Ad Manager connection option that makes this much easier.

Why Send Conversion Data Back to Meta?

After you create an ad campaign and conversion dataset in Meta, you need to send enrollment events back to Meta through the Conversion API. Here's why this matters for your childcare business:

  • More Accurate Tracking: The Conversion API sends data directly from Enrollio's servers, bypassing ad blockers and browser restrictions that might prevent the Meta pixel from tracking parent actions.
  • Better Results: When Meta knows which ads lead to tour bookings and enrollments, it can show your ads to more families likely to convert.
  • Complete Picture: Tracks conversions across devices—like when a parent sees your ad on mobile but books a tour on desktop.
  • Privacy Compliant: Works reliably even as browser privacy settings become stricter.
  • Smarter Spending: More accurate data helps Meta optimize your ad budget and improve your return on investment.
Pro Tip: The Meta pixel and Conversion API work together—the pixel tracks what happens in the browser, while the Conversion API fills in the gaps when pixel tracking fails.

Which Automation Triggers Work with Meta Conversion API?

The triggers you can use depend on what type of event you're sending to Meta. Here are the eligible triggers for each event type:

For Enrollment Page Events (Funnel Events)

Use these triggers when tracking form submissions and tour bookings:

  • Form Submitted
  • Survey Submitted
  • Customer Booked Appointment (for tour bookings from your scheduling widget)
  • Order Form Submission

For Lead Generation Events

Use these triggers when tracking Facebook lead forms:

  • Facebook Lead Form Submission
  • Enrollment Pipeline Stage Change (only works if the family originally came from a Facebook lead form)

For Instagram Direct Message Ads

Use any trigger that creates a new family contact in Enrollio.

Understanding the Two Connection Types

When you create a Meta Conversion API action in your automation, you'll see two connection options:

Integrations (Manual Setup)

This option requires you to manually:

  • Copy your Pixel ID from Meta
  • Generate and add an access token
  • Configure event details

This gives you full control but requires switching back and forth between Enrollio and Meta.

Ad Manager (Simplified Setup)

This newer option streamlines the entire process:

  • Auto-populated Pixels: All pixels from your connected Ad Manager account appear in a dropdown—no copying and pasting required.
  • Automatic Access Token: Enrollio handles the access token automatically.
  • Smart Event Selection: Choose based on your campaign objective:
    • Website traffic campaigns → Send enrollment page events
    • Lead generation campaigns → Send lead events
    • Click to direct message ads → Send Instagram DM events
[SCREENSHOT: Meta Conversion API action settings screen showing Ad Manager vs Integrations radio buttons]
Pro Tip: For Lead Events, the Stage Name field should match your actual Enrollment Pipeline and stage names for accurate reporting. Use the tag icon to select custom values from your pipeline.

Can I Track Offline Events Like Phone Calls?

Yes! You can send conversion events for offline actions like phone calls, enrollment pipeline changes, or tag additions—as long as the family originally came from a Facebook or Instagram ad.

Enrollio looks for the Facebook click ID (fbclid) in the family's record. If found, the conversion data is sent to Meta.

Example 1: Facebook Form to Enrollment

  1. A parent fills out your Facebook lead form (their first interaction)
  2. Enrollio creates their contact with fbclid data
  3. Your automation sends the lead event to Meta
  4. Later, they become an enrollment opportunity and change stages
  5. Your automation sends the enrollment event to Meta using the original fbclid

Example 2: Multiple Touchpoints

  1. A parent first visits your site via Google search (no fbclid)
  2. Later, they see your Facebook ad and fill out a form
  3. Enrollio updates their record with fbclid from Facebook
  4. Your automation sends the form submission to Meta
  5. When they become an enrollment opportunity, that conversion is also sent to Meta
[SCREENSHOT: Automation builder showing a "Facebook Lead Form Submitted" trigger connected to "Meta Conversion API" action]

Custom Field Mapping

Similar to Google Ads, you can now customize how Enrollio maps data to Meta's conversion parameters.

How It Works:

  • Custom mapping is disabled by default
  • Toggle it on to enable manual field mapping
  • For enrollment page events: Map the FBCLID field
  • For lead events: Map the Facebook Lead ID field
  • Your custom mappings take priority over Enrollio's defaults
  • If you leave fields empty, Enrollio uses its built-in values
[SCREENSHOT: Custom field mapping interface showing FBCLID and Facebook Lead ID mapping options]
Pro Tip: Most childcare centers can use the default mapping. Only customize if you need to track specific custom fields in your Meta campaigns.

Next Steps

Once you've set up your Meta Conversion API automation:

  1. Test it by submitting a form or booking a tour yourself
  2. Check Meta Ads Manager to confirm events are being received
  3. Monitor your campaign performance for 3-5 days to allow Meta's algorithm to optimize
  4. Adjust your targeting or creative based on which events drive the most enrollments

Need help connecting your Meta Ad Account? Check out our guide on setting up Meta Ad Manager integration.