540trainingpdx

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Forum: Plugins
    In reply to: [TrackSure Cloud – Server-Side Tracking, Meta CAPI & GA4 for WooCommerce] Inordinate amount of “(not set)” traffic after in GA4 after implementation
    Thread Starter 540trainingpdx

    (@540trainingpdx)

    2 days, 4 hours ago

    Thank you for the prompt update! I’ve updated the plugin and will let you know if our issues are resolved.

    Looking at the changelog, will server-side events not be sent if the browser event is successfully sent (to prevent duplication)?

    Thanks!

    Forum: Plugins
    In reply to: [TrackSure Cloud – Server-Side Tracking, Meta CAPI & GA4 for WooCommerce] Inordinate amount of “(not set)” traffic after in GA4 after implementation
    Thread Starter 540trainingpdx

    (@540trainingpdx)

    5 days, 2 hours ago

    Here’s an update from our website developer, please let me know if this is enough info to help diagnose:

    Since enabling TrackSure with the GA4 API Secret configured, GA4 traffic has roughly doubled and 50–60% of traffic is showing as Unassigned or (not set).

    The clearest issue is with purchases. Every WooCommerce transaction ID is appearing twice in GA4:

    • One purchase has the correct source, such as google / cpc, google / organic, or (direct) / (none)
    • The second purchase has Session source / medium = (not set)
    • Both copies have the same transaction ID, revenue, and purchase count

    Examples:

    • Transaction 111278: (not set) and google / cpc
    • Transaction 111276: (not set) and google / cpc
    • Transaction 111265: (not set) and google / organic
    • Transaction 111263: (not set) and duckduckgo / organic

    WooCommerce had about 24 real orders, while GA4 reported roughly 47 purchase events.

    The issue also affects other ecommerce events:

    • view_item: 522 events, 497 sessions, 443 users, all with Session source / medium = (not set)
    • add_to_cart: only appears under (not set)
    • begin_checkout: appears once with normal attribution and once under (not set)
    • purchase: appears once with normal attribution and once under (not set)

    For most of the server-side ecommerce events, GA4 shows:

    • First user source / medium: (direct) / (none)
    • Session source / medium: (not set)

    Browser DevTools only shows one GA4 browser request, so the second copy appears to be coming from TrackSure’s GA4 Measurement Protocol integration.

    Can you confirm:

    1. Does TrackSure send both browser and server-side GA4 ecommerce events?
    2. Does the Measurement Protocol request use the visitor’s actual GA4 client_id and session_id from the browser?
    3. How is purchase deduplication handled between browser and server events?
    4. Should the browser and server purchase use the same transaction_id, client_id, and session_id?
    5. Is there a recommended configuration to prevent duplicate GA4 purchases?

    At the moment, the data strongly suggests TrackSure’s server-side GA4 events are being sent under a separate or incomplete GA4 identity/session, causing both the Unassigned traffic and duplicate ecommerce events.

Viewing 2 replies - 1 through 2 (of 2 total)