Objective
This article explains how to identify and troubleshoot redundant Facebook Conversions API (CAPI) integrations by reviewing the “Connected Partners” settings in Facebook Events Manager. If you’re seeing higher-than-expected server event counts or duplicate events in Meta after connecting Segment or another CAPI integration, this guide will help you determine if multiple integrations are active for the same Pixel ID.
Product
Twilio Segment
Environment
Segment Console
User Account Permission/Role(s) Required
- Access to the Facebook Business Manager account with permission to view and manage Pixel settings
- Access to the Segment workspace and destination configuration
Procedure
Log in to Facebook Events Manager:
Go to Facebook Events Manager.Select the Relevant Pixel:
In the left navigation, choose the Pixel ID that is connected to your Segment Facebook Conversions API destination.Open the “Settings” Tab:
Click on the “Settings” tab for the selected Pixel.Scroll to “Connected Partners”:
Locate the “Connected Partners” section. This area lists all integrations (such as Segment, CAPI gateways, or other marketing platforms) that are currently sending events to this Pixel.-
Review the List of Partners:
- Check if more than one partner or integration is listed as connected to the Pixel.
- If you see multiple CAPI integrations (for example, both Segment and another CAPI gateway), this can result in duplicate server events being sent to Meta.
-
Take Action if Needed:
- If you identify redundant integrations, decide which integration should remain active.
- Remove or disable any unnecessary CAPI connections to prevent duplicate event reporting.
Verify Event Counts:
After making changes, monitor your event counts in both Segment and Meta to confirm that the discrepancy is resolved.
Additional Information
- For more on deduplication and best practices, see Segment’s Deduplication Considerations and Meta’s Handling Duplicate Pixel and Conversions API Events.
- If you continue to see discrepancies, request event IDs from Facebook support to trace the source of server events.