Server Sending Invalid Match Key Parameters for ViewContent Event
-
Hi,
Since yesterday I have several problems that can be seen on the “Diagnostic” page of my Facebook Pixel (in Facebook Business Manager).
The pixel is installed on my website since a long time thanks to your plugin.
The problems are:
1) “Server Sending Invalid Match Key Parameters for ViewContent Event” : Your server is sending an invalid ip_address parameters value for your ViewContent event. This may be because there was an error in the parameter value.
This may cause issues with the attribution and delivery optimization of ad campaigns that are using this event.2) “External server ID does not match external pixel ID” : You are sending the external_ID parameter for your InitiateCheckout event from your server, but you are not sending the external_ID parameter for this event from your pixel. If you send an external_ID for an event from your server, you must also send it from your pixel for that event to be valid.
3) Same problem for ViewContent.
4) Same problem for ViewCategory.
Those problems must be due to your plugin because nothing has changed on my server.
Maybe it’s since the new 6.0.2 version of WordPress? Is your plugin compatible with this version?
Could you please solve those problems?Thank you very much.
The page I need help with: [log in to see the link]
-
Hi @fotske
Thanks for providing the details about the changes you are seeing recently. I understand that you suspect that these may be due to the recently released 6.0.2 version of WordPress.
I wasn’t able to replicate the issues on my test site which has the latest versions of both, so we may need to look for other causes.
As a first step can you please check if the solutions shared in this thread for the “Server Sending Invalid Match Key Parameters for ViewContent Event” error work for you? https://www.ads-software.com/support/topic/server-sending-invalid-match-key-parameters-7/
So that we can try to identify the overall cause better, could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. Once you’ve done that, paste it here in your response.
Hi,
I checked and applied the solutions shared in the thread that you sent me.
How can I verify if it works?And how can I send you my system status in a secure way?
Thank you very much for your help.
Hi @fotske!
I checked and applied the solutions shared in the thread that you sent me. How can I verify if it works?
Thanks for the update. Do you still get the warnings in your Facebook Pixel?
And how can I send you my system status in a secure way?
You can send your system status report here in the thread. There is no sensitive information there so it’s safe to share. You can read more about how to post code/info enclosed in backticks here:
https://www.ads-software.com/support/forum-user-guide/faq/#how-do-i-post-code-examples
We look forward to hearing from you.
Hi,
I don’t get the problems in the “Diagnostic” section of my pixel in Facebook Business Manager.
However, on my website, I checked the Facebook Pixel Helper and I have several warnings:
ViewContent WARNINGS We detected event code but the pixel has not activated for this event, so no information was sent to Facebook. This could be due to an error in the code, but could also occur if the pixel fires on a dynamic event such as a button click.Learn more EVENT INFO Setup Method: Manual Pixel Code: Show Pixel Location: Show Frame: Window PageView WARNINGS We detected event code but the pixel has not activated for this event, so no information was sent to Facebook. This could be due to an error in the code, but could also occur if the pixel fires on a dynamic event such as a button click.Learn more EVENT INFO Setup Method: Manual Pixel Code: Show Pixel Location: Show Frame: Window
Also, when I add a product to cart, the pixel does not seem to fire the “Add to cart” event (that’s a very annoying issue).
Could you please help solving those issues?
Here is the system status report:
### WordPress Environment ###WordPress address (URL): https://www.matcha-iro.com
Site address (URL): https://www.matcha-iro.com
WC Version: 6.8.2
REST API Version: ? 6.8.2
WC Blocks Version: ? 8.4.0
Action Scheduler Version: ? 3.4.0
Log Directory Writable: ?
WP Version: 6.0.2
WP Multisite: –
WP Memory Limit: 768 Mo
WP Debug Mode: –
WP Cron: –
Language: fr_FR
External object cache: ?### Server Environment ###
Server Info: Apache
PHP Version: 7.4.30
PHP Post Max Size: 256 Mo
PHP Time Limit: 120
PHP Max Input Vars: 4000
cURL Version: 7.66.0
OpenSSL/1.1.1q-fipsSUHOSIN Installed: –
MySQL Version: 5.7.39-42-log
Max Upload Size: 256 Mo
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: wpsx_
Taille totale de la base de données: 315.39MB
Taille de la base de données: 197.46MB
Taille de l’index: 117.93MB
wpsx_woocommerce_sessions: Données?: 1.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_woocommerce_api_keys: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_woocommerce_attribute_taxonomies: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_woocommerce_downloadable_product_permissions: Données?: 0.02MB + Index?: 0.06MB + Moteur InnoDB
wpsx_woocommerce_order_items: Données?: 0.42MB + Index?: 0.16MB + Moteur InnoDB
wpsx_woocommerce_order_itemmeta: Données?: 3.52MB + Index?: 4.03MB + Moteur InnoDB
wpsx_woocommerce_tax_rates: Données?: 0.02MB + Index?: 0.06MB + Moteur InnoDB
wpsx_woocommerce_tax_rate_locations: Données?: 0.02MB + Index?: 0.05MB + Moteur InnoDB
wpsx_woocommerce_shipping_zones: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_woocommerce_shipping_zone_locations: Données?: 0.02MB + Index?: 0.05MB + Moteur InnoDB
wpsx_woocommerce_shipping_zone_methods: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_woocommerce_payment_tokens: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_woocommerce_payment_tokenmeta: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_woocommerce_log: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_actionscheduler_actions: Données?: 1.52MB + Index?: 0.86MB + Moteur InnoDB
wpsx_actionscheduler_claims: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_actionscheduler_groups: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_actionscheduler_logs: Données?: 0.52MB + Index?: 0.39MB + Moteur InnoDB
wpsx_aepc_custom_audiences: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_aepc_logs: Données?: 23.52MB + Index?: 0.00MB + Moteur InnoDB
wpsx_commentmeta: Données?: 0.08MB + Index?: 0.03MB + Moteur InnoDB
wpsx_comments: Données?: 1.52MB + Index?: 0.81MB + Moteur InnoDB
wpsx_ee_products_sync_list: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_ee_product_sync_call: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_ee_product_sync_data: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_failed_jobs: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_feedmanager_channel: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_feedmanager_country: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_feedmanager_feed_status: Données?: 0.02MB + Index?: 0.08MB + Moteur InnoDB
wpsx_feedmanager_field_categories: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_feedmanager_product_feed: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_feedmanager_product_feedmeta: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_feedmanager_source: Données?: 0.02MB + Index?: 0.08MB + Moteur InnoDB
wpsx_icl_content_status: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_icl_core_status: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_icl_flags: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_icl_languages: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_icl_languages_translations: Données?: 0.19MB + Index?: 0.11MB + Moteur InnoDB
wpsx_icl_locale_map: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_icl_message_status: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_icl_mo_files_domains: Données?: 0.14MB + Index?: 0.05MB + Moteur InnoDB
wpsx_icl_node: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_icl_reminders: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_icl_strings: Données?: 8.52MB + Index?: 17.09MB + Moteur InnoDB
wpsx_icl_string_batches: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_icl_string_packages: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_icl_string_pages: Données?: 40.58MB + Index?: 57.17MB + Moteur InnoDB
wpsx_icl_string_positions: Données?: 0.08MB + Index?: 0.02MB + Moteur InnoDB
wpsx_icl_string_status: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_icl_string_translations: Données?: 8.52MB + Index?: 5.03MB + Moteur InnoDB
wpsx_icl_string_urls: Données?: 0.05MB + Index?: 0.02MB + Moteur InnoDB
wpsx_icl_translate: Données?: 19.52MB + Index?: 0.52MB + Moteur InnoDB
wpsx_icl_translate_job: Données?: 0.14MB + Index?: 0.08MB + Moteur InnoDB
wpsx_icl_translations: Données?: 0.22MB + Index?: 0.56MB + Moteur InnoDB
wpsx_icl_translation_batches: Données?: 0.05MB + Index?: 0.00MB + Moteur InnoDB
wpsx_icl_translation_downloads: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_icl_translation_status: Données?: 7.52MB + Index?: 0.06MB + Moteur InnoDB
wpsx_links: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_mailchimp_carts: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_mailchimp_jobs: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_optinrev: Données?: 0.03MB + Index?: 0.02MB + Moteur InnoDB
wpsx_options: Données?: 4.28MB + Index?: 0.20MB + Moteur InnoDB
wpsx_popover_ip_cache: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_postmeta: Données?: 13.52MB + Index?: 13.03MB + Moteur InnoDB
wpsx_posts: Données?: 3.52MB + Index?: 0.72MB + Moteur InnoDB
wpsx_queue: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_smush_dir_images: Données?: 0.02MB + Index?: 0.05MB + Moteur InnoDB
wpsx_termmeta: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_terms: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_term_relationships: Données?: 0.13MB + Index?: 0.13MB + Moteur InnoDB
wpsx_term_taxonomy: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_tm_taskmeta: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_tm_tasks: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_usermeta: Données?: 2.52MB + Index?: 3.03MB + Moteur InnoDB
wpsx_users: Données?: 0.11MB + Index?: 0.08MB + Moteur InnoDB
wpsx_wc_admin_notes: Données?: 0.08MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wc_admin_note_actions: Données?: 0.05MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wc_category_lookup: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wc_customer_lookup: Données?: 0.14MB + Index?: 0.13MB + Moteur InnoDB
wpsx_wc_download_log: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_wc_order_coupon_lookup: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_wc_order_product_lookup: Données?: 0.28MB + Index?: 0.34MB + Moteur InnoDB
wpsx_wc_order_stats: Données?: 0.17MB + Index?: 0.22MB + Moteur InnoDB
wpsx_wc_order_tax_lookup: Données?: 0.17MB + Index?: 0.16MB + Moteur InnoDB
wpsx_wc_product_attributes_lookup: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wc_product_download_directories: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wc_product_meta_lookup: Données?: 0.02MB + Index?: 0.09MB + Moteur InnoDB
wpsx_wc_rate_limits: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wc_reserved_stock: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wc_tax_rate_classes: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wc_webhooks: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wfBlockedIPLog: Données?: 0.05MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfBlocks7: Données?: 0.02MB + Index?: 0.05MB + Moteur InnoDB
wpsx_wfConfig: Données?: 10.47MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfCrawlers: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfFileChanges: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfFileMods: Données?: 15.55MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfHits: Données?: 2.02MB + Index?: 0.28MB + Moteur InnoDB
wpsx_wfHoover: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wfIssues: Données?: 0.02MB + Index?: 0.06MB + Moteur InnoDB
wpsx_wfKnownFileList: Données?: 7.52MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfLiveTrafficHuman: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wfLocs: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfLogins: Données?: 0.45MB + Index?: 0.19MB + Moteur InnoDB
wpsx_wfls_2fa_secrets: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_wfls_settings: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfNotifications: Données?: 0.09MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfPendingIssues: Données?: 0.02MB + Index?: 0.06MB + Moteur InnoDB
wpsx_wfReverseCache: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wfSNIPCache: Données?: 0.02MB + Index?: 0.05MB + Moteur InnoDB
wpsx_wfStatus: Données?: 9.02MB + Index?: 3.03MB + Moteur InnoDB
wpsx_wfTrafficRates: Données?: 0.02MB + Index?: 0.00MB + Moteur InnoDB
wpsx_wsal_metadata: Données?: 3.52MB + Index?: 6.03MB + Moteur InnoDB
wpsx_wsal_occurrences: Données?: 2.52MB + Index?: 0.52MB + Moteur InnoDB
wpsx_yoast_indexable: Données?: 1.52MB + Index?: 0.80MB + Moteur InnoDB
wpsx_yoast_indexable_hierarchy: Données?: 0.06MB + Index?: 0.05MB + Moteur InnoDB
wpsx_yoast_migrations: Données?: 0.02MB + Index?: 0.02MB + Moteur InnoDB
wpsx_yoast_primary_term: Données?: 0.02MB + Index?: 0.03MB + Moteur InnoDB
wpsx_yoast_seo_links: Données?: 0.48MB + Index?: 0.34MB + Moteur InnoDB
wpsx_yoast_seo_meta: Données?: 0.08MB + Index?: 0.00MB + Moteur InnoDB### Post Type Counts ###
amn_mi-lite: 2
attachment: 1183
boxzilla-box: 1
custom_css: 1
jetpack_migration: 2
jp_img_sitemap: 1
jp_sitemap: 1
jp_sitemap_master: 1
mc4wp-form: 4
nav_menu_item: 105
oembed_cache: 20
page: 113
portfolio: 60
product: 43
product_variation: 10
revision: 3
sg_optimizer_jobs: 27
shop_coupon: 120
shop_order: 1380
shop_order_refund: 4
wp_global_styles: 1
wprm_recipe: 1
wpsl_stores: 1021### Security ###
Secure connection (HTTPS): ?
Hide errors from visitors: ?### Active Plugins (41) ###
WPML Multilingual CMS: par OnTheGoSystems – 4.5.8
WPML SEO: par OnTheGoSystems – 2.0.1
AddToAny Share Buttons: par AddToAny – 1.8.5
Akismet Anti-Spam: par Automattic – 5.0
BackWPup: par Inpsyde GmbH – 3.10.0
Boxzilla: par ibericode – 3.2.25
Classic Editor: par Contributeurs et contributrices WordPress – 1.6.2
Conversios.io – Google Analytics and Google Shopping plugin for WooCommerce: par Conversios – 4.8.9
Envato Market: par Envato – 2.0.7
Facebook for WooCommerce: par Facebook – 2.6.21
Heartbeat Control par WP Rocket: par WP Rocket – 2.0
HookMeUp – Additional Content for WooCommerce: par GetBowtied – 1.3.5
Jetpack: par Automattic – 11.2
éditeur de page: par Michael M – WPBakery.com – 6.8.0
Loco Translate: par Tim Whitlock – 2.6.2
Mailchimp for WooCommerce: par Mailchimp – 2.7.3
MC4WP: Mailchimp for WordPress: par ibericode – 4.8.8
MC4WP: WPML compatibility: par ibericode – 1.0.3
Regenerate Thumbnails: par Alex Mills (Viper007Bond) – 3.1.5
SiteGround Optimizer: par SiteGround – 7.2.1
Shopkeeper Deprecated Features: par GetBowtied – 1.1.6
Shopkeeper Extender: par GetBowtied – 1.6.9
Shopkeeper Portfolio Addon: par GetBowtied – 1.3.5
WC MyParcel Belgium: par Richard Perdaan – 4.5.1
WooCommerce Blocks: par Automattic – 8.4.0
WooCommerce Stripe Gateway: par WooCommerce – 6.6.0
WooCommerce Multilingual & Multicurrency: par OnTheGoSystems – 5.0.2
Advanced Order Export Pour WooCommerce (Pro): par AlgolPlus – 3.3.2
WooCommerce: par Automattic – 6.8.2
Wordfence Security: par Wordfence – 7.6.0
Yoast SEO: par L’équipe Yoast – 19.6
WP Activity Log for WooCommerce: par WP White Security – 1.4.4
WP Product Feed Manager: par Michel Jongbloed – 1.43.0
WP Activity Log: par WP White Security – 4.4.2.1
Smush: par WPMU DEV – 3.11.1
WP Store Locator: par Tijmen Smit – 2.2.235
MailChimp for WordPress Multilingual: par OnTheGoSystems – 0.0.3
WPML Media: par OnTheGoSystems – 2.7.0
WPML Sticky Links: par OnTheGoSystems – 1.5.4
WPML String Translation: par OnTheGoSystems – 3.2.1
WPS Hide Login: par WPServeur
NicolasKulka
wpformation – 1.9.6### Inactive Plugins (0) ###
### Dropin Plugins (1) ###
object-cache.php: Memcached
### Settings ###
API Enabled: ?
Force SSL: ?
Currency: EUR (€)
Currency Position: left_space
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-nl)
rated-5 (rated-5)Connected to WooCommerce.com: –
Enforce Approved Product Download Directories: –### WC Pages ###
Base de la boutique: #5 – /shop/
Panier: #26018 – /panier-2/
Commander: #26019 – /commander/
Mon compte: #26020 – /mon-compte-2/
Conditions générales de vente et d’utilisation: #578 – /conditions-generales-de-vente/### Theme ###
Name: Shopkeeper Child
Version: 1.0
Author URL: http:%20//www.getbowtied.com/
Child Theme: ?
Parent Theme Name: Shopkeeper
Parent Theme Version: 2.9.91
Parent Theme Author URL: https://www.getbowtied.com/
WooCommerce Support: ?### Templates ###
Overrides: shopkeeper/woocommerce/archive-product.php
shopkeeper/woocommerce/checkout/form-coupon.php
shopkeeper/woocommerce/checkout/form-login.php
shopkeeper/woocommerce/content-product.php
shopkeeper/woocommerce/content-single-product.php
shopkeeper/woocommerce/global/quantity-input.php
shopkeeper/woocommerce/global/sidebar.php
shopkeeper/woocommerce/global/wrapper-end.php
shopkeeper/woocommerce/global/wrapper-start.php
shopkeeper/woocommerce/myaccount/form-login.php
shopkeeper/woocommerce/single-product/add-to-cart/simple.php
shopkeeper/woocommerce/single-product/product-image.php
shopkeeper/woocommerce/single-product/product-thumbnails.php
shopkeeper/woocommerce/single-product/tabs/tabs.php
shopkeeper/woocommerce/single-product.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
mobile-app-banner
navigation
onboarding
onboarding-tasks
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
wc-pay-promotion
wc-pay-welcome-page
wc-pay-subscriptions-pageDisabled Features: minified-js
settingsDaily Cron: ? Next scheduled: 2022-09-03 06:28:02 +02:00
Options: ?
Notes: 98
Onboarding: completed### Action Scheduler ###
Complete: 1?056
Oldest: 2022-08-02 13:30:03 +0200
Newest: 2022-09-02 12:03:12 +0200Failed: 4
Oldest: 2019-11-03 14:54:40 +0100
Newest: 2022-03-11 10:47:07 +0100Pending: 3
Oldest: 2022-09-02 14:30:05 +0200
Newest: 2022-09-04 11:02:33 +0200### Status report information ###
Generated at: 2022-09-02 12:33:13 +02:00
`Hi @fotske,
Thanks for sharing the warnings and your system status.
WARNINGS
We detected event code but the pixel has not activated for this event, so no information was sent to Facebook.Looking into those warnings, it seems that other users have seen those come up when an Adblocker is being used within the browser.
Can you please make sure that you have disabled all ad blocking extensions within the browser and check if this is resolved? You could also use an incognito/private browser window.
Keep us posted.
Hi,
I confirm that I don’t have any ad blocking extension within the browser (Google Chrome).
Thank you for your help for solving those issues.
Hello @fotske!
Thanks for getting back to us!
I confirm that I don’t have any ad blocking extension within the browser (Google Chrome).
As mentioned in this Facebook for WooCommerce FAQ section, some caching solutions can prevent some pixel events from firing up.
Please clear your cache and make sure to avoid grouping JS scripts as part of a caching plugin’s minification efforts.
Furthermore, please consult a WooCommerce best practices guide on configuring caching plugins here.
If caching is handled by your hosting provider instead of third-party plugins, you might want to reach out to your host to help you with the steps above.
If the above steps still don’t resolve the issue, please consider reconnecting your Facebook for WooCommerce plugin as suggested here and see if it helps.
Let us know how it turns out! We will be here.
Hi @tamirat22,
I managed to solve the “WARNINGS We detected event code but the pixel has not activated for this event” issue with the Facebook Pixel helper on my website.
The issue was caused by a Chrome extension (Bitdefender anti-tracker).However, I still have this error in the “Diagnostic” section of my pixel in Facebook Business Manager:
“Server Sending Invalid Match Key Parameters for ViewCategory Event
Your server is sending an invalid ip_address parameters value for your ViewCategory event. This may be because there was an error in the parameter value.
This may cause issues with the attribution and delivery optimization of ad campaigns that are using this event.” “Check that you’re sending valid and unique values for the ip_address parameters for your ViewCategory event and that the data is normalized correctly.”How can I solve this issue?
Thank you very much for your help.
Hi there @fotske ??
I managed to solve the “WARNINGS We detected event code but the pixel has not activated for this event” issue with the Facebook Pixel helper on my website.
The issue was caused by a Chrome extension (Bitdefender anti-tracker).That’s great to read! Thank you for letting us know.
However, I still have this error in the “Diagnostic” section of my pixel in Facebook Business Manager
Thanks for reporting the issue.
It looks like this is a similar issue that we have reported earlier and this issue is currently being investigated by our developers in this bug report:
https://github.com/woocommerce/facebook-for-woocommerce/issues/1777
As we have no further information to share other than what is in that report, we recommend subscribing to the report to follow the process. This step will allow you to be the first to find out when the bug is fixed.
You can subscribe by selecting this button on the GitHub repo (this will only be visible if you have a GitHub account, which can be done for free): https://cld.wthms.co/2EmX9K
Thank you ??
- The topic ‘Server Sending Invalid Match Key Parameters for ViewContent Event’ is closed to new replies.