PixelYourSite PRO - Best Powerful WordPress Plugin for FaceBook 11.1.0 Nulled

New options related to our native Google Tags data layer are available on the Google Tags Settings page. You can choose between our default names (dataLayerPYS – RECOMMENDED), the usual name, dataLayer (it can create conflicts when using our native tags along our GTM integration), or a custom name. These options are useful if there are conflicts between our names and the names declared by external scripts.
Support for the new_customer parameter for our native Google Tags and GTM – WooCommerce and EDD Purchase events. This parameter is used by Google Ads New Customer campaigns.
“Send just the data layer” option for our GTM integration.
WooCommerce and EDD item prices will follow the settings configured under Value Options about taxes (include, exclude).
WooCommerce and EDD events values updated: value options will now affect all the tags. We recommend sending value to Purchase events, but value is also supported for product events, cart events, and checkout events.
ON/OFF options for each tag added on the main page. We removed almost similar options from the tags settings pages.
New options for GTM custom events: add automated parameters in the data layer, remove the customTrigger object, use a custom name for the custom parameters object.
Fixing a small bug related to the GTM object name used to track custom event parameters.

• A new GTM configuration download file will set up a GTM container with variables tracking all our parameters and triggers tracking all our events. Version 1.0 of the file will also configure GA4 tags.
• Changes to the GTM data layer variable name to avoid possible conflicts.
• New GTM data layer structure that will make it easier to track our data.
• Fixing a possible conflict with WPRocket that resulted in the plugin being disabled on pages created with the cache pre-load feature.
• A new option that lets you remove bots from the disallow list using their user-name.
• Now you can disable bot blocking functionality if it creates problems.

• Google Tag Manager Support. It’s now possible to install a GTM container. We push all our default and custom events to the GTM Data Layer. This is only a beta version and we plan to develop it further. In the future, we will offer an Import file to implement a GMT container with all the triggers and variables required to track our events and parameters, plus the most popular tags.
• Multiple triggers for our events: when configuring events with the plugin you can now use multiple triggers (logic AND).
• WPML option for WooCommerce events: you select the main language IDs for e-commerce events making it possible to use localized feeds for your catalogs.
• Improving our crawler detect feature that can block a large number of known crawlers from triggering API events.
• Fixing possible conflicts with other plugins using outdated versions of the Guzzle library.
• Fixing a possible issue with YouTube and Vimeo scripts.
• Fixing a possible issue with item category tracking for some WooCommerce events.
• Fixing and improving the code.

• Improving some queries to avoid memory issues.
• Fixing a problem related to lifetime value and Advanced Marketing Events.

• Fixing possible issues and conflicts.
• Minimum PHP requirements 7.2.5.

New Elementor forms trigger fire events when an Elementor form is successfully submitted.
The automatic Form event will fire on a form submitted for Elementor forms instead of the form’s button clicks.
New trigger for email links: fire events for one or multiple email links.
Bot/Crawlers list updated.
New parameter for WooCommerce or Easy Digital Downloads Advanced Purchase Tracking events for Meta, Google, and TikTok tags: advanced_purchase_tracking. It will help identify events triggered by this option in the reports or our native logs.
Declaring compatibility with WooCommerce 9.3.

• New events trigger: fire your events for embedded YouTube or Vimeo videos.
• WooCommerce and EDD ChatGPT export include payment type. You can now ask ChatGPT to analyze the data based on the payment type.

New option regarding Google Tags user data with support for multiple user values (up to 3 email addresses, up to 2 address fields).
Fix related to the URL parameters events trigger logic.
Security improvement related to the API logs. Now access is restricted based on the plugin’s permission settings. Only user types with permission can download the logs.

• A new option that lets you use URL parameter values as personal data with API events or for Google Enhanced Conversions.
• Data persistency option for personal data used with the API events or Google Enhanced Conversions: you can select between using data for as long as possible (default), or updating it whenever possible.
• WSForm integration: our default Form event will fire when the form data is successfully submitted.
• WSForm integration: you can configure your own events for one or multiple forms that will fire when the form is submitted.
• Recurring tracking for our WooCommerce and Easy Digital Downloads reports.
• A fix related to the Litespeed cache.
• A fix related to a possible bug with Funnelkit checkout pages.
• Various code improvements and warning fixes.

• New options regarding external IDs. We now store a temporary value for external IDs using transients for up to 10 minutes, creating the premises to detect returning traffic based on IP addresses even when it’s done from a different browser or device. This can be turned OFF on the Global Settings page.
• Improved way to generate external IDs to fix missing values in some instances.
• A new Global Settings page, linked from the main right-side menu. We moved the Global Settings from the Dashboard page to this dedicated section.
• We improved how we fire purchase events for WooCommerce to cover some niche cases and configurations we noticed on clients’ websites.
• A new filter that allows developers to control Google Tags’ url_passthrough option. The filter is explained on the Google Tags Settings page. We also use this filter with our ConsentMagic plugin, allowing you to configure consent settings for this option.