Issue

You observe low Event Match Quality (EMQ) in Meta for high-volume events such as PageView delivered via Segment's Meta Conversions API (CAPI). You may also see the warning "Update Conversions API IP addresses to IPv6 IP addresses" or notice IP address mismatches between client-side and server-side events in Meta Events Manager.

Product

Segment

Environment

Segment Console

Cause

Meta Pixel automatically collects IPv6 addresses directly from the browser. However, Segment's server-side Conversions API integration may send IPv4 addresses unless explicitly configured. When Meta compares browser events against server-side CAPI events, mismatched IP protocols (IPv6 versus IPv4) or missing consistent identifiers like external_id hinder Meta's event deduplication and lower match scores.

Resolution

To resolve IP mismatch warnings and improve Meta Event Match Quality while preserving PII compliance:

1. Capture and Pass Client IPv6 Addresses 
   Ensure your application or server middleware extracts the user's IPv6 address from HTTP request headers and explicitly passes it in the event payload within context.ip.
2. Standardize external_id Across Events 
   Pass a consistent external_id (such as a hashed unique user ID or persistent identifier) in both client-side Meta Pixel events and server-side CAPI payloads. Consistent identifiers allow Meta to accurately pair and deduplicate high-volume events like PageView.
3. Configure Advanced Matching Settings 
   Review your Segment Meta Conversions API destination settings and map user parameters (such as email or phone number). Ensure all sensitive PII is properly hashed or formatted according to Segment's automatic hashing requirements before transmission.
4. Verify Event Match Quality 
   After deploying payload updates, navigate to Meta Events Manager to monitor your Event Match Quality score and confirm that IPv6 warning messages clear.

Additional Information

• Segment Facebook Pixel Documentation: Mismatched IP Address Warning