live-unnestedoperated by: Chartboost, Inc. (get company information on datarequests.org, go to tracker entry in the Exodus database)
Endpoint URLsThese 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 stepsEvery 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.
- Parse the request body as JSON. Store that in the result for the request body.
- Decode the result for the request body at
identityas a Base64 string. Replace the existing value.
- Parse the result for the request body at
identityas JSON. Replace the existing value.
1res.body = parseJson(body) 2res.body.identity = decodeBase64(res.body.identity) 3res.body.identity = parseJson(res.body.identity)
Observed data transmissionsThis 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.
|Property||Context||Path||Examples of observed values|
|Device advertising ID||body|
|Is device rooted?||body|
|Network connection type||body|
|Tracker SDK version||body|