Export transactions as offline conversions - Facebook (Meta)
Learn how to use it: watch video
>
If the default Purchase event doesn't fire when an order is placed by the client, a Purchase event will be sent to Meta and Google using API when the order status is changed to "Completed". Meta Conversion API token and GA4 Measurement Protocol secret are required.
A "Refund" event will be sent to Google via the API when the order status changes to "Refund". GA4 measurement protocol secret required.
Save the landing page, UTMs, client's browser's time, day, and month, the number of orders, lifetime value, and average order. You can view this data when you open an order, or on the WooCommerce Reports page
You will see the landing page, UTMs, client's browser's time, day, and month, the number of orders, lifetime value, and average order in your WooCommerce's default "New Order" email. Your clients will NOT get this info.
Show the landing page, traffic source, and UTMs on the order's edit page.
Display the number of orders, lifetime value, and average order.
Show the tracking type in the orders table and on the order's page.
The new_customer parameter is added to the purchase event for our Google native tags and for GTM. It's use by Google for new customer acquisition. We always send it with true or false values for logged-in users. We will use these options for guest checkout.
Don't add the Checkout page IDs if you use Stripe or Klarna because conflicts are possible.
Consider adding a prefix for transactions IDs if you use the same tags on multiple websites.
It looks like you're using both PixelYourSite and Facebook for WooCommerce Extension. Good, because they can do a great job together!
Facebook for WooCommerce Extension is a useful free tool that lets you import your products to a Facebook shop and adds a very basic Meta Pixel on your site. PixelYourSite is a dedicated plugin that supercharges your Meta Pixel with extremely useful features.
We made it possible to use both plugins together. You just have to decide what ID to use for your events.
* If you plan to use the product catalog created by Facebook for WooCommerce Extension, use the Facebook for WooCommerce Extension ID. If you plan to use older product catalogs, or new ones created with other plugins, it's better to keep the default PixelYourSite settings.
If you enable this option, the main ID will be used instead of the variation ID. Turn this option ON when your Product Catalog doesn't include the variants for variable products.
If you use localized feeds, enable the unified ID logic for the tag and we will use the native product ID for each translated item.
If you enable this option, the main ID will be used instead of the variation ID. Turn this option ON when your Merchant Catalog doesn't include the variants for variable products.
If you use localized feeds, enable the unified ID logic for the tag and we will use the native product ID for each translated item.
If you enable this option, the main ID will be used instead of the variation ID. Turn this option ON when your Product Catalog doesn't include the variants for variable products.
If you use localized feeds, enable the unified ID logic for the tag and we will use the native product ID for each translated item.
If you enable this option, the main ID will be used instead of the variation ID. Turn this option ON when your Product Catalog doesn't include the variants for variable products.
If you use localized feeds, enable the unified ID logic for the tag and we will use the native product ID for each translated item.
If you enable this option, the main ID will be used instead of the variation ID. Turn this option ON when your Product Catalog doesn't include the variants for variable products.
If you use localized feeds, enable the unified ID logic for the tag and we will use the native product ID for each translated item.
If you enable this option, the main ID will be used instead of the variation ID. Turn this option ON when your Merchant Catalog doesn't include the variants for variable products.
If you use localized feeds, enable the unified ID logic for the tag and we will use the native product ID for each translated item.
Supported only when using Google Analytics as conversion source
Note: When using Google Analytics as a conversion source, please use the parameter aw_feed_label instead.
It works when the tag is configured to track the variation data when a variation is selected - tags ID settings..
When checked, we send the data like we do now. Example:
Category - iPhones
Learn how to use it: watch video
You can use these parameters to create audiences, custom conversions, or goals. We recommend keeping them active. If you get privacy warnings about some of these parameters, you can turn them OFF.
All events get the following Global Parameters for all the tags: page_title, post_type, post_id, landing_page, event_URL, user_role, plugin, event_time (pro), event_day (pro), event_month (pro), traffic_source (pro), UTMs (pro).
The Meta Pixel events are Dynamic Ads ready.
The Google Analytics events track Monetization data (GA4).
The Google Ads events have the required data for Dynamic Remarketing (official help).
The Pinterest events have the required data for Dynamic Remarketing.
The Purchase event will have the following extra-parameters: category_name, num_items, tags, total (pro), transactions_count (pro), tax (pro), predicted_ltv (pro), average_order (pro), coupon_used (pro), coupon_code (pro), shipping (pro), shipping_cost (pro), fee (pro).
; ?>)