Clarify landingPageDeviceInfo.userAgent timing in Data Manager API docs

Esamina il riferimento AdIdentifiers collegato e le descrizioni condivise di DeviceInfo ed eventDeviceInfo, concentrandoti sul momento di acquisizione di landingPageDeviceInfo.userAgent. Il lavoro è completato quando la documentazione distingue esplicitamente il contesto del dispositivo della pagina di destinazione dell’annuncio dal contesto al momento dell’evento di conversione, oppure conferma che non sono necessarie modifiche.

Hi Google Data Manager API team,

I found an ambiguity in the documentation for:

https://developers.google.com/data-manager/api/reference/rest/v1/events/ingest#AdIdentifiers

The field adIdentifiers.landingPageDeviceInfo is described as device information collected when the user entered the advertiser website after interacting with an ad. That suggests the userAgent should come from the landing page / ad click context.

However, landingPageDeviceInfo uses the shared DeviceInfo object, and the DeviceInfo description says it contains device information used at the time of the event. For a conversion event such as a purchase, “event time” can be interpreted as the purchase/checkout moment, not the original ad landing moment.

Could you clarify the intended source for:

adIdentifiers.landingPageDeviceInfo.userAgent

Specifically, should this be:

The user agent captured at the ad landing page visit/click, matching the click identifiers/session attributes in adIdentifiers, or
The user agent captured at the conversion event time, e.g. checkout/purchase?
There is also eventDeviceInfo, which seems to fit the conversion event-time device context. Because of that, I assume:

adIdentifiers.landingPageDeviceInfo.userAgent = user agent from the ad landing page visit
eventDeviceInfo.userAgent = user agent from the conversion event time
Please confirm if this interpretation is correct. It would help if the docs explicitly stated the expected timing/source for landingPageDeviceInfo.userAgent, especially when the same DeviceInfo type is reused in multiple contexts.

Thanks.