The 'Platform' Property Not Arriving Consistently to Segment and Destinations – Twilio Support

Issue

'userAgentData' is commonly used to track the platform in events. If the events are not delivering all properties consistently to your Segment implementation (most commonly the platform sub-property), and in turn not sending that data properly over to your assigned destination, you may have an issue with 'userAgentData'.

Product

Segment

Environment

Twilio Segment

Cause

This happens because the 'userAgentData' property is not widely available, and does not work in some of the most widely-used browsers. The following browsers/platform combinations collect 'userAgentData':

Desktop: Chrome, Edge, Opera.
Mobile: Chrome-Android, Opera-Android, Samsung Internet, WebView Android.
Server: Deno

If the browser-platform combination is not mentioned above, then 'userAgentData' will not be collected. However, the 'userAgent' field may be.

Resolution

As a workaround, you can create a source insert function that looks for the 'userAgent' when 'userAgentData' is unavailable and gathers the platform data from the full string received.

Additional Information

Even if you don't apply the recommended resolution, you can still continue receiving the proper 'userAgentData' from all the aforementioned supported browsers.