Skip to main content
All CollectionsSetup GuideApp Store Connector
App Store Connect API <> Looker Studio Setup Guide
App Store Connect API <> Looker Studio Setup Guide

How to active your App Store Connect connector on Data Studio using Easy App Reports

Felipe Sebastiao avatar
Written by Felipe Sebastiao
Updated over 3 months ago

Requirements to activate this integration


Part 1 - Getting API keys and credentials from App Store Connect (with tutorial video)

  1. Go to "Users and Access > Integrations" on App Store Connect.

  2. Click on the "+" sign to generate an API Key

    If you don't see this page or the button, you're not an Admin or Account Holder. In that case, your best option is to ask the owner of your developer account for help.
    ​
    ​

  3. Now we'll do two things: give it a name and set the Access Level.
    ​
    ​Option 1: To unlock all metrics, select "Admin" [πŸ”₯ RECOMMENDED]
    ​Option 2: To unlock "Trends" and "Reviews": "Sales and Reports + App Manager"
    ​Option 3: To unlock "Trends" only: "Sales and Reports"
    ​
    ​See details here on why the Admin permissions are needed to unlock all reports.
    ​
    ​

  4. Well done! Now you need to copy your Key ID and download your API Key:


    ​

  5. Open the API key file to find your Auth key.

    App Store Auth Key example


    ​

  6. The Issuer ID should be visible on the same page (see below)


    ​

  7. And the Vendor ID is available on your Payment and Financial Reports page

Great, now you have everything you need for part two 🀘


Part 2 - Activating your App Store connector on Looker Studio

  1. Edit your App Store connector (link) and add your Key ID, Issuer ID, Vendor ID, and Auth Key precisely as they are:

    IMPORTANT: don't remove the "-----BEGIN PRIVATE KEY-----" and "-----END PRIVATE KEY-----" from the Auth Key field.
    ​

    ​

  2. Now you'll get feedback on your API key credentials. Make sure you have as many "green" statuses as possible as that equals access to more metrics and dimensions.
    ​

    If you see errors on this page, it means that we didn't find all the permissions necessary on the API key. You can go back to step 1.3 and generate a new API key with more permissions if needed.
    ​

  3. Great! Now you can go to Looker Studio through this link. You'll have to open and authorize our connector:

    image

  4. Log in with the email address and password from your EASY APP REPORTS account, not the App Store:


    ​

  5. We recommend you start with "Trends" report. Then click "Connect".

    Pro tip: always rename your data sources! We use "A" for App Store sources and then the name of the report. This will be crucial later when dealing with multiple data sources.
    ​
    ​

  6. That's it; you're in! Now "Create Report" to get started πŸ†

    image


    Once you click "Create Report," you can start building your dashboard.

πŸ€“ We compiled a comprehensive list with all reports and fields in our connector. Check it out!


Visualizing your data

πŸ‘‰ We recommend everybody to start with our Magic Templates. Even if you're building your own thing from scratch, there's an option there for you too ;)

You can also check this video if you want to learn how to use it without any template:

UPDATE: watch the walkthrough for App Store Analytics on this link.

In the video above, we use our own App Store connector for the first time, so you know exactly what to do and what to expect from your first experience on Looker Studio.

In this article, we provide a few extra tips on how to get the most out of your brand-new connector:


Conclusion

From now on, your data will remain available if you don't remove the API keys under your account and own an active subscription.

This means no more dealing with CSVs and wasting time building your app reports! I hope you have a great one with us.

And if you're struggling with your setup, feel free to message us on the chat. We'll be happy to help!


Please consider letting us know if this article was helpful so we can continue improving our documentationπŸ‘‡

Did this answer your question?