Skip to main content

IP Management for CAPI Events

This guide explains the three IP address modes in Pixel Plus and helps you choose the right one. The setting is in the CAPI configuration section but affects all tracking channels — both Pixel (browser) and CAPI (server-side).

Why IP Management Is Tricky​

The internet uses two IP formats: IPv4 (192.168.1.1) which still dominates global traffic, and IPv6 (2001:0db8:...) which Facebook increasingly recommends for better matching.

The core problem: when the Facebook Pixel JavaScript loads in the visitor's browser, it automatically captures their IP (usually IPv4) — this is completely beyond the module's control. If you configure the module to send IPv6, Facebook compares:

  • Pixel automatic capture: 203.0.113.5 (IPv4)
  • Module custom parameters + CAPI: ::ffff:203.0.113.5 (IPv6 format)

The mismatch triggers diagnostic warnings even when everything is configured correctly.

Key Insight

Warnings appear not because something is broken, but because Facebook's own automatic IP capture (which you cannot control) differs from the IP format the module sends.

Your Three Options​

Sends the visitor's IP exactly as captured by the server — no conversion. All sources (Pixel automatic capture, custom parameters, CAPI) show the same IP.

  • ✅ All sources match — no mismatch warnings
  • ✅ Accurate representation of the visitor's actual IP
  • ⚠️ Facebook may show "Consider using IPv6" (informational only)

Option 2: IPv6 If Available​

Attempts to detect the visitor's IPv6 address via a real network test. Falls back to IPv4 if unavailable (which is the case for ~60% of visitors globally).

DNS Requirement

Your domain needs an AAAA DNS record for IPv6 detection to work. Without it, detection always fails and falls back to IPv4.

  • ✅ Only uses IPv6 when genuinely available
  • ✅ Graceful fallback — behaves like Raw IP for most visitors
  • ⚠️ Most visitors still use IPv4, so similar warnings as Raw IP for the majority

Option 3: Force IPv6 (Avoid)​

Attempts IPv6 detection; if it fails, converts the IPv4 address to IPv6-mapped format (::ffff:192.168.1.1). This guarantees all IPs are sent in IPv6 format, but creates intentional mismatches with the Pixel's automatic capture.

Most Aggressive Option
  • ❌ Creates mismatches with Pixel's automatic IPv4 capture
  • ❌ Often generates more diagnostic warnings, not fewer
  • ❌ IPv6-mapped addresses aren't true IPv6 connections

Our Recommendation​

Use Raw IP for most stores. IPv6 If Available is acceptable if you want to prioritize IPv6 when it's genuinely present. Avoid Force IPv6 — it creates more problems than it solves.

Bottom Line

No configuration eliminates all Facebook diagnostic warnings. IPv4 still dominates traffic, and Facebook's automatic Pixel capture will always see the visitor's real IP. Focus on metrics that matter: Event Matching Quality and conversion tracking.

Configuration Steps​

  1. Go to Pixel Plus Configuration → CAPI Options → IP Management
  2. Select "Send IP as captured (Raw)" or "IPv6 If Available"
  3. Click Save
  4. Clear PrestaShop cache: Advanced Parameters → Performance → Clear cache
  5. Monitor for 7 days before making further changes
Avoid Frequent Changes

Switching IP configurations often creates inconsistent data. Choose one option and let it run for at least a week before evaluating.

Which IP mode should I choose for most stores?

Use Raw IP for most stores. It sends the visitor's IP exactly as captured by the server, ensuring all tracking sources report the same value with no mismatches.

Why does Facebook recommend IPv6 if my visitors mostly have IPv4?

Facebook's recommendation is forward-looking. Most internet users still connect via IPv4, so this is an informational suggestion, not an error. Your tracking accuracy is not affected by keeping Raw IP mode.

What is the difference between IPv6 If Available and Force IPv6?

IPv6 If Available checks whether the visitor genuinely has an IPv6 address and sends it only if confirmed. Force IPv6 converts any IPv4 address to an IPv6-mapped format, which creates mismatches with the Pixel's automatic IP capture and typically generates more warnings.

Why does Force IPv6 create more problems?

The browser Pixel automatically captures the visitor's real IP, usually IPv4. If CAPI sends an artificially converted IPv6-mapped address, Facebook sees two different IPs for the same event and flags the mismatch in diagnostics.

Does my domain need special DNS settings to use IPv6 If Available?

Yes. Your domain needs an AAAA DNS record pointing to an IPv6 address. Without it, the IPv6 detection always falls back to IPv4, making the option behave the same as Raw IP.