Conversions API IPv6 mishandling

  • Hi there,

    Good job on the plugin, I’ve been using it for a while now and was very happy to see you add server-side tracking! I stumbled on a bug and wanted to give you a detailed report, so here it goes:

    Facebook events reports the following:

    AdvancedEvents Event sending invalid IP address parameter
The IP address associated with the [EVENT NAME] events sent from your server is invalid, so the data for all AdvancedEvents events sent from your server hasn't been received and can't be used for ads attribution or optimisation.
Without an IP address, this data can't be received or used for ads attribution or optimisation.

    I found the debug log in the logs section:

    ---- Report: 2021-02-14T11:38:25+00:00 ----

Exception: FacebookAds\Http\Exception\AuthorizationException

--------------------

Message: Server Side Event error: Invalid parameter

---- Context ----

{"code":100,"events":["{\"event_name\":\"AdvancedEvents\",\"event_time\":1613302705,\"event_source_url\":\"https:\\\/\\\/redacted\\\/\",\"event_id\":\"57f3c056-92e8-4e86-ae2c-07480cccc23a\",\"user_data\":{\"client_ip_address\":\"2600:1900:2001:10::a,66.102.6.174\",\"client_user_agent\":\"Mozilla\\\/5.0 (X11; Linux x86_64) AppleWebKit\\\/537.36 (KHTML, like Gecko) Chrome\\\/49.0.2623.75 Safari\\\/537.36 Google Favicon\"},\"custom_data\":{\"login_status\":\"not_logged_in\",\"post_type\":\"page\",\"object_id\":\"19\",\"object_type\":\"home\"},\"action_source\":\"website\"}"]}

    The “client_ip_address” seems to contain both an IPv6 and an IPv4 IP address for some weird reason, and facebook probably wants either-or (although the docs don’t really mention anything regarding IPv6 [https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters/#client-ip-address]).

Viewing 1 replies (of 1 total)
  • Plugin Author Antonino Scarfì

    (@antoscarface)

    Hi,

    thanks for reporting this and thank you for sharing the report, it was very helpful!

    In your case, that’s not actually an IPv6 problem, but you have a mix of both IPs, read with attention: 2600:1900:2001:10::a,66.102.6.174

    There are both IPs, separated by a comma, which is the first time I see it.

    At this point, some servers are sending both IP versions together to PHP.

    I’ll fix it in the next version of Pixel Caffeine. Unfortunately, I don’t have any workaround at the moment, but hopefully, I’ll release the new version within this week.

Viewing 1 replies (of 1 total)
  • The topic ‘Conversions API IPv6 mishandling’ is closed to new replies.