Got it. If you want the full picture—revenue, subscription churn, cancellation surveys, and all the bulk data—but strictly read-only with zero risk of accidentally modifying their app, we will adjust the permissions.

By keeping it 100% read-only, you can still confidently tell developers: “We can see your data to run our AI models, but we physically cannot alter your store listing, cancel user subscriptions, or reply to reviews.”

Here is the exact Markdown you should use for your Google Play setup page.

---

Connect Your Google Play Store Account

To allow AppDataLayer to securely analyze your app’s performance, revenue, reviews, and crash data, you need to provide a Google Cloud Service Account Key.

🔒 100% Read-Only: We only ask for read-only access. We physically cannot modify your app, alter your store presence, manage subscriptions, or reply to users on your behalf.

Follow the step-by-step guide below to generate your secure, read-only credentials.

Step 1: Find your Package Name

Your Package Name (or Application ID) uniquely identifies your app in the Google Play Store.

1. Open the Google Play Console.
2. Select your application from the dashboard.
3. Your Package Name is displayed right under your application’s name at the top of the page (e.g., com.yourcompany.yourapp).
4. Copy this value and paste it into the Package Name field in AppDataLayer.

Step 2: Enable Developer APIs

You need to enable the APIs that allow us to fetch your reports and metrics.

1. Go to the Google Cloud Console API Library.
2. Ensure you have a project selected in the top-left dropdown (or create a new one).
3. Search for and Enable the following two APIs:

• Google Play Android Developer API * Google Play Developer Reporting API

Step 3: Create a Service Account

This creates the secure “bot user” that AppDataLayer will use to read your data.

1. In the Google Cloud Console, navigate to IAM & Admin > Service Accounts.
2. Click Create Service Account at the top.
3. Give it a clear name (e.g., AppDataLayer Read-Only) so you remember what it is used for.
4. Click Create and Continue, then click Done. (You do not need to assign any Google Cloud roles for this step).

Step 4: Download the JSON Key File

Now, generate the file you will upload to AppDataLayer.

1. In the Service Accounts list, click the three-dot menu (Actions) next to the account you just created and select Manage Keys.
2. Click Add Key > Create new key.
3. Select JSON as the key type and click Create.
4. A .json file will automatically download to your computer. Keep this secure!

Step 5: Grant Read-Only Permissions in Google Play Console

Finally, you must give this new Service Account permission to read your app’s data in the Play Console.

1. Go back to the Google Play Console.
2. Navigate to Users and Permissions on the left menu.
3. Click Invite new users.
4. In the Email address field, paste the email of the Service Account you created in Step 3 (it looks like name@project.iam.gserviceaccount.com).
5. Under App permissions, add your specific app.
6. Under Account permissions, check ONLY the following read-only boxes:

• ✅ View app information and download bulk reports (read-only) * ✅ View financial data, orders, and cancellation survey responses * ✅ View app quality information (read-only) * (⚠️ Do NOT check “Manage orders and subscriptions”, “Reply to reviews”, or “Release to production”. Keep it strictly read-only!)

7. Click Invite user.

Step 6: Connect to AppDataLayer

1. Go back to the AppDataLayer Add Store Credentials screen.
2. Enter a Label (e.g., “My Android App”).
3. Paste the Package Name you copied in Step 1.
4. Upload the .json file you downloaded in Step 4.
5. Click Save Credentials.

(Note: It can take Google up to 24-36 hours to fully activate new Service Account permissions. If your dashboard doesn’t populate immediately, check back tomorrow!)

---

That gives you the financial data, the reviews, the crash reports, and the CSV dumps, while keeping the API key completely neutered from making changes.

Would you like me to write the matching documentation for the Apple App Store (Issuer ID, Key ID, and .p8 file) next?