PressPlay continuously synchronizes with Google Play Console to keep your experiments and data up-to-date. This guide explains how syncing works and how to manage it effectively.
Synchronization is the process of keeping PressPlay's data in sync with Google Play Console. This bi-directional communication ensures:
Experiments created in PressPlay appear in Google Play Console
Results from Google Play Console are imported to PressPlay
Store listing changes are reflected accurately
Status updates happen in real-time
PressPlay automatically syncs on different schedules based on data type:
Experiment Status: Every 30 minutes
Check if experiments started, completed, or paused
Update experiment state in PressPlay
Trigger notifications for status changes
Store Listing Data: Every 6 hours
Fetch current assets and descriptions
Update locale availability
Sync CSL configuration
Experiment Results: Daily
Import conversion rate data
Update statistical calculations
Refresh analytics dashboards
App Metadata: Weekly
Update app version info
Refresh category and ratings data
Check app availability status
Hands-off data management
Always-current experiment status
No manual intervention required
Optimal API quota usage
You can trigger immediate sync when needed:
Navigate to Publishers page
Find the publisher you want to sync
Click the "Sync" button on the publisher card
Wait for sync to complete (2-5 minutes)
All apps under this publisher will be updated
Open the app dashboard
Click the "Sync" button in the top navigation
Wait for sync to complete (30 seconds - 2 minutes)
Only this app's data will be updated
After changes in Google Play Console: If you updated store listings directly
Before creating experiments: Ensure you have the latest data
When data appears stale: Last sync timestamp is old
After reconnecting: Publisher or app was reconnected
Troubleshooting: Investigating sync issues
Before important reviews: Ensure reports show latest data
Apps: List of all apps in publisher account
Store Listings: Current text, images, and assets
Locales: Available languages and regions
Experiments: Running, paused, and completed tests
Results: Conversion data, install counts, statistical metrics
CSLs: Custom store listing configurations
App Metadata: Version, category, ratings (read-only)
New Experiments: Created in PressPlay and pushed to Google Play
Experiment Updates: Priority changes, status changes
CSL Modifications: When experiments require new store listings
Assets: New icons, feature graphics, descriptions
Synced: Up-to-date, last sync timestamp shown
Syncing: Actively synchronizing data
Sync Failed: Error occurred, see error message
Pending: Sync scheduled but not yet started
Never Synced: New connection, sync hasn't run yet
Every publisher and app shows "Last synced" timestamp:
Just now: Synced within last minute
X minutes ago: Recent sync
X hours ago: Normal for automatic schedule
Days ago: May indicate issue; trigger manual sync
Single App: 30 seconds - 2 minutes
Publisher (few apps): 2-5 minutes
Publisher (many apps): 5-15 minutes
Initial Connection: 5-20 minutes
Number of apps in publisher account
Number of locales per app
Number of active experiments
Amount of historical data
Google Play Console API response time
Current API quota usage
Google limits API requests per developer account:
PressPlay manages quotas automatically
Spreads sync requests throughout the day
Prioritizes critical updates (experiment status)
Queues less urgent syncs during high-traffic periods
Sync will be delayed until quota resets (daily)
You'll see a "Quota Exceeded" status message
Critical experiment updates still process
Manual sync requests may be queued
Contact support if quotas are consistently exceeded
If data changed in both PressPlay and Google Play Console:
Experiments: Google Play Console is source of truth
Results: Always from Google Play Console
Pending Changes: PressPlay changes push to Google Play
Status Updates: Most recent change wins
PressPlay handles conflicts automatically:
Logs conflicts for review
Notifies via Slack if configured
Shows warnings in UI when conflicts occur
Provides manual override options when needed
Expected behavior for large publishers (10+ apps)
Let it run; don't trigger multiple syncs simultaneously
Check Google Play Console API status
Contact support if sync runs over 30 minutes
Check publisher OAuth connection status
Verify Google Play Console permissions
Check if app was suspended or removed
Review error message for specific cause
Try reconnecting the publisher
See Sync Errors troubleshooting guide
Verify sync timestamp is recent
Trigger manual sync
Hard refresh browser (Ctrl+Shift+R)
Clear browser cache
Check if changes were made in correct locale/CSL
Wait for automatic sync to run (up to 30 minutes)
Trigger manual sync
Verify experiment was approved in PressPlay
Check experiment status in Google Play Console directly
Ensure experiment meets Google Play requirements
Let automatic sync handle routine updates
Use manual sync strategically, not constantly
Sync before creating new experiments
Check sync status before reviewing reports
Monitor for sync failures and address promptly
Don't trigger multiple syncs simultaneously
Wait for sync to complete before making changes
Avoid making concurrent changes in PressPlay and Google Play Console
Keep Google Play Console permissions up-to-date
Monitor API quota usage if you have many apps
Review sync timestamps daily
Set up Slack alerts for sync failures
Address sync errors immediately
Document any recurring sync issues
Contact support for persistent problems
Choose which data types to sync
Sync specific apps instead of all
Prioritize certain experiments
Custom sync schedules
Receive notifications when sync completes
Trigger external workflows on sync events
Integrate with CI/CD pipelines
Now that you understand syncing:
Set up Slack Integration for sync notifications
Review Understanding App Status for status monitoring
Learn about Connection Issues troubleshooting
Explore Sync Errors common problems and solutions
