Cross app usage
Try this endpoint · Response attributes
Weighted connection between apps based reviews data. It is not meant to tell you the exact # of users who use both apps, but rather is meant to be used to understand proportions. For instance If App A and B had an weight_sim value of .80 and App A and App C had a value of 0.2, you could confidently assume that users of App A are 4x more likely to also be active users of App B versus App C.
Endpoint path: /api/:store/app_graph
Query parameters
Section titled “Query parameters”| Param | Description |
|---|---|
id |
store specific app id |
date |
date in ISO 8601 format for which to find app graph data |
| country_iso | two digit country codes in ISO 3166-1 format (itunes_connect) OR two digit language codes in ISO 639-1 format (google_play) |
Response fields
Section titled “Response fields”| Field | Description |
|---|---|
| weight | (legacy calculation) |
| weight_sim | Calculated by dividing the [Total Overlaps between App A and App B] / [ Total Possible Overlaps…i.e. total reviews of App B]. This is important as this is the reason you don’t see Facebook & Google Maps at the top of every Cross App Usage chart. Instead the above Weight highlights the strongest cross app usage based on size and relevancy. This value matches the value displayed in the Apptopia web tool. |
This dataset is being updated on a monthly basis, hence only year and month parts of a date date value are being used to address a requested dataset. Pulling data for different dates within the same month will result in identical responses.
In order to pull Instagram iTunes Cross App Usage for May 2020 in US, the following can be used:
curl -X "GET" "https://integrations.apptopia.com/api/itunes_connect/app_graph?id=389801252&date=2020-05-01&country_iso=US" \ -H "Authorization: $APPTOPIA_TOKEN"Discovery Endpoint for App Graph /api/:store/app_graph/discovery takes the same partition parameters as other discovery endpoints.
Discovery Endpoint also includes query parameters:
| Param | Description |
|---|---|
from |
optional date in ISO 8601 format |
to |
optional date in ISO 8601 format |