SensorTower - API

Owned by Graham Tolson (Deactivated)
Last updated: Sept 20, 2021
3 min read

4 products

  • store intelligence

  • usage intelligence

  • ad intelligence

  • app tear down

 

Here is the link to our API reference site that will give you a good initial understanding of how our API works: https://sensortower.com/api/v1/index.  Additionally, this next link is a quick guide to accessing the API token so you can begin to pull data via the API connection: https://help.sensortower.com/s/article/Accessing-API-Token?language=en_US

 

Credentials are under user name graham@knoema.com. Please contact Graham for pass.

 

300 calls per month on API (NOT A ENOUGH TO COVER ALL PRODUCTS)

 

Southpoint data subset.

#Slice for Data set on AppLovin 

#Ticker: APP 

  • 49 title sub studios

  • Focus on Revenue and downloads

  • Ad intelligence network. 

    • Share of ads vs. cross selling ads

“““I spoke with Sensor Tower last week to get a better sense for the use cases.  Here’s what I think would be most useful:

  • Tracking who’s advertising on the AppLovin ad network using Top Advertisers/Publishers in Ad Intelligence.  We’d have to do multiple requests since each request is limited to 250.  I think getting the top 1,000 advertisers would be a good place to start.  We also have to make a separate request for each country.  I think it’d make sense to do the US and then major European and Asian markets.  To make the data easier to consume, they suggested putting all the app IDs in a specific column, then listing share of voice for each country in a certain date range going across

    • To see how much AppLovin is advertising on its own network, it sounds like we’d have to sort it externally and then sum.  It’d be helpful to have an easy way to set this up

    • To see the penetration of gaming versus non-gaming advertisers, they said we could sort by the custom tag for “is a game.”  This would also be useful

  • Tracking who’s advertising on AppLovin’s own apps.  This is in Advertiser Breakdown.  250 per request, the top 1,000 would be good.  In the output, I’d want to be able to sort by publisher name

  • If we have enough pulls, it might also be interesting to see which ad networks AppLovin is using to advertise its own apps.  I think that would involve making requests across all ad networks

  • AppLovin revenue and downloads, with a script added to easily calculate the w/w, m/m, and QTD q/q trends.  It should pull in data from 57 studios

  • If we have enough API pulls, setting up a way to see which AppLovin apps have the biggest increases / decreases in downloads and revenue on a % and absolute basis in a given week, month, or quarter.  Sensor Tower suggested using the App Intelligence à Custom fields Filter to create filter using the custom_fields_filter_id parameter then plugging that in for the ID in Store Intelligence à Top Apps

  • Their SDK breakdown is only available on a real time basis but it’d be good to be about to track SDK penetration over time for the AppLovin ad network and MAX SDKs.  If there’s a way to run this request on a weekly or monthly basis and save the output so we can compare it over time, that’d be great

 

They also mentioned being able to write a script to filter out all the data that’s returned with the API request that we don’t need, which would be helpful.

 

Please let me know if you have any questions or need any of their API documentation.  Thank you!”””

Find Sub Publishers:

  • App Intelligence

  • “Search Apps & Publishers” API Call to find unified publisher id. (Make sure you use unified)

  • Query publishers in “Unified Lookup” with the unified publisher id. Returns all publishers/title sub studios

Find Current API Credits used:

General API Information:

  • For add inteligence, Date returns the period the date falls in. Suggest using Monday as start of period. No time series.

  • For Store & App Inteligence Start Data and End Data returns time series defined by period.

  • Suggested to define params as defaults can cause issues. Not everything is required (bold is required).

  • Some parameters can be combined and used in list. Example: Devices in Top Advertisers/Publishers

  • Store & App Intelligence should be able to be called in 1 query.

  • NO hard limit on API credits/calls.