![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changeset 3771449
- Timestamp:
- 10/28/2026 07:19:56 PM (2 days ago)
- Location:
- tagioo-for-woocommerce
- Files:
-
- 2 edited
-
tags/2.7.0/readme.txt (modified) (5 diffs)
-
trunk/readme.txt (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
tagioo-for-woocommerce/tags/2.7.0/readme.txt
r3771442 r3771449 9 9 License URI: https://www.gnu.org/licenses/gpl-2.0.html 10 10 11 Se rver-side tracking for WooCommerce: GTM, GA4 ecommerce dataLayer events and a server-side purchase hit to your server-side GTM container.11 Send WooCommerce purchases to GA4, Meta and TikTok from your own server with server-side GTM, plus a complete GA4 ecommerce dataLayer. 12 12 13 13 == Description == 14 14 15 Tagioo Server-Side Tracking for WooCommerce connects your store to Google Tag Manager and to a server-side Google Tag Manager (sGTM) container, so purchases are still recorded when a browser pixel is blocked or the shopper closes the tab.15 Ad blockers, Safari's tracking limits and closed browser tabs stop many purchases from ever reaching GA4, Meta or TikTok. **Tagioo Server-Side Tracking for WooCommerce sends every paid order from your WordPress server to your own server-side Google Tag Manager (sGTM) container**, so the sale is recorded even when the browser pixel never fires. 16 16 17 **What it does** 17 It also gives your Google Tag Manager web container a complete GA4 ecommerce dataLayer, so you don't need a separate GTM plugin. 18 18 19 * Adds the Google Tag Manager snippet to your store (optional — turn it off if you already load GTM). 20 * Pushes GA4 ecommerce events to the dataLayer: `view_item`, `view_item_list`, `search`, `add_to_cart`, `remove_from_cart`, `view_cart`, `begin_checkout`, `add_shipping_info`, `add_payment_info` and `purchase`. Works with the classic shortcode checkout and the Cart and Checkout Blocks. 21 * Sends a server-side GA4 purchase hit to your sGTM container when an order is paid (or reaches Processing for cash on delivery and bank transfer). The hit runs in the background with retries, so a slow server never blocks checkout. 22 * Adds a shared `event_id` to browser and server events so Meta and TikTok can deduplicate them. 23 * Stores the Meta `_fbp` / `_fbc` identifiers as first-party cookies and saves them on the order for better conversion matching. 24 * Optional cookie consent: a built-in Accept / Reject banner wired to Google Consent Mode v2, or read the choice from CookieYes, Complianz, Cookiebot, OneTrust or the WP Consent API. 25 * Optional Custom Loader: load `gtm.js` through your own sGTM domain instead of googletagmanager.com. 19 = What it does = 20 21 * **Server-side purchase hit.** When an order is paid (or reaches Processing, for cash on delivery and bank transfer), the plugin sends a GA4 purchase event from your server to your sGTM container. It runs in the background, so checkout is never slowed down, and it tries again if your sGTM server is briefly unavailable. 22 * **GA4 ecommerce dataLayer.** Pushes `view_item`, `view_item_list`, `search`, `add_to_cart`, `remove_from_cart`, `view_cart`, `begin_checkout`, `add_shipping_info`, `add_payment_info` and `purchase` with items, value and currency. Works with the classic checkout and the Cart and Checkout Blocks, including AJAX add to cart and quantity changes. 23 * **Customer data for better matching.** Purchase events include the billing email, phone number (in international format), name and address, so your server tags can hash them and send them to Meta and TikTok. Logged-in shoppers' details are added to earlier events too. 24 * **No double counting.** Browser and server events share an `event_id` (the WooCommerce order ID for purchases), which Meta and TikTok use to deduplicate them. 25 * **Longer-lasting Meta identifiers.** Turns the `fbclid` from an ad click into the `_fbc` cookie on the landing page, keeps `_fbp` and `_fbc` as first-party cookies set by your server, and saves them on the order. 26 * **Google Tag Manager snippet.** Adds your GTM container to every page. Turn it off if your theme or another plugin already loads GTM. 27 * **Cookie consent (optional).** Show Tagioo's Accept / Reject banner with Google Consent Mode v2, or read the shopper's choice from CookieYes, Complianz, Cookiebot, OneTrust or the WP Consent API. The choice is sent with the server-side purchase hit so your sGTM tags can respect it. 28 * **Custom Loader (optional).** Loads `gtm.js` from your sGTM domain instead of googletagmanager.com, for servers set up to serve it (Tagioo-hosted servers are). 26 29 * Compatible with WooCommerce High-Performance Order Storage (HPOS). 27 30 28 **What you need** 31 = What you need = 29 32 30 * A Google Tag Manager web container. 31 * A server-side GTM container on your own domain (for the server-side purchase hit). You can host it yourself or use [Tagioo](https://tagioo.com). 32 * A GA4 Measurement ID and Measurement Protocol API secret. 33 * WooCommerce. 34 * A Google Tag Manager web container whose tags (for example GA4, Meta Pixel and TikTok Pixel) use the dataLayer events above. 35 * A server-side GTM container on your own subdomain, such as `sgtm.yourstore.com`, with a GA4 client and the server tags you want (for example GA4, Meta Conversions API and TikTok Events API). You can host it yourself or use [Tagioo](https://tagioo.com), which sets up both containers for you. 36 * Your GA4 Measurement ID and a GA4 Measurement Protocol API secret. 33 37 34 All features in the plugin are free. The plugin does not lock any feature behind a licence or account.38 Every feature in the plugin is free. Nothing is locked behind a licence or account, and it works with any server-side GTM container, not only Tagioo's. 35 39 36 40 == External services == … … 75 79 == Installation == 76 80 77 1. Install and activate WooCommerce. 78 2. Upload the plugin through Plugins → Add New, or search for "Tagioo Server-Side Tracking for WooCommerce", then activate it. 79 3. Go to WooCommerce → Tagioo. 80 4. Enter your GTM Container ID. 81 5. For the server-side purchase hit, enter your sGTM domain, GA4 Measurement ID and GA4 API secret. 82 6. Choose the events you want, set cookie consent if your store needs it, and save. 81 1. Make sure WooCommerce is installed and active. 82 2. In WordPress, go to **Plugins → Add New Plugin**, search for "Tagioo Server-Side Tracking", click **Install Now**, then **Activate**. 83 3. Go to **WooCommerce → Tagioo**. 84 4. **GTM:** enter your GTM container ID (`GTM-XXXXXXX`). If your theme or another plugin already adds GTM, untick **Inject GTM snippet** so it doesn't load twice. 85 5. **Server-side GTM:** enter your sGTM domain (for example `https://sgtm.yourstore.com`), your GA4 Measurement ID (`G-XXXXXXXXXX`) and a GA4 Measurement Protocol API secret. To create the secret, go to GA4 → Admin → Data streams → your web stream → Measurement Protocol API secrets → Create. The server-side purchase hit only runs when all three are filled in. 86 6. **Events:** all events are on by default. Untick any you don't want. 87 7. **Cookie consent:** leave it **Off**, choose **Show Tagioo consent banner**, or choose **Use my own cookie banner plugin** if your store already has one. 88 8. Click **Save Settings**. 83 89 84 If you already load GTM with another plugin or your theme, untick "Inject GTM snippet" so it does not load twice. 90 = Check that it works = 91 92 1. Open a product page with GTM Preview mode (Tag Assistant) running. You should see a `view_item` event with the product's name, price and currency. 93 2. Place a test order and make sure it is paid or Processing. Within a few minutes the purchase should appear in GA4 Realtime, and in Meta Events Manager as a server event if your sGTM container sends to Meta. 94 3. If it doesn't, check **WooCommerce → Status → Logs** for entries with the source `tagioo`. 95 96 The server-side purchase hit is sent by WP-Cron, which runs when your site gets visits. On a store with very little traffic, a real server cron job makes the hit arrive sooner. 85 97 86 98 == Frequently Asked Questions == … … 92 104 = Will purchases be counted twice? = 93 105 94 No. The browser purchase event and the server-side hit share the same `event_id` (the WooCommerce order ID), and GA4 deduplicates by`transaction_id`.106 No. The browser purchase event and the server-side hit share the same `event_id` (the WooCommerce order ID), which Meta and TikTok use to keep only one of them. Make sure your browser pixel tags in GTM pass the `event_id` from the dataLayer. Both hits also carry the same GA4 `transaction_id`. 95 107 96 108 = Does it work with the Checkout Block? = … … 104 116 = Where do I see errors from the server-side hit? = 105 117 106 Failed attempts are retried up to five times andlogged in WooCommerce → Status → Logs under the source `tagioo`.118 The plugin tries each purchase up to five times, waiting a little longer each time (1, 2, 3 and 4 minutes). Failed attempts are logged in WooCommerce → Status → Logs under the source `tagioo`. 107 119 108 120 == Screenshots == … … 115 127 116 128 = 2.7.0 = 129 * Renamed to Tagioo Server-Side Tracking for WooCommerce. 117 130 * Inline scripts and styles now use the WordPress script and style APIs. 118 131 * Escaping and input sanitizing hardened throughout. -
tagioo-for-woocommerce/trunk/readme.txt
r3771442 r3771449 9 9 License URI: https://www.gnu.org/licenses/gpl-2.0.html 10 10 11 Se rver-side tracking for WooCommerce: GTM, GA4 ecommerce dataLayer events and a server-side purchase hit to your server-side GTM container.11 Send WooCommerce purchases to GA4, Meta and TikTok from your own server with server-side GTM, plus a complete GA4 ecommerce dataLayer. 12 12 13 13 == Description == 14 14 15 Tagioo Server-Side Tracking for WooCommerce connects your store to Google Tag Manager and to a server-side Google Tag Manager (sGTM) container, so purchases are still recorded when a browser pixel is blocked or the shopper closes the tab.15 Ad blockers, Safari's tracking limits and closed browser tabs stop many purchases from ever reaching GA4, Meta or TikTok. **Tagioo Server-Side Tracking for WooCommerce sends every paid order from your WordPress server to your own server-side Google Tag Manager (sGTM) container**, so the sale is recorded even when the browser pixel never fires. 16 16 17 **What it does** 17 It also gives your Google Tag Manager web container a complete GA4 ecommerce dataLayer, so you don't need a separate GTM plugin. 18 18 19 * Adds the Google Tag Manager snippet to your store (optional — turn it off if you already load GTM). 20 * Pushes GA4 ecommerce events to the dataLayer: `view_item`, `view_item_list`, `search`, `add_to_cart`, `remove_from_cart`, `view_cart`, `begin_checkout`, `add_shipping_info`, `add_payment_info` and `purchase`. Works with the classic shortcode checkout and the Cart and Checkout Blocks. 21 * Sends a server-side GA4 purchase hit to your sGTM container when an order is paid (or reaches Processing for cash on delivery and bank transfer). The hit runs in the background with retries, so a slow server never blocks checkout. 22 * Adds a shared `event_id` to browser and server events so Meta and TikTok can deduplicate them. 23 * Stores the Meta `_fbp` / `_fbc` identifiers as first-party cookies and saves them on the order for better conversion matching. 24 * Optional cookie consent: a built-in Accept / Reject banner wired to Google Consent Mode v2, or read the choice from CookieYes, Complianz, Cookiebot, OneTrust or the WP Consent API. 25 * Optional Custom Loader: load `gtm.js` through your own sGTM domain instead of googletagmanager.com. 19 = What it does = 20 21 * **Server-side purchase hit.** When an order is paid (or reaches Processing, for cash on delivery and bank transfer), the plugin sends a GA4 purchase event from your server to your sGTM container. It runs in the background, so checkout is never slowed down, and it tries again if your sGTM server is briefly unavailable. 22 * **GA4 ecommerce dataLayer.** Pushes `view_item`, `view_item_list`, `search`, `add_to_cart`, `remove_from_cart`, `view_cart`, `begin_checkout`, `add_shipping_info`, `add_payment_info` and `purchase` with items, value and currency. Works with the classic checkout and the Cart and Checkout Blocks, including AJAX add to cart and quantity changes. 23 * **Customer data for better matching.** Purchase events include the billing email, phone number (in international format), name and address, so your server tags can hash them and send them to Meta and TikTok. Logged-in shoppers' details are added to earlier events too. 24 * **No double counting.** Browser and server events share an `event_id` (the WooCommerce order ID for purchases), which Meta and TikTok use to deduplicate them. 25 * **Longer-lasting Meta identifiers.** Turns the `fbclid` from an ad click into the `_fbc` cookie on the landing page, keeps `_fbp` and `_fbc` as first-party cookies set by your server, and saves them on the order. 26 * **Google Tag Manager snippet.** Adds your GTM container to every page. Turn it off if your theme or another plugin already loads GTM. 27 * **Cookie consent (optional).** Show Tagioo's Accept / Reject banner with Google Consent Mode v2, or read the shopper's choice from CookieYes, Complianz, Cookiebot, OneTrust or the WP Consent API. The choice is sent with the server-side purchase hit so your sGTM tags can respect it. 28 * **Custom Loader (optional).** Loads `gtm.js` from your sGTM domain instead of googletagmanager.com, for servers set up to serve it (Tagioo-hosted servers are). 26 29 * Compatible with WooCommerce High-Performance Order Storage (HPOS). 27 30 28 **What you need** 31 = What you need = 29 32 30 * A Google Tag Manager web container. 31 * A server-side GTM container on your own domain (for the server-side purchase hit). You can host it yourself or use [Tagioo](https://tagioo.com). 32 * A GA4 Measurement ID and Measurement Protocol API secret. 33 * WooCommerce. 34 * A Google Tag Manager web container whose tags (for example GA4, Meta Pixel and TikTok Pixel) use the dataLayer events above. 35 * A server-side GTM container on your own subdomain, such as `sgtm.yourstore.com`, with a GA4 client and the server tags you want (for example GA4, Meta Conversions API and TikTok Events API). You can host it yourself or use [Tagioo](https://tagioo.com), which sets up both containers for you. 36 * Your GA4 Measurement ID and a GA4 Measurement Protocol API secret. 33 37 34 All features in the plugin are free. The plugin does not lock any feature behind a licence or account.38 Every feature in the plugin is free. Nothing is locked behind a licence or account, and it works with any server-side GTM container, not only Tagioo's. 35 39 36 40 == External services == … … 75 79 == Installation == 76 80 77 1. Install and activate WooCommerce. 78 2. Upload the plugin through Plugins → Add New, or search for "Tagioo Server-Side Tracking for WooCommerce", then activate it. 79 3. Go to WooCommerce → Tagioo. 80 4. Enter your GTM Container ID. 81 5. For the server-side purchase hit, enter your sGTM domain, GA4 Measurement ID and GA4 API secret. 82 6. Choose the events you want, set cookie consent if your store needs it, and save. 81 1. Make sure WooCommerce is installed and active. 82 2. In WordPress, go to **Plugins → Add New Plugin**, search for "Tagioo Server-Side Tracking", click **Install Now**, then **Activate**. 83 3. Go to **WooCommerce → Tagioo**. 84 4. **GTM:** enter your GTM container ID (`GTM-XXXXXXX`). If your theme or another plugin already adds GTM, untick **Inject GTM snippet** so it doesn't load twice. 85 5. **Server-side GTM:** enter your sGTM domain (for example `https://sgtm.yourstore.com`), your GA4 Measurement ID (`G-XXXXXXXXXX`) and a GA4 Measurement Protocol API secret. To create the secret, go to GA4 → Admin → Data streams → your web stream → Measurement Protocol API secrets → Create. The server-side purchase hit only runs when all three are filled in. 86 6. **Events:** all events are on by default. Untick any you don't want. 87 7. **Cookie consent:** leave it **Off**, choose **Show Tagioo consent banner**, or choose **Use my own cookie banner plugin** if your store already has one. 88 8. Click **Save Settings**. 83 89 84 If you already load GTM with another plugin or your theme, untick "Inject GTM snippet" so it does not load twice. 90 = Check that it works = 91 92 1. Open a product page with GTM Preview mode (Tag Assistant) running. You should see a `view_item` event with the product's name, price and currency. 93 2. Place a test order and make sure it is paid or Processing. Within a few minutes the purchase should appear in GA4 Realtime, and in Meta Events Manager as a server event if your sGTM container sends to Meta. 94 3. If it doesn't, check **WooCommerce → Status → Logs** for entries with the source `tagioo`. 95 96 The server-side purchase hit is sent by WP-Cron, which runs when your site gets visits. On a store with very little traffic, a real server cron job makes the hit arrive sooner. 85 97 86 98 == Frequently Asked Questions == … … 92 104 = Will purchases be counted twice? = 93 105 94 No. The browser purchase event and the server-side hit share the same `event_id` (the WooCommerce order ID), and GA4 deduplicates by`transaction_id`.106 No. The browser purchase event and the server-side hit share the same `event_id` (the WooCommerce order ID), which Meta and TikTok use to keep only one of them. Make sure your browser pixel tags in GTM pass the `event_id` from the dataLayer. Both hits also carry the same GA4 `transaction_id`. 95 107 96 108 = Does it work with the Checkout Block? = … … 104 116 = Where do I see errors from the server-side hit? = 105 117 106 Failed attempts are retried up to five times andlogged in WooCommerce → Status → Logs under the source `tagioo`.118 The plugin tries each purchase up to five times, waiting a little longer each time (1, 2, 3 and 4 minutes). Failed attempts are logged in WooCommerce → Status → Logs under the source `tagioo`. 107 119 108 120 == Screenshots == … … 115 127 116 128 = 2.7.0 = 129 * Renamed to Tagioo Server-Side Tracking for WooCommerce. 117 130 * Inline scripts and styles now use the WordPress script and style APIs. 118 131 * Escaping and input sanitizing hardened throughout.
Note:
See TracChangeset
for help on using the changeset viewer.
