WordPress.org
Get WordPress

Plugin Directory

Changeset 3439902


Ignore:
Timestamp:
01/14/2026 10:48:11 PM (5 weeks ago)
Author:
kayavanvliet
Message:

new readme

Location:
tracksharp
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • tracksharp/tags/1.2.6/readme.txt

    r3439888 r3439902  
    1313== Description ==
    1414
    15 Are you losing conversion data without noticing?
     15**Improve purchase conversion tracking accuracy for WooCommerce with native server-side tracking.**
    1616
    17 Browser-based tracking is not 100% reliable. Ad blockers, iOS/browser privacy (ITP), consent choices, and fast checkouts can prevent tags from firing consistently. Orders are completed in WooCommerce, but reporting and attribution can be incomplete.
     17Browser-based tracking is blocked by modern privacy settings (ITP), ad blockers, and consent choices. This leads to missing purchase conversions in GA4 and incomplete ad reporting.
    1818
    19 **TrackSharp** adds a first-party, server-side tracking layer so your most important event **Purchase** is recorded more reliably in GA4.
     19**TrackSharp** adds a reliable, first-party server-side tracking layer. It ensures your most important event — **Purchase** — is recorded in GA4 even when browser tags fail.
    2020
    21 No GTM server container. No complex setup. Just install, connect, and verify.
     21No GTM server container. No Google Cloud costs. No complex coding.
    2222
    23 = Start with the Free Audit (included) =
     23> “We previously used Google Tag Manager, but browser blocking still caused us to miss up to 40% of our conversions. With TrackSharp, our data is finally 100% accurate without us needing to change a thing.”
     24>
     25> **Jordi** — Online Marketer at Hbeds.nl
    2426
    25 Not sure if you need server-side tracking? Install TrackSharp and check the Dashboard.
     27= What Problem We Solve =
    2628
    27 The free version adds **Attribution Audit Cards** that highlight tracking risks using your own site data:
     29Most store owners don't know *how much* data they are losing. Setting up server-side tracking usually requires complex Google Tag Manager (GTM) containers, monthly cloud hosting fees (Stape/Google Cloud), and developer time.
    2830
    29 * **Google Ads attribution risk** — whether orders were matched to Google Ads traffic in the last period.
    30 * **Meta Pixel coverage** — whether purchases are being detected in the browser (Pixel).
     31**TrackSharp removes that complexity and cost.**
     32It runs directly on your WordPress server as a native plugin. You can complete the setup in 5 minutes and immediately start auditing your data loss and fixing GA4 tracking.
    3133
    32 This is a health/audit view designed to make gaps visible so you can decide what to improve.
     34= Features & Capabilities =
    3335
    34 = What TrackSharp does =
     36**1. Instant Attribution Audit (Free)**
     37Unique to TrackSharp: we don't just track, we *diagnose*. The dashboard uses your real historical order data to highlight risks:
     38* **Google Ads Blind Spots:** See how many orders have Google Click IDs (gclid) that browser tracking might have missed.
     39* **Meta Pixel Health:** Monitor if your browser Pixel is firing correctly or being blocked.
    3540
    36 = Free Features (Included) =
     41**2. Reliable GA4 Server-Side Tracking**
     42Sends purchase events via the Measurement Protocol directly from your server. This bypasses ad blockers and iOS restrictions to close the gap between WooCommerce orders and Analytics reports.
    3743
    38 * **GA4 server-side Purchase tracking**
    39   Sends Purchase events via Measurement Protocol, triggered from the WooCommerce order flow.
    40 * **Attribution Audit Cards (Dashboard)**
    41   A quick health check for Google Ads and Meta based on real site data.
    42 * **Dashboard & Events Log**
    43   View sent events, order IDs, revenue, and delivery status. Export logs as CSV for auditing.
    44 * **Setup Wizard**
    45   Connect GA4 using your Measurement ID and API Secret in minutes.
    46 * **Consent-aware**
    47   Integrates with the WP Consent API. If no CMP is present, a configurable fallback applies.
    48 * **First-party collector endpoint**
    49   Optional endpoint (`/wp-json/tracksharp/v1/p`) for logging and advanced setups.
     44**3. Native WooCommerce Integration**
     45Unlike generic GTM solutions, TrackSharp is purpose-built for WooCommerce. It listens to internal order hooks to ensure data accuracy.
    5046
    51 *Note: Beside purchase, TrackSharp also sends other key WooCommerce ecommerce events server-side to GA4, including view_item, add_to_cart, begin_checkout, add_payment_info*
     47= Supported WooCommerce Events =
    5248
    53 = Optional: TrackSharp Pro =
     49TrackSharp tracks the complete shopping journey server-side (GA4) to ensure full funnel visibility:
    5450
    55 If you advertise on Meta or Google Ads, TrackSharp Pro adds deeper attribution features:
     51* **Shopper Activity:** `view_item` (product view), `add_to_cart`, `view_cart`
     52* **Checkout Flow:** `begin_checkout`, `add_payment_info`
     53* **Conversion:** `purchase` (Order Completed)
    5654
    57 * **Meta Conversions API (CAPI)**
    58   Server-side events with hashed customer data to improve matching.
    59 * **Google Ads attribution**
    60   Captures Google Ads identifiers so conversions can be attributed more reliably.
    61 * **Enhanced Conversions**
    62   Improves matching for bidding/attribution by sending hashed customer data.
    63 * **Priority support**
    64   Direct access to the developers.
     55*Note: Non-purchase events are sent via the first-party collector endpoint included in the free version.*
    6556
    66 TrackSharp Pro is optional - the free version works standalone with GA4.
     57= Best Fit For Which Stores? =
     58
     59* **Stores running Paid Ads:** If you spend budget on Google Ads or Meta (Facebook/Instagram) and suspect your ROAS is inaccurate due to tracking loss.
     60* **Cost-Conscious Owners:** Stores that want reliable Server-Side tracking without paying €20-€100/month for external hosting (like Stape or Google Cloud).
     61* **Agencies & Freelancers:** Professionals looking for a "set-and-forget" solution for clients that doesn't require maintaining complex GTM server containers.
     62* **Non-Technical Founders:** Anyone who wants to fix their data accuracy in 5 minutes without writing code or hiring a developer.
     63
     64= Pro Version: Advanced Attribution =
     65
     66For stores running paid ads on Google or Meta, TrackSharp Pro adds the missing attribution layer:
     67
     68* **Google Ads Attribution:** Captures attribution parameters server-side so conversions are credited to the right campaign.
     69* **Meta Conversions API (CAPI):** Full server-side backup for the Facebook Pixel.
     70* **Enhanced Conversions:** Sends hashed user data (email/phone) to improve match rates on both platforms.
     71* **Priority Support:** Direct access to the developers via email.
    6772
    6873== How It Works ==
    6974
    70 1. A customer checks out in WooCommerce.
    71 2. TrackSharp captures first-party session and GA identifiers during checkout.
    72 3. When the order is paid, a server-side Purchase event is sent to GA4.
    73 4. Use TrackSharp → Dashboard and TrackSharp → Events to verify delivery.
    74 
    75 == Consent & Privacy ==
    76 
    77 * If the WP Consent API is present, TrackSharp only sends GA4 events when the configured consent category is granted (default: `statistics` or `statistics-anonymous`).
    78 * If no WP Consent API / CMP is present, TrackSharp uses a configurable fallback behavior (default: grant immediately).
    79 
    80 == What Data Is Stored ==
    81 
    82 * Custom table: `{$wpdb->prefix}ws_events` (event audit log)
    83 * Order meta: session ID, GA client ID, consent snapshot
    84 * Cookie: `ws_session_id` (first-party session ID)
     751.  **Install:** Activate the plugin on your WordPress site.
     762.  **Connect:** Use the Setup Wizard to link your GA4 Measurement ID.
     773.  **Audit:** Check the Dashboard to see your "Revenue Audit" and potential data loss.
     784.  **Relax:** TrackSharp now runs in the background, securing your data.
    8579
    8680== Installation ==
    8781
    88 1. Install and activate the plugin.
    89 2. Go to TrackSharp → Setup Wizard.
    90 3. Enter your GA4 Measurement ID and Measurement Protocol API Secret.
    91 4. (Recommended) Use a CMP that integrates with the WP Consent API.
    92 5. Place a test order and review TrackSharp → Events.
     821.  Install and activate the plugin.
     832.  Go to **TrackSharp → Setup Wizard**.
     843.  Enter your GA4 Measurement ID and Measurement Protocol API Secret.
     854.  (Recommended) Use a CMP that integrates with the WP Consent API.
     865.  Place a test order and review **TrackSharp → Events**.
    9387
    9488== Frequently Asked Questions ==
    9589
    9690= Does this replace my GA4 browser tags? =
    97 No. TrackSharp adds server-side tracking for purchases and other ecommerce events.
     91No. TrackSharp adds server-side tracking as a safety net. If you use GTM for browser tags, TrackSharp handles the deduplication (using `event_id`) to prevent double counting.
    9892
    99 If you are already sending a browser `purchase` event (for example via GTM), make sure you avoid double counting in GA4:
    100 * disable the browser purchase tag, or
    101 * configure deduplication using the same `event_id`.
    102 
    103 = How does GA4 deduplication work? =
    104 GA4 can deduplicate browser and Measurement Protocol events when they share the same `event_name` and `event_id` and are associated with the same user/session.
    105 
    106 TrackSharp uses deterministic `event_id` values for server-side Purchase events based on the WooCommerce order ID.
    107 
    108 = Does this work without WooCommerce? =
    109 No. TrackSharp is built specifically for WooCommerce orders.
     93= Do I need a GTM server container (Stape / Google Cloud)? =
     94No! That is the main benefit of TrackSharp. It runs directly on your WordPress server. You save €20-€100/month on external server hosting costs compared to container-based solutions like Conversios or Stape.
    11095
    11196= Is it GDPR compliant? =
    112 TrackSharp integrates with the WP Consent API and can be configured to respect consent categories. You are responsible for your legal basis and privacy disclosures.
     97TrackSharp integrates with the WP Consent API. It only sends data when the appropriate consent (Statistics/Marketing) is granted. If no CMP is found, you can configure the fallback behavior.
    11398
    11499== Screenshots ==
    115100
    116 1. Dashboard - Attribution Audit Cards (Google Ads + Meta Pixel health)
    117 2. Events Log - filters, status indicators, and CSV export
    118 3. Settings - GA4 credentials and consent configuration
    119 4. Setup Wizard - guided setup and testing tools
     1011.  **Dashboard** - Instantly see "Untracked Google Ads Revenue" and "Pixel Gaps".
     1022.  **Events Log** - Inspect individual API calls and status indicators.
     1033.  **Settings** - GA4 credentials and consent configuration.
     1044.  **Setup Wizard** - Guided 5-minute setup.
    120105
    121106== Changelog ==
    122107
    123108= 1.2.6 =
    124 * Added "Attribution Audit" cards on the Dashboard to highlight tracking risks using real site data (Google Ads click IDs + Meta Pixel coverage).
     109* New: "Attribution Audit" cards on the Dashboard to highlight tracking risks using real site data.
    125110
    126111= 1.2.5 =
    127 * Added a GA4 comparison mode to send server purchases as purchase_sst (optional).
    128 * Increased the default log retention to 180 days for reliable period comparisons.
     112* Added GA4 comparison mode to send server purchases as purchase_sst.
     113* Increased log retention to 180 days.
    129114
    130115= 1.2.4 =
    131 * Added a setting to measure revenue excluding VAT/tax (affects dashboard + GA4/Meta purchase value).
     116* Added setting to measure revenue excluding VAT/tax.
    132117
    133118= 1.2.3 =
    134 * Dutch sites: Upgrade button opens https://tracksharp.nl/#prijzen
     119* Dutch sites: Upgrade button opens https://tracksharp.nl
    135120
    136121= 1.2.2 =
    137 * Initial WordPress.org release
    138 * GA4 server-side Purchase tracking (Measurement Protocol)
    139 * Dashboard + Events Log
    140 * WP Consent API integration and setup wizard
     122* Initial WordPress.org release.
    141123
    142124== Upgrade Notice ==

  • tracksharp/trunk/readme.txt

    r3439672 r3439902  
    1313== Description ==
    1414
    15 Are you losing conversion data without noticing?
     15**Improve purchase conversion tracking accuracy for WooCommerce with native server-side tracking.**
    1616
    17 Browser-based tracking is not 100% reliable. Ad blockers, iOS/browser privacy (ITP), consent choices, and fast checkouts can prevent tags from firing consistently. Orders are completed in WooCommerce, but reporting and attribution can be incomplete.
     17Browser-based tracking is blocked by modern privacy settings (ITP), ad blockers, and consent choices. This leads to missing purchase conversions in GA4 and incomplete ad reporting.
    1818
    19 **TrackSharp** adds a first-party, server-side tracking layer so your most important event **Purchase** is recorded more reliably in GA4.
     19**TrackSharp** adds a reliable, first-party server-side tracking layer. It ensures your most important event — **Purchase** — is recorded in GA4 even when browser tags fail.
    2020
    21 No GTM server container. No complex setup. Just install, connect, and verify.
     21No GTM server container. No Google Cloud costs. No complex coding.
    2222
    23 = Start with the Free Audit (included) =
     23> “We previously used Google Tag Manager, but browser blocking still caused us to miss up to 40% of our conversions. With TrackSharp, our data is finally 100% accurate without us needing to change a thing.”
     24>
     25> **Jordi** — Online Marketer at Hbeds.nl
    2426
    25 Not sure if you need server-side tracking? Install TrackSharp and check the Dashboard.
     27= What Problem We Solve =
    2628
    27 The free version adds **Attribution Audit Cards** that highlight tracking risks using your own site data:
     29Most store owners don't know *how much* data they are losing. Setting up server-side tracking usually requires complex Google Tag Manager (GTM) containers, monthly cloud hosting fees (Stape/Google Cloud), and developer time.
    2830
    29 * **Google Ads attribution risk** — whether orders were matched to Google Ads traffic in the last period.
    30 * **Meta Pixel coverage** — whether purchases are being detected in the browser (Pixel).
     31**TrackSharp removes that complexity and cost.**
     32It runs directly on your WordPress server as a native plugin. You can complete the setup in 5 minutes and immediately start auditing your data loss and fixing GA4 tracking.
    3133
    32 This is a health/audit view designed to make gaps visible so you can decide what to improve.
     34= Features & Capabilities =
    3335
    34 = What TrackSharp does =
     36**1. Instant Attribution Audit (Free)**
     37Unique to TrackSharp: we don't just track, we *diagnose*. The dashboard uses your real historical order data to highlight risks:
     38* **Google Ads Blind Spots:** See how many orders have Google Click IDs (gclid) that browser tracking might have missed.
     39* **Meta Pixel Health:** Monitor if your browser Pixel is firing correctly or being blocked.
    3540
    36 = Free Features (Included) =
     41**2. Reliable GA4 Server-Side Tracking**
     42Sends purchase events via the Measurement Protocol directly from your server. This bypasses ad blockers and iOS restrictions to close the gap between WooCommerce orders and Analytics reports.
    3743
    38 * **GA4 server-side Purchase tracking**
    39   Sends Purchase events via Measurement Protocol, triggered from the WooCommerce order flow.
    40 * **Attribution Audit Cards (Dashboard)**
    41   A quick health check for Google Ads and Meta based on real site data.
    42 * **Dashboard & Events Log**
    43   View sent events, order IDs, revenue, and delivery status. Export logs as CSV for auditing.
    44 * **Setup Wizard**
    45   Connect GA4 using your Measurement ID and API Secret in minutes.
    46 * **Consent-aware**
    47   Integrates with the WP Consent API. If no CMP is present, a configurable fallback applies.
    48 * **First-party collector endpoint**
    49   Optional endpoint (`/wp-json/tracksharp/v1/p`) for logging and advanced setups.
     44**3. Native WooCommerce Integration**
     45Unlike generic GTM solutions, TrackSharp is purpose-built for WooCommerce. It listens to internal order hooks to ensure data accuracy.
    5046
    51 *Note: Beside purchase, TrackSharp also sends other key WooCommerce ecommerce events server-side to GA4, including view_item, add_to_cart, begin_checkout, add_payment_info*
     47= Supported WooCommerce Events =
    5248
    53 = Optional: TrackSharp Pro =
     49TrackSharp tracks the complete shopping journey server-side (GA4) to ensure full funnel visibility:
    5450
    55 If you advertise on Meta or Google Ads, TrackSharp Pro adds deeper attribution features:
     51* **Shopper Activity:** `view_item` (product view), `add_to_cart`, `view_cart`
     52* **Checkout Flow:** `begin_checkout`, `add_payment_info`
     53* **Conversion:** `purchase` (Order Completed)
    5654
    57 * **Meta Conversions API (CAPI)**
    58   Server-side events with hashed customer data to improve matching.
    59 * **Google Ads attribution**
    60   Captures Google Ads identifiers so conversions can be attributed more reliably.
    61 * **Enhanced Conversions**
    62   Improves matching for bidding/attribution by sending hashed customer data.
    63 * **Priority support**
    64   Direct access to the developers.
     55*Note: Non-purchase events are sent via the first-party collector endpoint included in the free version.*
    6556
    66 TrackSharp Pro is optional - the free version works standalone with GA4.
     57= Best Fit For Which Stores? =
     58
     59* **Stores running Paid Ads:** If you spend budget on Google Ads or Meta (Facebook/Instagram) and suspect your ROAS is inaccurate due to tracking loss.
     60* **Cost-Conscious Owners:** Stores that want reliable Server-Side tracking without paying €20-€100/month for external hosting (like Stape or Google Cloud).
     61* **Agencies & Freelancers:** Professionals looking for a "set-and-forget" solution for clients that doesn't require maintaining complex GTM server containers.
     62* **Non-Technical Founders:** Anyone who wants to fix their data accuracy in 5 minutes without writing code or hiring a developer.
     63
     64= Pro Version: Advanced Attribution =
     65
     66For stores running paid ads on Google or Meta, TrackSharp Pro adds the missing attribution layer:
     67
     68* **Google Ads Attribution:** Captures attribution parameters server-side so conversions are credited to the right campaign.
     69* **Meta Conversions API (CAPI):** Full server-side backup for the Facebook Pixel.
     70* **Enhanced Conversions:** Sends hashed user data (email/phone) to improve match rates on both platforms.
     71* **Priority Support:** Direct access to the developers via email.
    6772
    6873== How It Works ==
    6974
    70 1. A customer checks out in WooCommerce.
    71 2. TrackSharp captures first-party session and GA identifiers during checkout.
    72 3. When the order is paid, a server-side Purchase event is sent to GA4.
    73 4. Use TrackSharp → Dashboard and TrackSharp → Events to verify delivery.
    74 
    75 == Consent & Privacy ==
    76 
    77 * If the WP Consent API is present, TrackSharp only sends GA4 events when the configured consent category is granted (default: `statistics` or `statistics-anonymous`).
    78 * If no WP Consent API / CMP is present, TrackSharp uses a configurable fallback behavior (default: grant immediately).
    79 
    80 == What Data Is Stored ==
    81 
    82 * Custom table: `{$wpdb->prefix}ws_events` (event audit log)
    83 * Order meta: session ID, GA client ID, consent snapshot
    84 * Cookie: `ws_session_id` (first-party session ID)
     751.  **Install:** Activate the plugin on your WordPress site.
     762.  **Connect:** Use the Setup Wizard to link your GA4 Measurement ID.
     773.  **Audit:** Check the Dashboard to see your "Revenue Audit" and potential data loss.
     784.  **Relax:** TrackSharp now runs in the background, securing your data.
    8579
    8680== Installation ==
    8781
    88 1. Install and activate the plugin.
    89 2. Go to TrackSharp → Setup Wizard.
    90 3. Enter your GA4 Measurement ID and Measurement Protocol API Secret.
    91 4. (Recommended) Use a CMP that integrates with the WP Consent API.
    92 5. Place a test order and review TrackSharp → Events.
     821.  Install and activate the plugin.
     832.  Go to **TrackSharp → Setup Wizard**.
     843.  Enter your GA4 Measurement ID and Measurement Protocol API Secret.
     854.  (Recommended) Use a CMP that integrates with the WP Consent API.
     865.  Place a test order and review **TrackSharp → Events**.
    9387
    9488== Frequently Asked Questions ==
    9589
    9690= Does this replace my GA4 browser tags? =
    97 No. TrackSharp adds server-side tracking for purchases and other ecommerce events.
     91No. TrackSharp adds server-side tracking as a safety net. If you use GTM for browser tags, TrackSharp handles the deduplication (using `event_id`) to prevent double counting.
    9892
    99 If you are already sending a browser `purchase` event (for example via GTM), make sure you avoid double counting in GA4:
    100 * disable the browser purchase tag, or
    101 * configure deduplication using the same `event_id`.
    102 
    103 = How does GA4 deduplication work? =
    104 GA4 can deduplicate browser and Measurement Protocol events when they share the same `event_name` and `event_id` and are associated with the same user/session.
    105 
    106 TrackSharp uses deterministic `event_id` values for server-side Purchase events based on the WooCommerce order ID.
    107 
    108 = Does this work without WooCommerce? =
    109 No. TrackSharp is built specifically for WooCommerce orders.
     93= Do I need a GTM server container (Stape / Google Cloud)? =
     94No! That is the main benefit of TrackSharp. It runs directly on your WordPress server. You save €20-€100/month on external server hosting costs compared to container-based solutions like Conversios or Stape.
    11095
    11196= Is it GDPR compliant? =
    112 TrackSharp integrates with the WP Consent API and can be configured to respect consent categories. You are responsible for your legal basis and privacy disclosures.
     97TrackSharp integrates with the WP Consent API. It only sends data when the appropriate consent (Statistics/Marketing) is granted. If no CMP is found, you can configure the fallback behavior.
    11398
    11499== Screenshots ==
    115100
    116 1. Dashboard - Attribution Audit Cards (Google Ads + Meta Pixel health)
    117 2. Events Log - filters, status indicators, and CSV export
    118 3. Settings - GA4 credentials and consent configuration
    119 4. Setup Wizard - guided setup and testing tools
     1011.  **Dashboard** - Instantly see "Untracked Google Ads Revenue" and "Pixel Gaps".
     1022.  **Events Log** - Inspect individual API calls and status indicators.
     1033.  **Settings** - GA4 credentials and consent configuration.
     1044.  **Setup Wizard** - Guided 5-minute setup.
    120105
    121106== Changelog ==
    122107
    123108= 1.2.6 =
    124 * Added "Attribution Audit" cards on the Dashboard to highlight tracking risks using real site data (Google Ads click IDs + Meta Pixel coverage).
     109* New: "Attribution Audit" cards on the Dashboard to highlight tracking risks using real site data.
    125110
    126111= 1.2.5 =
    127 * Added a GA4 comparison mode to send server purchases as purchase_sst (optional).
    128 * Increased the default log retention to 180 days for reliable period comparisons.
     112* Added GA4 comparison mode to send server purchases as purchase_sst.
     113* Increased log retention to 180 days.
    129114
    130115= 1.2.4 =
    131 * Added a setting to measure revenue excluding VAT/tax (affects dashboard + GA4/Meta purchase value).
     116* Added setting to measure revenue excluding VAT/tax.
    132117
    133118= 1.2.3 =
    134 * Dutch sites: Upgrade button opens https://tracksharp.nl/#prijzen
     119* Dutch sites: Upgrade button opens https://tracksharp.nl
    135120
    136121= 1.2.2 =
    137 * Initial WordPress.org release
    138 * GA4 server-side Purchase tracking (Measurement Protocol)
    139 * Dashboard + Events Log
    140 * WP Consent API integration and setup wizard
     122* Initial WordPress.org release.
    141123
    142124== Upgrade Notice ==
Note: See TracChangeset for help on using the changeset viewer.