iadsdk-attribution-v2

iadsdk-attribution-v2

operated by: Apple Distribution International Ltd. (get company information on datarequests.org)

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.
  • https://ca.iadsdk.apple.com/adserver/attribution/v2

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. Parse the request body as JSON. Store that in the result for the request body.
1res.body = parseJson(body)

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 IDbodybundleIdcom.storytel.iphone
com.budgestudios.PawPatrolRescueWorld
de.immonet.iphone
com.widget.theme
io.metamask.MetaMask
Other unique identifiers for the user, device, session, or installationbodytoroId2C15A5F4-0557-4376-A73A-428431CFD5C8
11F7A3D8-77DC-4C54-913A-F0497127DE77
E61C2E17-B65E-4582-BCCF-CF03CCFD347C
bodyanonymousDemandId3544A689-C465-43BC-B35A-160988BBDCE4
FCC480D1-6046-4E01-A180-4EA1B954DDF5
58E78BA3-F55F-4837-9AFC-6C720782B056