wc_order Facebook violation
-
Hello everyone, I have a big problem with Facebook..
It reports a violation of health data in the urls of the orders received…
In practice, I believe that Facebook “believes” that in the url of the orders received there are health data of the buyers ..
The url of the order received contains …../?key=wc_order_…..
Facebook remove the part “wc_order” In fact he signals it to me like this …../?key=_removed_……..
Inserts _removed_ Instead of wc_order..
What health data does Facebook see? I ignore it, maybe he thinks I sell wc?
The strange thing is that, I think, this url is the same for all sites based on woocommerce so hypothetically I should find dozens of guides about the problem instead I can’t find anything……
I don’t go any further and ask if PLEASE can anyone tell me what’s going on or what I have to do or maybe how to change that part of url?
THANK YOU!
-
Hi there @achillem ??
Hello everyone, I have a big problem with Facebook..
It reports a violation of health data in the urls of the orders received…
Thanks for reaching out about this. I am not sure that I understand what you are describing, could you clarify further, please?
From what I gather, you are saying that Facebook is being fed the received order’s URL and is reporting violations of health data because of it?
What kind of connection is set up between your WooCommerce store and Facebook? Kindly explain further.
Could you please share a copy of your site’s System Status? You can find it via
WooCommerce > Status
. SelectGet system report
and thenCopy for support
.?Additionally, could you also provide us with the fatal error logs (if any) under
WooCommerce > Status > Logs
.Once you’ve copied each, you can either paste them in your response here, or use https://pastebin.com/ for pasting it there and sharing it with us.
Looking forward to hearing from you!
Hi and thank you for your interest.. I write from Italy and I hope to be quite clear ..
I have the Facebook pixel installed on the site, https://www.paracelsus.it, and Facebook warns me that I am sending customer health data, clearly it is not true, it is a Facebook error but talk to Facebook is impossible .. I have to solve the problem myself ..
Here’s what facebook tells me:
Il problema “Controlla i contenuti “dati sanitari” potenzialmente in violazione” è stato riscontrato negli eventi provenienti dall’URL riportato di
seguito….I translate with the translator:
The ‘Check potentially infringing ‘health data’ content’ issue was found in events from the reported following URL …
The url in question reported by Facebook:
The full url is as follows:
https://www.paracelsus.it/cassa/order-received/18814/?key=wc_order_yLQgirXLr9wAO&utm_nooverride=1
As you can see, the part removed is wc_order_yLQgirXLr9wAO
Then you ask me to share site’s System Status
I can do this right here or I have to send you site’s System Status in private?
Ok, hoping not to share sensitive data I share the site’s system status.. `
### WordPress Environment ###
WordPress address (URL): https://www.paracelsus.it
Site address (URL): https://www.paracelsus.it
WC Version: 7.0.0
REST API Version: ? 7.0.0
WC Blocks Version: ? 8.5.1
Action Scheduler Version: ? 3.4.0
Log Directory Writable: ?
WP Version: 6.0.3
WP Multisite: –
WP Memory Limit: 768 MB
WP Debug Mode: –
WP Cron: ?
Language: it_IT
External object cache: –### Server Environment ###
Server Info: Apache
PHP Version: 7.4.32
PHP Post Max Size: 256 MB
PHP Time Limit: 120
PHP Max Input Vars: 3000
cURL Version: 7.66.0
OpenSSL/1.1.1q-fipsSUHOSIN Installed: –
MySQL Version: 5.7.39-42-log
Max Upload Size: 256 MB
Default Timezone is UTC: ?
fsockopen/cURL: ?
SoapClient: ?
DOMDocument: ?
GZip: ?
Multibyte String: ?
Remote Post: ?
Remote Get: ?### Database ###
WC Database Version: 6.8.2
WC Database Prefix: hgb2ya_
Dimensione totale database: 326.53MB
Dimensione dati database: 175.81MB
Dimensione indice database: 150.72MB
hgb2ya_woocommerce_sessions: Dati: 4.02MB + indice: 0.08MB + motore InnoDB
hgb2ya_woocommerce_api_keys: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_woocommerce_attribute_taxonomies: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_woocommerce_downloadable_product_permissions: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
hgb2ya_woocommerce_order_items: Dati: 2.52MB + indice: 1.52MB + motore InnoDB
hgb2ya_woocommerce_order_itemmeta: Dati: 17.55MB + indice: 21.03MB + motore InnoDB
hgb2ya_woocommerce_tax_rates: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
hgb2ya_woocommerce_tax_rate_locations: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_woocommerce_shipping_zones: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_woocommerce_shipping_zone_locations: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_woocommerce_shipping_zone_methods: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_woocommerce_payment_tokens: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_woocommerce_payment_tokenmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_woocommerce_log: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_actionscheduler_actions: Dati: 3.02MB + indice: 2.73MB + motore InnoDB
hgb2ya_actionscheduler_claims: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_actionscheduler_groups: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_actionscheduler_logs: Dati: 2.52MB + indice: 1.94MB + motore InnoDB
hgb2ya_aws_cache: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_aws_index: Dati: 3.11MB + indice: 3.23MB + motore InnoDB
hgb2ya_chaty_contact_form_leads: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_commentmeta: Dati: 0.08MB + indice: 0.09MB + motore InnoDB
hgb2ya_comments: Dati: 14.52MB + indice: 13.09MB + motore InnoDB
hgb2ya_db7_forms: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_dokan_announcement: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_dokan_orders: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_dokan_refund: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_dokan_reverse_withdrawal: Dati: 0.02MB + indice: 0.08MB + motore InnoDB
hgb2ya_dokan_vendor_balance: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_dokan_withdraw: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_duplicator_packages: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_e_events: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_e_notes: Dati: 0.02MB + indice: 0.17MB + motore InnoDB
hgb2ya_e_notes_users_relations: Dati: 0.02MB + indice: 0.05MB + motore InnoDB
hgb2ya_e_submissions: Dati: 0.02MB + indice: 0.27MB + motore InnoDB
hgb2ya_e_submissions_actions_log: Dati: 0.02MB + indice: 0.11MB + motore InnoDB
hgb2ya_e_submissions_values: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_gla_budget_recommendations: Dati: 0.22MB + indice: 0.14MB + motore InnoDB
hgb2ya_gla_merchant_issues: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_gla_shipping_rates: Dati: 0.02MB + indice: 0.05MB + motore InnoDB
hgb2ya_gla_shipping_times: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_itsec_bans: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_itsec_dashboard_events: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_itsec_distributed_storage: Dati: 11.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_itsec_fingerprints: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_itsec_geolocation_cache: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_itsec_lockouts: Dati: 0.02MB + indice: 0.08MB + motore InnoDB
hgb2ya_itsec_logs: Dati: 2.02MB + indice: 0.11MB + motore InnoDB
hgb2ya_itsec_mutexes: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_itsec_opaque_tokens: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_itsec_temp: Dati: 0.02MB + indice: 0.06MB + motore InnoDB
hgb2ya_itsec_user_groups: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_links: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_mpsl_sliders: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_mpsl_sliders_preview: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_mpsl_slides: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_mpsl_slides_preview: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_options: Dati: 7.17MB + indice: 1.55MB + motore InnoDB
hgb2ya_postmeta: Dati: 55.59MB + indice: 61.17MB + motore InnoDB
hgb2ya_posts: Dati: 6.52MB + indice: 3.73MB + motore InnoDB
hgb2ya_shipment_batch_process: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_short_links: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_short_link_clicks: Dati: 0.06MB + indice: 0.02MB + motore InnoDB
hgb2ya_short_link_replacements: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_squalomail_carts: Dati: 1.03MB + indice: 0.00MB + motore InnoDB
hgb2ya_squalomail_jobs: Dati: 0.14MB + indice: 0.00MB + motore InnoDB
hgb2ya_termmeta: Dati: 0.06MB + indice: 0.06MB + motore InnoDB
hgb2ya_terms: Dati: 0.05MB + indice: 0.03MB + motore InnoDB
hgb2ya_term_relationships: Dati: 0.06MB + indice: 0.05MB + motore InnoDB
hgb2ya_term_taxonomy: Dati: 0.06MB + indice: 0.03MB + motore InnoDB
hgb2ya_tm_taskmeta: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_tm_tasks: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_usermeta: Dati: 17.55MB + indice: 18.06MB + motore InnoDB
hgb2ya_users: Dati: 1.52MB + indice: 0.77MB + motore InnoDB
hgb2ya_wc_admin_notes: Dati: 0.06MB + indice: 0.00MB + motore InnoDB
hgb2ya_wc_admin_note_actions: Dati: 0.05MB + indice: 0.02MB + motore InnoDB
hgb2ya_wc_category_lookup: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_wc_customer_lookup: Dati: 1.52MB + indice: 1.75MB + motore InnoDB
hgb2ya_wc_download_log: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_wc_order_coupon_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_wc_order_product_lookup: Dati: 2.52MB + indice: 1.41MB + motore InnoDB
hgb2ya_wc_order_stats: Dati: 2.52MB + indice: 0.92MB + motore InnoDB
hgb2ya_wc_order_tax_lookup: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_wc_product_attributes_lookup: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_wc_product_download_directories: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_wc_product_meta_lookup: Dati: 0.05MB + indice: 0.09MB + motore InnoDB
hgb2ya_wc_rate_limits: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_wc_reserved_stock: Dati: 0.02MB + indice: 0.00MB + motore InnoDB
hgb2ya_wc_tax_rate_classes: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_wc_webhooks: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_woo_shippment_provider: Dati: 0.06MB + indice: 0.00MB + motore InnoDB
hgb2ya_wpil_report_links: Dati: 0.08MB + indice: 0.03MB + motore InnoDB
hgb2ya_yith_wcwl: Dati: 0.05MB + indice: 0.02MB + motore InnoDB
hgb2ya_yith_wcwl_lists: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_yoast_indexable: Dati: 2.52MB + indice: 1.08MB + motore InnoDB
hgb2ya_yoast_indexable_hierarchy: Dati: 0.06MB + indice: 0.05MB + motore InnoDB
hgb2ya_yoast_migrations: Dati: 0.02MB + indice: 0.02MB + motore InnoDB
hgb2ya_yoast_primary_term: Dati: 0.02MB + indice: 0.03MB + motore InnoDB
hgb2ya_yoast_seo_links: Dati: 14.55MB + indice: 14.03MB + motore InnoDB
hgb2ya_yoast_seo_meta: Dati: 0.08MB + indice: 0.00MB + motore InnoDB### Post Type Counts ###
attachment: 393
custom_css: 2
elementor_library: 1
elementor_snippet: 1
itsec-dash-card: 6
itsec-dashboard: 1
mailpoet_page: 1
nav_menu_item: 54
oembed_cache: 48
page: 28
post: 94
product: 134
product_variation: 18
revision: 169
shop_order: 15496
shop_order_refund: 22
wafs: 11
wc_mmqw: 1
wpcf7_contact_form: 2### Security ###
Secure connection (HTTPS): ?
Hide errors from visitors: ?### Active Plugins (46) ###
Advanced Custom Fields: by WP Engine – 6.0.2
Advanced Woo Search: by ILLID – 2.65
FiboSearch – AJAX Search for WooCommerce: by FiboSearch Team – 1.20.0
iThemes Security: by iThemes – 8.1.3
Chaty: by Premio – 3.0.1
Classic Editor: by Contributori WordPress – 1.6.2
Piattaforma Clearpay per Woocommerce: by Clearpay – 3.4.4
Contact Form 7: by Takayuki Miyoshi – 5.6.3
Contact Form CFDB7: by Arshid – 1.2.6.4
Disable Comments: by WPDeveloper – 2.4.2
Elementor Pro: by Elementor.com – 3.7.2
Elementor: by Elementor.com – 3.7.8
Facebook for WooCommerce: by Facebook – 2.6.27
Flexible Checkout Fields: by WP Desk – 3.4.3
GA Google Analytics: by Jeff Starr – 20221016
Google Listings and Ads: by WooCommerce – 2.1.4
Site Kit by Google: by Google – 1.85.0
Cookie and Consent Solution for the GDPR & ePrivacy: by iubenda – 3.2.5
Loco Translate: by Tim Whitlock – 2.6.2
Microsoft Advertising Universal Event Tracking (UET): by Microsoft Corporation – 1.0.4
Responsive WordPress Slider Lite: by MotoPress – 2.2.0
URL Shortener by MyThemeShop: by MyThemeShop – 1.0.16
Facebook for WordPress: by Facebook – 3.0.7
Pinterest per WooCommerce: by WooCommerce – 1.2.4
Remove Yoast SEO Comments: by Mitch – 3.1
WooCommerce Real Time Shipping Rates: by ShippyPro – 0.0.8
Squalomail for WooCommerce: by Squalomail – 2.5.1
Sucuri Security – Auditing, Malware Scanner and Hardening: by Sucuri Inc. – 1.8.35
Themebeez Toolkit: by themebeez – 1.2.5
User Menus: by Code Atlantic – 1.3.0
Monitoraggio avanzato della spedizione per WooCommerce: by zorema – 3.4.7
Min Max Quantity & Step Control for WooCommerce: by CodeAstrology Team – 3.2
Woo Reviews for Google: by ICREATOR – 1.0
WooCommerce Satispay: by Satispay – 2.1.0
WooCommerce Advanced Free Shipping: by Jeroen Sormani – 1.1.5
WooCommerce Extra Charges To Payment Gateway (Standard): by hemsingh1 – 1.0.12.9
WooCommerce Amazon Pay: by WooCommerce – 2.3.0
WooCommerce Google Analytics Integration: by WooCommerce – 1.5.15
WP Menu Cart: by WP Overnight – 2.12.1
Advanced Order Export For WooCommerce (Pro): by AlgolPlus – 3.3.1
WooCommerce Payments: by Automattic – 4.8.1 (aggiornamento alla versione 4.9.0 disponibile)
WooCommerce Product Categories Selection: by PluginForage.com – 2.0
WooCommerce Shortcodes: by WooThemes
Claudio Sanches – 1.0.0WooCommerce: by Automattic – 7.0.0
Yoast SEO: by Team Yoast – 19.8
WP-Paginate: by Max Foundry – 2.1.9### Inactive Plugins (1) ###
UpdraftPlus – Backup/Restore: by UpdraftPlus.Com
DavidAnderson – 1.22.23### Settings ###
API Enabled: ?
Force SSL: –
Currency: EUR (€)
Currency Position: right
Thousand Separator: .
Decimal Separator: ,
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
variable (variable)Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)Connected to WooCommerce.com: ?
Enforce Approved Product Download Directories: –### WC Pages ###
Shop base: #6 – /shop/
Carrello: #7 – /carrello/
Pagamento: #8 – /cassa/
Il mio account: #1426 – /il-tuo-account/
Termini e condizioni: #1434 – /termini-e-condizioni/### Theme ###
Name: Orchid Store
Version: 1.3.4 (aggiornamento alla versione 1.3.9 disponibile)
Author URL: https://themebeez.com
Child Theme: ? – Se stai modificando WooCommerce o un tema genitore che non hai costruito personalmente
ti consigliamo di utilizzare un tema child. Vedi: Come creare un tema childWooCommerce Support: ?
### Templates ###
Overrides: orchid-store/woocommerce/archive-product.php
orchid-store/woocommerce/content-product.php
orchid-store/woocommerce/global/wrapper-end.php
orchid-store/woocommerce/global/wrapper-start.php
orchid-store/woocommerce/loop/loop-start.php
orchid-store/woocommerce/loop/sale-flash.php
orchid-store/woocommerce/product-searchform.php### Admin ###
Enabled Features: activity-panels
analytics
coupons
customer-effort-score-tracks
experimental-products-task
experimental-import-products-task
experimental-fashion-sample-products
experimental-product-tour
shipping-smart-defaults
shipping-setting-tour
homescreen
marketing
multichannel-marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-pageDisabled Features: minified-js
new-product-management-experience
settingsDaily Cron: ? Next scheduled: 2022-11-02 09:42:13 +01:00
Options: ?
Notes: 113
Onboarding: completed### WooCommerce Payments ###
Version: 4.8.1
Connected to WPCOM: Sì
Blog ID: *************
Account ID: *******************### Action Scheduler ###
Operazione annullata: 6
Oldest: 2022-10-02 21:17:33 +0200
Newest: 2022-10-31 21:18:56 +0100Completato: 4.974
Oldest: 2022-10-05 09:19:48 +0200
Newest: 2022-11-01 11:58:51 +0100Operazione non riuscita: 23
Oldest: 2022-03-22 21:45:07 +0100
Newest: 2022-10-14 15:20:03 +0200In attesa: 5
Oldest: 2022-11-01 13:31:38 +0100
Newest: 2022-11-02 00:10:54 +0100### Status report information ###
Generated at: 2022-11-01 12:25:07 +01:00
`
- This reply was modified 2 years ago by Achillem.
I can’t find fatal errors..
Hi there @anastas10s ?? I sent you what you asked me, what can you tell me?
Hello,
Thanks for sending the system report, no worries it does not contain sensitive info.
When checking the system report, it shows the following:
WC Database Version: 6.8.2
Please update the database, navigate to WooCommerce > status > tools > update database.
Facebook for WooCommerce: by Facebook – 2.6.27
Please navigate to WP Dashboard > plugins > installed plugins > locate Facebook for WooCommerce, and update it.
I have the Facebook pixel installed on the site, https://www.paracelsus.it, and Facebook warns me that I am sending customer health data, clearly it is not true, it is a Facebook error but talk to Facebook is impossible .. I have to solve the problem myself ..
To get a better idea, you can send us a screenshot about this part, you can send it using https://snipboard.io. Then please provide the screenshot URL in your response.
Let us know, thanks.
Hello @ihereira and thank you for your help.. I hope I understand.. Do you want to see Facebook alerts?..
Here they are..
https://snipboard.io/m842jz.jpg
- This reply was modified 2 years ago by Achillem.
Hi @achillem
Facebook for WooCommerce: by Facebook – 2.6.27 Facebook for WordPress: by Facebook – 3.0.7
I can see that you have two Facebook plugins here. Can you please try to disable
Facebook for WordPress
and replicate the scenario and see if this resolves the issue?Let us know how it goes!
Hi @xue28 and thank you very much for your interest.. I have deactivated Facebook for WordPress: by Facebook, called Meta pixel for WordPress.
Now I am testing events from Facebook but both with Meta pixel for WordPress activated and deactivated the purchase events are not detected, ad to cart yes, page view yes but purchase is not really detected .. I don’t know what to think..
But don’t you think it’s enough to change the url that Facebook sees as a violation? It would only be the part that contains wc_order
Hi there @achillem,
With the Facebook for WooCommerce plugin, you can install the Facebook pixel, upload your online store catalog, and create a shop on your Facebook page, enabling you to easily run dynamic ads.
Thanks for confirming that you have deactivated
Facebook for WordPress
; could you confirm you have updated Facebook for WooCommerce to the latest version?Now I am testing events from Facebook but both with Meta pixel for WordPress activated and deactivated the purchase events are not detected, ad to cart yes, page view yes but purchase is not really detected .. I don’t know what to think..
Meta has the How do I see insights for my Facebook Page’s orders? document available on this, feel free to check it out.
But don’t you think it’s enough to change the url that Facebook sees as a violation? It would only be the part that contains wc_order
For going ahead with changing the
wc_order
from the URL, feel free to try out the code referenced here.A plugin like Code Snippets makes it straight forward, for using it on your site.
@anastas10s Ladies and Gentlemen, thankyou very much for your support! Following your answers I have made some tests and I am hoping to have achieved some improvements I have managed to create new events thanks to the facebook tool for creating events. Now I have tested them and they seem to work and there are no warnings .. The only warning is for add to cart generated by the plugin Facebook for woocommerce, it tells me that the article is not present in the catalog but unfortunately I cannot use the catalog, I will explain later why .. Now, since I have set the events manually and considering that I can’t use the catalog I’m considering also to deactivate plugin Facebook for woocomerce, what do you think? Maybe it’s the best solution, I’m just afraid that disabling the Facebook plugin will take time to get my ads going but unfortunately I have to see that the results are poor .. So I think I’ll do it, what do you think?`Thank you all again..
- This reply was modified 2 years ago by Achillem.
Now, I would like to explain why I can’t use catalog. I need to explain because it’ s more than one year that I have a big problem..
I can’t use catalog because when I implemented it Facebook blocked it because they are food supplements and Facebook says that they are of dubious safety, I am a pharmacist and I know what I sell, I do it in full compliance with the rules and I think that Facebook should respect professionals more.
After some times Facebook closed my facebook page without warning and without explanations, it happened in a bad moment, when I was already experiencing a sharp decline in sales ..
Closing the page made me lose all the contacts acquired, up to then, 10000 likes and blocked all my ads. After this I recorded a drastic drop in performance that has not yet recovered ..
As I said I was already recording the decline in sales before the facebook page closure but no one was able to help me. I think that all started when things were going better, instead of relaxing I thought bad I wanted to grow and I turned to an advertising agency for google ads, because facebook was doing very well, so I disconnected the google ads and I left this agency to manage google ads .. After 3 months of swooping results I decided to put the situation back in my hand but there was no way to raise sales.
Even the traffic hasn’t recovered since then .. I’m afraid it was all the fault of this advertising agency but I can’t even imagine how it could have done .. At first I think they copied what I was doing on facebook ads because I they asked too many questions about this but there is no explanation for the drop in sales and traffic.
It is true that I do not know any experts in the sector, my webmaster is a site designer and does not know what to tell me. Among my friends and acquaintances there are no experts in the sector, on the contrary they do not know exactly what I do.
I sought the help of some other agencies but they only stole money from me.
I don’t think the problem was caused only from facebook but in my opinion the problem is in the site. Do you have any suggestions for me to understand what could have happened?
I apologize if I’m digressing and if I’ve written too much but I desperately need help.
Hello,
Facebook blocked it because they are food supplements and Facebook says that they are of dubious safety, I am a pharmacist and I know what I sell
While I understand your point, please note that Facebook has its own e-commerce policy, that you can check here. Unfortunately, we are unable to change it.
I’m considering also to deactivate plugin Facebook for WooCommerce, what do you think? Maybe it’s the best solution
This will depend on your own needs, I mean you will need to evaluate what is better for your business model, Facebook for WooCommerce offers some benefits to users that you can check in this page.
That will depend as well on how you configure your catalog. Or how the collections are configured, that way you can only sync certain products to the Facebook Platform.
I hope this helps.
Ok, Facebook has its own e-commerce policy and of course we can’t change it but facebook accepts food supplements, of course it does, for some it says they are ok for others says that a are of dubious safety. Who decides this? It is not consistent with itself. Also, if you see the problem I have now, Facebook says that I am sending health data of my clients, it is absolutely not true! Facebook is only good at taking the money for the rest it doesn’t care that we have to live with that money and this is not good. This is not FarmVille.
@ihereira of course you helped me with your support, thank you very much.
Hello @achillem.
Sorry to hear this, I wish we could’ve done something but it’s not from our side.
I will recommend you take the matter to Facebook and try to explain this to them in a very detailed manner.
I will go ahead and mark the thread as solved. If you have a few minutes, we’d love it if you could leave us a review: https://www.ads-software.com/support/plugin/woocommerce/reviews/
Cheers!
- The topic ‘wc_order Facebook violation’ is closed to new replies.