Skip to main content

Meta Asks for IPv6 in Event Tracking - Pixel Plus Solutions

🌐 Why is Meta asking for IPv6?​

Meta is encouraging businesses to send event data (like ViewContent, AddToCart, Purchase...) using IPv6 addresses, because IPv6 can provide better attribution accuracy and is more future-proof as the world transitions away from IPv4.

You may see messages like:

"Send IPv6 for AddToCart events"

"Send IPv6 for Purchase events"

"Try Sending IPv6 for ViewContent events"
...

This recommendation appears when Meta detects that your current server-side (CAPI) events are being sent using IPv4 addresses.

🤔 Why is my site sending IPv4?​

Although IPv6 is widely supported, most internet users in Europe and other regions are still assigned IPv4 addresses by their Internet Service Providers (ISPs).

That means, even if your server supports IPv6, the actual customer IP seen by the module is usually an IPv4. This is not a mistake — it's just the current infrastructure reality.

⚙️ Solution proposed from the Pixel Plus module - 3 ways to handle the IPS​

To help with this, Pixel Plus includes an IP Management setting under the CAPI options, offering three modes:

  1. Send RAW IP – Sends the IP as detected (IPv4 or IPv6), without modification. This is the default and most accurate option.
  2. Try to get IPv6 – Checks if the visitor's connection provides both IPv4 and IPv6. If an IPv6 is available, it sends that instead.
  3. Force IPv6 – Tries to detect IPv6; if not available, it converts the IPv4 to a compatible IPv6 format and sends that instead.

This gives you the flexibility to comply with Meta's recommendation without compromising data quality.

✅ Recommended: "Try to get IPv6"​

This option strikes the best balance: it respects the visitor’s real IP and sends IPv6 only if available, to check taht it performs a small check on a IPV6 validation site, without forcing artificial conversion. This will only bring IPV6 addresses if the user actually have one assigned.

Use this setting if you want to address Meta’s suggestion but avoid side effects from converting valid IPv4s.

📌 Important: This is only a recommendation​

Even if Meta flags this as a warning or optimization tip, it does not affect your Pixel or CAPI tracking accuracy.

The message is informational and does not imply that your setup is broken. If the customer has only an IPv4 address, there’s no technical way to provide Meta with something different — and that’s completely fine.

Meta includes this suggestion to encourage future compliance, but it’s not mandatory.

✅ Our recommendation​

  • If your visitors are primarily using IPv4, this message is expected and can be safely ignored.
  • To partially comply, enable the "Try to get IPv6" mode in the module.
  • Avoid "Force IPv6" unless you understand the risks of sending artificially converted IPs.
  • Don’t worry — your ad tracking and performance are not negatively affected by this.

If you need further help selecting the best option for your shop or want to test how the module behaves with different IPs, feel free to contact our support team.