operated by: Google LLC (get company information on

Endpoint URLs

These are URLs or regexes of endpoints the tracker sends data to. We use these to determine which adapter to apply to a request. Some trackers use the same endpoint for several formats. In this case we use additional logic to match the adapter to the request, refer to the code for more information.

Decoding steps

Every tracking library has its own way of transmitting tracking data, often even several. They are regularly pretty convoluted, nested encoding schemes. Because of that, the adapter needs to decode the request information into a consistent format. We try to keep keys and paths intact, but the structure results from our decoding. All steps used in the decoding for this adapter are documented here.
  1. Decode the request body as a protocol buffer (Protobuf). Store that in the result for the request body.
  2. Wrap the result for the request body at 1 in an array if it isn’t one already. Replace the existing value.
1res.body = decodeProtobuf(body)
2res.body.1 = ensureArray(res.body.1)

Observed data transmissions

This is data that we observed being transmitted by this tracker. Not every request contains all of this data. The context of the data describes where we found the data in the request, the path describes the location of the data in the decoded request. The examples are a selection of observed values.
PropertyContextPathExamples of observed values
App IDbody1.*.14com.ea.ios.fifamobile
App versionbody1.*.1615.5.04
6.0.117 (
Device advertising IDbody1.*.19ea70edc1-ac05-481c-8d2a-66b1be496a7e
iOS IDFVbody1.*.279683A1D5-E36B-4071-A809-E3732902BF33
OS namebody1.*.8ios
OS versionbody1.*.914.8