Potentially Violating Personal Data Sent to Facebook: Event Purchase first_name

Hello,

This is usually related to a mandatory parameter for server events called event_source_url. This parameter must send the URL where the event takes place.

There are cases where your URL will contain parameters like the ones you just mentioned, and Facebook will show this kind of waring.

To avoid the problem, starting version 8.1.1 we filter all URL parameters for event_source_url by default.

So the solution is to update the plugin to the latest version and mark the problem as fixed.

Hi.
Thanks for getting back to me so quickly.
Your plugin has been very useful by the way… I’m using the free version.
Thanks for that!

The problem is that I’ve already updated to the current Version 8.2.0.
I also cleared the WP Rocket cache.

Do you have any recommendations what to do next?

I found this article on your website
https://www.pixelyoursite.com/event-violates-business-tools-terms?fbclid=IwAR0kTuDgKl-QnV-8vtgyz5p6Yctb96fk-CAzMwanFunHaab0__TXXKLvNRM

I didn’t find the location where to disable ‘Enable the ClickEvent on Facebook’
and I’m also not sure if this is the next step I would have to take.

Thanks again. I appreciate the help.
Michael

Chances are that the warning is related to some older data, because your current version doesn’t send URL parameters anymore for serve events.

The article refers to an old and paid feature. It’s been replaced by the Signal event. However, the free version will not fire the Signal event for clicks, this is available with the pro plugin only.

The only option you might want to change is the one referring to event_url parameter. You can find it on the plugin’s main page, at the bottom. But even here we no longer send URL parameters by default.

I’m having the same issue and I installed your plugin did 3 days. I’m using latest version.
Facebook alert:
Event: PageView
first_name
last_name
Last detection was yesterday of this issue.

Same problem, here with version FREE 8.2.11

PageView
Parametro URL della query:
first_name
Yesterday at 19:07
Parametro URL della query:
last_name
Yesterday at 19:07
Purchase
Parametro URL della query:
first_name
Yesterday at 19:07
Parametro URL della query:
last_name
Yesterday at 19:07

url sent revealed by FB:

https://website.ext/checkout/order-received/5271/?key=_removed_&utm_nooverride=_removed_&PayerID=_removed_&st=_removed_&tx=_removed_&cc=_removed_&amt=_removed_&cm=_removed_&payer_email=_removed_&payer_id=_removed_&payer_status=_removed_&first_name=_removed_&last_name=_removed_&address_name=_removed_&address_street=_removed_&address_city=_removed_&address_state=_removed_&address_country_code=_removed_&address_zip=_removed_&residence_country=_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_&item_name1=_removed_&item_number1=_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_&_filteredParams=_removed_

How we can fix that?

• This reply was modified 3 years ago by pixelmm.

The only way to fix it is to stop using those parameters in the URLs.

The Facebook pixel automatically takes the URLs for the browsers events, and there is nothing on our end we can do about it. We don’t send them for the server events.

However, most of the time is virtually impossible to get read of those parameters, they are used by some payment processing plugin.

The good new is that the only consequence is that Facebook removes the parameters and don’t let you use them for Custom Conversions or Custom Audiences. Nothing else.

hi, is there a way to disable in the url passed to facebook these parameters?

first_name
last_name

I’ve updated to the latest version and i don’t find anymore the way to disable these 2 parameters

Unfortunately there is no easy fix for this one. We don’t send those parameters, but Facebook do gets them automatically for their browser events.

More details in this video: https://www.youtube.com/watch?v=sM9yNkBK6Eg