Meta Asks for IPv6 in Event Tracking
If you're seeing a message from Meta (Facebook) suggesting that your site should send events using IPv6 instead of IPv4, this guide will help clarify what it means, why it's not always possible, and how Pixel Plus offers solutions to align with this recommendation.
This is not an error, a bug in the module or something that needs to be fixed —it's related to the type of IP address your customers have, and the way the Facebook Pixel and Conversion API (CAPI) collect and process this information.
🌐 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 reflects 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:
- Send RAW IP – Sends the IP as detected (IPv4 or IPv6), without modification. This is the default and most accurate option.
- Try to get IPv6 – Checks if the visitor's connection provides both IPv4 and IPv6. If an IPv6 is available, it sends that instead.
- 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 that 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.
Is the Meta IPv6 recommendation an error I need to fix?
No. This is an informational suggestion from Meta, not an error. Your pixel and CAPI tracking accuracy are not affected. Meta encourages IPv6 for future compatibility, but IPv4 is still dominant globally and is fully supported.
Why is my store sending IPv4 even though IPv6 exists?
Most internet users in Europe and other regions still receive IPv4 addresses from their ISPs. Even if your server supports IPv6, the customer's actual IP seen by the module is typically IPv4. This reflects current internet infrastructure, not a module bug.
Which IP mode in Pixel Plus is recommended to partially address the IPv6 suggestion?
Use the IPv6 If Available mode. This checks whether the visitor genuinely has an IPv6 address and sends it only if confirmed. For visitors without IPv6, it falls back to their real IPv4 address without any conversion.
Why should I avoid Force IPv6?
Force IPv6 converts IPv4 addresses to an IPv6-mapped format when a real IPv6 is unavailable. This creates a mismatch with the Pixel's automatic IP capture, which records the real IPv4, and typically generates more diagnostic warnings rather than fewer.
Will changing the IP mode improve my ad performance or ROAS?
No. IP mode affects only how Meta records the IP field in event data. It does not directly influence ad delivery, bidding, or ROAS. Focus on match quality score and conversion tracking accuracy instead.
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.