Skip to main content
Facebook Pixel and the Conversions API (CAPI) let you send conversion data from your HoopAI funnels and automations directly to Meta’s advertising platform. This data powers campaign optimization, audience building, and conversion reporting inside Meta Ads Manager — giving your ad campaigns the signal they need to find more of the contacts who actually convert.

​
Pixel vs. Conversions API

HoopAI supports both tracking methods, and using them together is the recommended approach:
  • Facebook Pixel — a browser-based JavaScript snippet that fires when visitors interact with your pages. It is easy to install but can be blocked by ad blockers or lost when users opt out of browser tracking.
  • Conversions API (CAPI) — a server-side integration that sends conversion events directly from HoopAI to Meta’s servers. Because it does not rely on the browser, it is not affected by ad blockers, iOS privacy changes, or browser-based tracking restrictions.
Using both methods together (called “deduplication mode”) gives you the broadest possible signal coverage while Meta’s systems deduplicate any events that are reported twice.

​
Step 1: Create a Meta Pixel

  1. Log in to Meta Business Suite and navigate to Events Manager.
  2. Click Connect Data Sources and select Web.
  3. Choose Meta Pixel and Conversions API as your connection method.
  4. Name your pixel, verify your domain, and select the events you want to track (for example, Lead, Purchase, Schedule).
  5. Enable customer parameters including email, first name, last name, and client IP address for better match quality.
  6. Copy the Pixel ID shown in Events Manager — you will need this in HoopAI.

​
Step 2: Add the Pixel to your funnels

To install the Facebook Pixel on pages built in HoopAI:
  1. In HoopAI, navigate to Sites → Funnels and open the funnel you want to track.
  2. Go to Settings for the funnel (not an individual page).
  3. Locate the Header Tracking Code field.
  4. Paste your complete Facebook Pixel base code (including the fbq('init', 'PIXEL_ID') and fbq('track', 'PageView') lines) into the field.
  5. Save the settings. The pixel will now fire on every page in the funnel.
To add the pixel to a single page only, open that page’s settings in the funnel builder and paste the code into the page-level header tracking field.
If you use the same pixel across multiple funnels, paste the same base code into the header tracking settings of each funnel. There is no central site-wide pixel field in HoopAI — each funnel or website is configured independently.

​
Step 3: Set up Conversions API events via workflows

The Conversions API integration in HoopAI uses workflows to send conversion events to Meta at the moment a key action happens in your CRM — not just when a page is viewed.
  1. In Automations, open or create a workflow.
  2. Add a trigger — for example, Form Submitted, Customer Booked Appointment, Survey Submitted, or Order Form Submission.
  3. Add an action and search for Facebook Conversion API.
  4. Select Funnel Event as the event type.
  5. From Meta Business Suite → Events Manager → Settings, copy your Access Token and Dataset ID (also called Pixel ID).
  6. Paste both values into the corresponding fields in the workflow action.
  7. Select the Meta standard event to send — common choices include Lead for form submissions and bookings, and Purchase for order completions.
  8. Optionally, enter an event value (numeric) to represent the estimated or actual value of the conversion for campaign optimization.
  9. Save the action and activate the workflow.
For lead value, use a consistent assumed value based on your average lead-to-close rate. For example, if your average deal is worth 2,000andyouclose1in10leads,eachleadisworthapproximately2,000 and you close 1 in 10 leads, each lead is worth approximately 200. Enter this value so Meta can optimize for higher-value leads over time.

​
Supported trigger events for CAPI

The following HoopAI triggers can be used to fire Facebook Conversion API events:
HoopAI triggerRecommended Meta event
Form SubmittedLead
Survey SubmittedLead
Customer Booked AppointmentSchedule
Order Form SubmissionLead or Purchase
Payment ReceivedPurchase
Opportunity Stage Changed (to closed-won)Purchase

​
Verifying your setup

After activating the workflow, test the integration by submitting a form or booking an appointment using a test contact. Then:
  1. In Meta Business Suite, go to Events Manager → Test Events.
  2. Enter your website URL and click Open Website to start a test session.
  3. Complete the conversion action and verify that the event appears in the Test Events panel within a few minutes.
Server-side events sent via CAPI will show up separately from browser-based pixel events in the test panel.

​
Custom mapping for advanced users

HoopAI supports custom parameter mapping for Facebook Conversion API events. When enabled, you can map additional data fields from your CRM — such as Facebook Click ID (FBCLID) or Facebook Lead ID — to the corresponding Meta parameters. This improves event matching and attribution accuracy. To enable custom mapping, toggle on the Custom Mapping option in the Facebook Conversion API workflow action configuration.

​
Reading conversion data in Meta Ads Manager

Once events are flowing from HoopAI to Meta:
  1. Open Meta Ads Manager and navigate to the campaign, ad set, or ad you want to evaluate.
  2. In the columns selector, add the custom events you have configured (for example, Lead, Schedule, Purchase) as conversion columns.
  3. Review your cost per result for each conversion type to evaluate campaign efficiency.
  4. Use the event data in Custom Audiences to create retargeting lists based on users who completed specific conversion events.

​
Frequently asked questions

Event matching requires that the Pixel fires on the same session where the ad click occurred, and that customer parameters (email, name) are passed correctly. If the contact navigated away from the landing page before converting, or if customer parameters are missing, match rates will be lower. Using CAPI alongside the browser pixel improves overall match coverage.
HoopAI sends a unique event ID with each CAPI event. When you also have the browser pixel installed on the same page, Meta uses the event ID to deduplicate browser and server events automatically. Make sure both methods use the same event name (for example, Lead) so deduplication works correctly.
Yes. Use the same Pixel ID in the header tracking code of every funnel and in every Conversions API workflow action. All events across funnels will be attributed to the same Meta dataset, giving you a unified view in Events Manager.
The pixel alone is sufficient for basic tracking, but CAPI is strongly recommended. iOS privacy changes and ad blockers can suppress 20–40% of browser-based pixel events in some audiences. CAPI events are not affected by these restrictions, making your conversion data more complete and your campaign optimization more accurate.
Last modified on March 5, 2026