Once your Google Play Console publisher is connected, you can add individual apps to PressPlay for A/B testing. This guide explains how to connect apps, verify they're ready for testing, and manage their settings.
After connecting your publisher, PressPlay automatically imports all your Google Play apps. However, you need to explicitly enable each app for testing before you can create experiments.
Log in to PressPlay
Select your publisher from the Publishers list
You'll see all apps associated with this publisher account
Apps display with their name, package ID, and connection status
For each app, you'll see:
App Name: The display name from Google Play Console
Package ID: The unique identifier (e.g., com.example.myapp)
Status: Connection status (Not Connected, Connected, Syncing, Error)
Last Sync: Timestamp of the most recent data synchronization
Active Experiments: Number of currently running experiments
Find the app you want to optimize in the app list
Click on the app card or row
Click the "Connect App" button
PressPlay will initialize the app for testing:
Fetch all store listings and locales
Import current assets (icons, feature graphics)
Create necessary Custom Store Listings (CSLs)
Set up default experiment settings
Wait for the connection process to complete (typically 1-3 minutes)
Once connected, the status will change to "Connected"
When you connect an app, PressPlay:
Imports Locales: All store listing languages/regions (e.g., en-US, de-DE)
Creates CSLs: Sets up Custom Store Listings for experiment isolation
Fetches Assets: Downloads current icons, feature graphics, and screenshots
Configures Defaults: Sets default experiment durations and priorities
Enables Tracking: Starts monitoring for experiment opportunities
To connect an app successfully, it must meet these criteria:
Published Status: App must be published on Google Play Store (not just drafted)
Store Listing Complete: At least one locale with complete store presence
Assets Present: Minimum required assets (icon, feature graphic) uploaded
Active Listing: App must be available (not removed or suspended)
After connecting an app, verify it's set up correctly:
Click into the connected app
Check the App Dashboard for:
Number of available locales
Current assets displayed correctly
CSL status showing "Active"
No error messages or warnings
Navigate to Settings to review:
Default experiment duration
Default priority values
Enabled locales for testing
Once connected, each app has a dedicated dashboard showing:
App metadata (name, package ID, version)
Connection status and last sync time
Quick stats (experiments run, active tests, completed tests)
Active experiments currently running
Pending experiments in the backlog
Recently completed experiments
Quick access to create new experiments
Current store listing assets
AI-generated assets pending review
Asset generation history
Upload new assets manually
Experiment defaults by asset type
Enabled/disabled locales
Slack integration settings
Advanced configuration options
Navigate to your app dashboard
Click "Settings" in the app navigation
Configure defaults for each asset type:
Duration: Default test length (e.g., 14 days)
Priority: Default priority for new experiments
Auto-approve: Whether to skip review step (advanced)
Click "Save Settings"
Go to Settings → Locales
Review the list of available locales
Toggle locales on/off for testing:
Enabled: Can create experiments for this locale
Disabled: Locale hidden from experiment creation
Save your changes
Tip: Disable locales you don't plan to test to simplify the UI.
If you need to stop testing an app:
Go to the app dashboard
Click the three-dot menu in the top-right
Select "Disconnect App"
Review the warning about active experiments
Confirm disconnection
Important: Disconnecting an app:
Stops PressPlay from managing experiments
Does NOT stop experiments running in Google Play Console
Removes the app from your PressPlay dashboard
Historical data remains but is archived
To reconnect an app:
Go to your publisher's app list
Find the disconnected app
Click "Connect App" again
PressPlay will re-sync the app data
Previous experiment history may be restored if experiments are still active in Google Play
When managing many apps:
Use the search bar to filter apps by name or package ID
Sort apps by status, last sync date, or number of active experiments
Select multiple apps to sync them simultaneously
View aggregate statistics across all apps
Best practices for multiple apps:
Connect only apps you actively plan to test
Use consistent naming conventions
Set similar experiment defaults for related apps
Group apps by team or product line in Slack channels
Apps sync with Google Play Console automatically and on-demand. See Understanding App Status for detailed status explanations.
Connected: App is active and ready for experiments
Syncing: Currently updating data from Google Play
Sync Error: Issue with data synchronization (see troubleshooting)
Not Connected: App imported but not enabled for testing
Verify app is published in Google Play Console
Trigger a manual publisher sync
Check that app has at least one store listing
Wait 10-15 minutes after initial publisher connection
Ensure app meets all requirements (published, has assets, etc.)
Check Google Play Console for app status
Verify publisher connection is still active
Try disconnecting and reconnecting the publisher
Check if Google Play Console has CSL limits reached
Verify app has complete store listings
Contact support if issue persists
Trigger a manual app sync
Check that assets exist in Google Play Console
Verify asset formats meet Google's requirements
Clear browser cache and refresh
Start Small: Connect 1-2 apps initially to learn the workflow
Verify Settings: Review default experiment settings before creating tests
Enable Key Locales: Focus on your highest-traffic markets first
Monitor Sync Status: Check sync timestamps regularly to ensure data freshness
Document Conventions: Establish team guidelines for experiment naming and prioritization
After adding your apps:
Review Understanding App Status to monitor connection health
Set up Slack Integration for app-specific notifications
Configure Experiment Settings by Asset Type for optimal defaults
Start Creating Manual Experiments or use AI-Generated Experiments
For additional help, see Connection Issues or Sync Errors in our troubleshooting section.
