Branch Attribution API (branch-io/v1
)
operated by: Branch Metrics, Inc.
(get company information on datarequests.org, go to tracker entry in the Exodus database)The Branch Attribution API is used for “deep linking and session attribution. […] Every time the API is called, it will track an INSTALL, REINSTALL, or OPEN event in Branch and return deep link data in the response if the session is attributed.”
It can also track “additional downstream conversion events” like PURCHASE.
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:\/\/api2?\.branch\.io\/v1\/install$/
/^https:\/\/api2?\.branch\.io\/v1\/open$/
/^https:\/\/api2?\.branch\.io\/v1\/close$/
/^https:\/\/api2?\.branch\.io\/v1\/profile$/
/^https:\/\/api2?\.branch\.io\/v1\/logout$/
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.- 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.References
- Documentation for
app_version
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
google_advertising_id
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
advertising_ids.aaid
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
ios_vendor_id
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
local_ip
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
os
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
os_version
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
hardware_id
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
metadata.$marketing_cloud_visitor_id
: https://help.branch.io/partners-portal/docs/adobe-analytics - Documentation for
metadata.$braze_install_id
: https://help.branch.io/partners-portal/docs/braze - Documentation for
metadata.$google_analytics_client_id
: https://help.branch.io/partners-portal/docs/google-analytics - Documentation for
metadata.$mixpanel_distinct_id
: https://help.branch.io/partners-portal/docs/mixpanel - Documentation for
metadata.$segment_anonymous_id
: https://help.branch.io/partners-portal/docs/segment-export - Documentation for
metadata.user_id
: https://help.branch.io/using-branch/docs/advertising-identifiers-for-attribution - Documentation for
identity
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
screen_height
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
screen_width
: https://help.branch.io/developers-hub/reference/attribution-api - Documentation for
user_agent
: https://help.branch.io/developers-hub/reference/attribution-api