In this article, I will clarify the object table and JSON output specifically of the 42 Matters ASO app keywords API. I will provide an overview of the structure and contents of the object table and explain how the data is represented in the JSON output. Please note that this article will not cover how to access or use the data, only the format of the object table and JSON output.

Object and Description table

1. trackId: A unique identifier that represents the app being searched.

2. country: The country for which the search is being conducted.

3. lang: The language for which the search is being conducted.

4. number_results: The total number of results found for the given search criteria.

5. pages: The maximum number of pages of results that are available for the given search criteria.

6. has_next: A boolean flag indicating whether there is a next page of results available for the given search criteria.

7. limit: The number of results per page that are being returned.

8. page: The current page number of the results being returned.

9. results: An array of objects representing individual search results.

10. keyword: A string representing the keyword being searched for.

11. difficulty: An integer value on a scale of 0 to 100 representing the estimated competitiveness of targeting the given keyword. 0 is the least competitive and 100 is the most competitive.

12. traffic: An integer value on a scale of 0 to 100 representing the estimated frequency with which the given keyword is being searched. 0 is the lowest traffic and 100 is the highest traffic.

13. rank: An integer representing the ranking of the app for the given keyword. A higher rank indicates a higher position in the search results.

The information in the table is useful for app developers and marketers who are looking to optimize their app's visibility in app stores. The trackId and keyword fields can help identify which app and keywords are being searched for, while the country and lang fields allow for targeted searches in specific regions and languages. The number_results, pages, and has_next fields provide information on the volume and pagination of search results, which can be helpful in understanding the competition for a given keyword. The difficulty and traffic fields give estimates on the competitiveness and popularity of a keyword, which can help inform decisions on which keywords to target in app store optimization efforts. The rank field can help track the performance of an app for a given keyword over time, allowing developers to see the impact of their optimization efforts. Overall, this information can be valuable in improving the discoverability of an app in app stores.

Json output

This JSON output represents search results for an app with a trackId of "284882215" in the United States for the English language. There are a total of 3749 results for this search, spread across 375 pages of results with a limit of 10 results per page. The current page being displayed is the first page. The "has_next" field indicates that there are more pages of results available beyond the current page. The "results" field contains an array of objects, each representing a single search result. Each object includes the keyword being searched for, an estimate of the competitiveness of targeting that keyword (on a scale of 0 to 100, with 0 being the least competitive and 100 being the most competitive), an estimate of the traffic for that keyword (on a scale of 0 to 100, with 0 being the lowest traffic and 100 being the highest traffic), and the rank of the app for that keyword. In this example, there are three search results listed, each with a keyword related to "facebook", a high level of difficulty and traffic, and a rank of 1.

{
"trackId": "284882215",
"country": "US",
"lang": "en",
"number_results": 3749,
"pages": 375,
"has_next": true,
"limit": 10,
"page": 1,
"results": [
{
"keyword": "facebook",
"difficulty": 88,
"traffic": 99,
"rank": 1
},
{
"keyword": "facdbook",
"difficulty": 87,
"traffic": 98,
"rank": 1
},
{
"keyword": "facabook",
"difficulty": 86,
"traffic": 98,
"rank": 1
},

In conclusion

In this article, we discussed the object table and JSON output of the 42 Matters ASO app keywords API. We explained the structure and contents of the object table and how the data is represented in the JSON output. We also discussed the usefulness of the information contained in the table and JSON for app developers and marketers looking to optimize their app's visibility in app stores. Finally, we provided an example of JSON output and described the various fields and their meanings.

Footnote

You can request access to the 42 Matters ASO app keywords API through the third party data marketplace of Worldindata. Worldindata is a platform that allows users to browse, purchase, and access a variety of APIs from various sources. By requesting access to the 42 Matters ASO app keywords API through Worldindata, you can obtain the necessary credentials to use the API in your own projects and applications. Please note that access to the API may be subject to certain terms and conditions and may require payment of a fee. It is recommended to carefully review the documentation and pricing information provided by Worldindata before requesting access to the API.