• Resolved Epsiloncool

    (@epsiloncool)


    Hello, today Facebook reported that two events registered by Facebook Pixel installed by your plugin have sent some private information from the page URL. Before that, I have removed the pixel code and all my other FB-related code in order to let your awesome plugin make the dirty job.

    The event names are PageView and Purchase and the link is such:

    https://fulltextsearch.org/checkout/order-received/136124/?key=_removed_&utm_nooverride=_removed_&PayerID=_removed_&ul=_removed_&lite=_removed_&token=_removed_&useraction=_removed_&rm=_removed_&mfid=_removed_&rcache=_removed_&country.x=_removed_&locale.x=_removed_&payer_email=_removed_&payer_id=_removed_&payer_status=_removed_&first_name=_removed_&last_name=_removed_&txn_id=_removed_&mc_currency=_removed_&mc_fee=_removed_&mc_gross=_removed_&protection_eligibility=_removed_&payment_fee=_removed_&payment_gross=_removed_&payment_status=_removed_&payment_type=_removed_&handling_amount=_removed_&shipping=_removed_&tax=_removed_&item_name1=_removed_&quantity1=_removed_&mc_gross_1=_removed_&tax1=_removed_&num_cart_items=_removed_&txn_type=_removed_&payment_date=_removed_&business=_removed_&receiver_id=_removed_&notify_version=_removed_&custom=_removed_&invoice=_removed_&verify_sign=_removed_&amt=_removed_&cc=_removed_&cm=_removed_&st=_removed_&tx=_removed_&_filteredParams=%7B%22unwantedParams%22%3A%5B%22first_name%22%2C%22last_name%22%5D%2C%22sensitiveParams%22%3A%5B%5D%7D

    As you can see this link is generated by Woocommerce when the order is successful and the FB Pixel somehow sends this URL to Facebook, which is restricted.

    I guess we need to remove some parts of this URL before sending the info to the FB, but I don’t really understand how to make that, because everything is controlled now by your plugin.

    Could you share some ideas, please?

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi @epsiloncool,

    The notice from Facebook is quite strange. For context, we haven’t had similar reports about this. I’m not seeing any open issues about this in the plugin’s GitHub repository either, so this seems very specific to your particular site setup.

    To start, I do see that there is only one pixel on your checkout page, but do you perhaps have any other customizations there that may be causing Facebook to detect what they see as a violation?

    For instance, on my test sites, the Event URL passed to Facebook is much shorter compared to the example you gave. It’s only like this:

    https://***.com/checkout/order-received/616/?client_secret=_removed_&key=_removed_&livemode=_removed_&order_id=616&redirect_status=_removed_&source=_removed_&utm_nooverride=_removed_

    Thread Starter Epsiloncool

    (@epsiloncool)

    Hi @dcka

    Yes, I think that one payment plugin (Paypal in particular) may return a lot of information in URL after the payment on its side. Actually, there is at the website may be more things (plugins, etc) that use URL to pass client’s information between pages.

    The question is a bit different: how I need to configure FB Pixel code to force pixel to remove some sensitive information from the URL BEFORE sending it to Facebook?

    I know this can be solved in a different way: e.g. by finding the place in a plugin that adds parameters to URL and encode the data before placing it in URL and then by changing another code that uses URL to get parameters and add decode procedure there, but it feels like a bit dumb solution. There should be a way to limit data for Pixel instead.

    Thank you for your support!

    Hi @epsiloncool,

    The question is a bit different: how I need to configure FB Pixel code to force pixel to remove some sensitive information from the URL BEFORE sending it to Facebook?

    We don’t have a specific way to configure this by default with Facebook for WooCommerce.

    Here I found a link to a third party article describing a similar case to yours:

    https://www.pixelyoursite.com/event-violates-business-tools-terms

    I hope this helps.

    Hi, @epsiloncool! We haven’t heard back from you in a while, so I’m going to mark this thread as resolved. However, we’ll be here if/when you’re ready to continue.

    Thread Starter Epsiloncool

    (@epsiloncool)

    Hi @dcka

    This warning magically disappeared from the Facebook Business page and I stopped the solving issue.

    Thank you for the help!

    Hi @epsiloncool

    I am glad to hear the warning disappeared.

    If it happens again, please do let us know!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘PageView Event Violates Business Tools Terms’ is closed to new replies.