Incomplete documentation for Measurement [243678686]

Bug

Status Update

No update yet.

Description

ro...@gmail.com

created issue #1

Aug 24, 2022 05:51PM

Summary:

Documentation related to event params session_id and session_number missing.

Session Id and Session number is required to be sent with the measurement api parameters for session channel grouping is to be correctly attributed, else data used in Google Ads connector and Google ads cpc / Cross-Network attribution is lost when sending purchase events server side / measurement protocol 4

https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference/events

https://developers.google.com/s/results/analytics/devguides/collection/protocol/ga4?q=session_number

Following example event shows up using the GA4 DebugView with correctly assigned ga_session_id and ga_session_number

POST /mp/collect

{
  "client_id": "1194932241.1645610030",
  "events": [
    {
      "name": "purchase",
      "params": {
        "timestamp_micros": "1659348524683755",
        "session_id": "1661343705",
        "session_number": 1,
        "currency": "SEK",
        "value": 12.11,
        "debug_mode": true
      }
    }
  ]
}

Comments

ke...@google.com <ke...@google.com> #2Aug 25, 2022 07:00AM

Reassigned to ke...@google.com.

redacted

ro...@gmail.com <ro...@gmail.com> #3Aug 25, 2022 07:54AM

‫في الثلاثاء، 8 نوفمبر 2022 في 2:39 ص تمت كتابة ما يلي بواسطة
‪samaabunail‬‏ <‪buganizer-system@google.com‬‏>:‬

- Show quoted text -

lo...@e-net-b.be <lo...@e-net-b.be> #4Aug 25, 2022 07:56AM

Hi,

Normally, the client_id or user_id are used for session channel grouping is to be correctly attributed, but it doesn't work...

I use both and I have this problem of losing channel and source country on the events that use the API, in the report user acquisition, the events/conversions are well assigned, but in traffic acquisition, I have all the sales and my API events that are in "Unassigned" and in demographics, it's assigned to "(not set)", while we can't set these values manually in API, they should be reconciled with the JS that uses the same user_id & client_id anyway...

Analytics-Acquisition-d-utilisateurs-Premier-regroupement-de-canaux-par-défaut-de-l-utilisateur.png

81 KB

View

Download

Analytics-Acquisition-de-trafic-Regroupement-de-canaux-par-défaut-de-la-session.png

80 KB

View

Download

Analytics-Données-démographiques-Pays.png

97 KB

View

Download

ke...@google.com <ke...@google.com> #5Aug 26, 2022 05:23AM

Hi Robin,

Thank you for providing more information.

I can confirm that source / medium information is not yet supported in Measurement Protocol for GA4. The Measurement Protocol for GA4 is only intended to supplement events already collected via other libraries such as the SDKs and gtag.js. We've already raised a feature request on this, however, we're unable to provide a timeline on when it will be supported. You may follow the Google Analytics API Notify group for future updates.

@lois - Since your concern is a bit different with the original issue in this thread, I suggest you reach out to our team directly via this link and provide more details about your observations such as sample payload that you're sending to Google Analytics and some screenshots of an existing data with the same client_id or user_id for our reference.

Regards,

Kevin Soriano, Google Analytics API Team

an...@byax.se <an...@byax.se> #6Sep 1, 2022 01:17PM

Hi Kevin,

The `session_id` parameter is referenced in the changelog of the GA4 MP, but hasn't been added to the general documentation.

https://developers.google.com/analytics/devguides/collection/protocol/ga4/changelog#2022-05-23

Best Regards,
Andreas

ke...@google.com <ke...@google.com> #7Sep 2, 2022 07:07AM

Hi Andreas,

Thank you for sharing your insights. I'll share all the information in this thread with the rest of our team so they can consider updating our documentation. Please note that we're unable to provide a definite timeline on when the documentation will be updated. Feel free to check the Measurement Protocol documentation from time to time for future changes.

Regards,

Kevin Soriano, Google Analytics API Team

is...@google.com <is...@google.com> Oct 8, 2023 08:07AM

Status: New

Issue 243678686

Description

Issue summary

Comments

ke...@google.com <ke...@google.com> #2Aug 25, 2022 07:00AM

ro...@gmail.com <ro...@gmail.com> #3Aug 25, 2022 07:54AM

lo...@e-net-b.be <lo...@e-net-b.be> #4Aug 25, 2022 07:56AM

ke...@google.com <ke...@google.com> #5Aug 26, 2022 05:23AM

an...@byax.se <an...@byax.se> #6Sep 1, 2022 01:17PM

ke...@google.com <ke...@google.com> #7Sep 2, 2022 07:07AM

is...@google.com <is...@google.com> Oct 8, 2023 08:07AM

Add comment

Issue metadata