Meta CAPI Feedback

What is the Conversions API?

Meta's Conversions API (CAPI) is a server-to-server connection that lets you send conversion events directly to Facebook. Unlike the Meta Pixel, which runs in the browser and can be blocked by ad blockers or privacy settings, CAPI events are sent from Adsu's servers and always reach Meta reliably.

By default, when you run Meta ads, Facebook optimizes for the action you tell it to -- usually "leads" or "conversions" at the form-fill level. Facebook finds people who are likely to fill out your form. But filling out a form and actually becoming a paying gym member are very different things.

When Adsu sends deeper-funnel events back to Meta -- appointments booked, prospects who showed up, members who paid -- Facebook's algorithm learns the difference. Over time, it starts finding more people who look like your actual paying members, not just people who click forms.

How the Feedback Loop Works

Adsu's CAPI feedback loop operates automatically once your Meta ad account is connected and your funnel stages are configured:

1. A contact advances through a funnel stage in Adsu -- via a GoHighLevel pipeline move, booked appointment, Stripe payment, or any other stage trigger.
2. Adsu checks if the contact originated from Meta (either their sourceType is "meta" or they have a Facebook click ID).
3. If the contact is Meta-sourced and the stage maps to a CAPI event, Adsu queues a conversion event for delivery.
4. The event is sent to Meta's Conversions API with hashed user data and event details (event name, timestamp, value if applicable).
5. Meta receives the event, matches it to the user, and feeds the data into its ad delivery algorithm.

Stage-to-Event Mapping

Not every funnel stage triggers a CAPI event. Adsu maps specific stages to Meta conversion events based on what is most useful for ad optimization:

• Appointment Set maps to Schedule. Tells Meta the lead booked an appointment -- a strong intent signal beyond a form fill.
• Showed maps to AppointmentShowed (custom event). Tells Meta the person actually showed up, filtering out no-shows and giving the algorithm an even stronger quality signal.
• Closed maps to Purchase with the transaction value. The ultimate conversion signal -- actual revenue. The purchase amount is included so Meta can optimize for value.
• Active Member also maps to Purchase with the contact's lifetime value (LTV). Signals that the member has ongoing value, which is especially important for subscription-based gym memberships.

Other stages like "New" and "Contacted" do not trigger CAPI events because they are too similar to the initial lead event Meta already tracks natively.

Which Contacts Trigger CAPI Events

CAPI events only fire for contacts that originated from Meta:

• Contacts with a Facebook click ID (fbclid) captured by the tracking script when they landed on your website from a Meta ad.
• Contacts with sourceType "meta", typically from Meta lead form submissions.

Contacts from Google Ads, organic search, referrals, or any non-Meta source are silently skipped. Sending non-Meta conversions to CAPI would confuse the algorithm because Meta cannot attribute those conversions to any of your ads.

Privacy and Data Handling

Meta requires that personally identifiable information be hashed before sending it through the Conversions API. Adsu handles this automatically:

• Email addresses are lowercased, trimmed, and SHA256-hashed. Meta never receives the raw email from Adsu.
• Phone numbers are stripped to digits only and SHA256-hashed. The raw phone number is never transmitted.
• Facebook click IDs (fbclid), browser parameters (fbp, fbc), IP addresses, and user agent strings are sent unhashed as Meta requires these in raw form for matching.

All hashing happens on Adsu's servers before any data leaves for Meta. The hashing is one-way (SHA256), meaning the original values cannot be recovered from the hashes.

Event Deduplication

Adsu generates a deterministic event ID for every CAPI event using the format adsu_{contactId}_{stageKey}. The same contact advancing to the same stage always produces the same event ID, regardless of how the stage change was triggered.

This matters because the same stage change can sometimes be detected by multiple paths -- for example, a manual pipeline move and a calendar booking webhook firing simultaneously. Both produce the same event ID, so Meta deduplicates them automatically. You never have to worry about conversions being counted twice.

Reliability

Adsu decouples CAPI delivery from the stage update process. When a contact advances, two things happen independently: the contact's stage is updated in the database immediately (source of truth for your dashboard), and a separate background job is queued to send the CAPI event to Meta. A Meta API outage or rate limit never prevents your funnel from functioning.

Measuring CAPI Impact

The impact of CAPI is not instant. Meta needs enough conversion events to learn from -- typically at least 50 events of a given type. Here is what to expect:

• First 2-4 weeks: You may not notice any change in ad performance. Facebook is still collecting data. This is normal.
• 1-3 months: Lead quality should gradually improve. Cost per lead may stay flat or increase slightly, but leads should convert at higher rates. Cost per paying member should begin to decrease.
• 3+ months: With enough conversion data, Facebook becomes significantly better at finding people who match your paying member profile. Gyms using CAPI feedback consistently report 20-40% lower cost per acquisition over six months.

Requirements

CAPI works automatically once these are in place:

• Meta ad account connected -- needed to discover the Pixel ID and authenticate API calls. The Pixel ID is auto-discovered from your ad account during setup and backfilled by health checks.
• Funnel stages configured -- stages must be mapped so Adsu knows which stage changes trigger CAPI events.
• Active Meta campaigns -- you need Meta ads generating leads with Facebook click IDs. CAPI only fires for Meta-sourced contacts.

No additional configuration is required. There are no CAPI-specific settings to toggle -- once the prerequisites are in place, events flow automatically as contacts move through your funnel.

Related Pages

• Attribution Models -- how revenue credit is distributed across touchpoints
• Matching Engine -- how Adsu identifies Meta-sourced contacts for CAPI eligibility
• Connect Meta Ads -- initial Meta setup including ad account selection and Pixel discovery
• Configure Funnel Stages -- mapping pipeline stages to enable CAPI event triggers