Workflows
Connecting Google Play
Connecting Google Play lets Paywall Parity read the catalogue an app actually uses. The connection should have only the permissions needed for the product features the account chooses to use.
Updated
What the connection provides
The catalogue includes subscriptions, base plans, offers, one-time products, regional availability, and prices. Importing that structure creates the foundation for comparisons and proposed updates.
A store connection is therefore more than a file upload: it keeps the pricing view tied to the provider's representation of the app.
Permissions should match the intended action
Reading a catalogue and publishing prices are different capabilities. Teams should understand which access is required for analysis and which additional access is required before a live update can be submitted.
The dashboard setup guide supplies the exact current permission and validation steps, where they can remain accurate as the provider changes.
Common connection problems
Failures usually come from an unavailable package, missing Play Console access, a credential that no longer works, or an API permission that has not propagated. Rechecking the package and the service account's app-level role is a useful first step.
Removing a connection affects Paywall Parity's local view; it does not, by itself, rewrite the prices already live in Google Play.