Skip to content
AppDues
Log in
Contact salesSign up

Ship the product, hand off the monetization plumbing

Product teams lose time to two recurring jobs: keeping in-app purchase code in step with Apple and Google, and reconciling purchase data across platforms before anyone can trust a number.

A managed subscription layer takes both off the roadmap so the team can spend its cycles on features, experiments, and retention. This overview explains what such a layer covers, how the setup sequence runs, and how to judge whether it fits your team.

The setup sequence

Three steps describe the integration path:

  1. Configure products. In the dashboard, map the products you created in the app stores to offerings and packages.
  2. Connect the SDK. The Purchases SDK is designed for straightforward integration and covers the major platforms and frameworks.
  3. Fetch, subscribe, unlock. Retrieve product details and complete a purchase in a few lines of code, then unlock entitlement.

After that, day-to-day work happens in the dashboard rather than in a release cycle.

What the dashboard gives you

The dashboard is the working surface for in-app purchases. It combines a KPI overview with configurable visualizations in Charts, and a Customers view that centralizes cross-platform customer data so behavior is easier to understand and support requests are easier to resolve. A public demo lets you click through the interface before committing.

Reducing churn work

Three levers address churn directly:

  • A self-serve subscription hub, the Customer Center, lets customers manage their own plans and cuts engineering and support load.
  • Cancellation surveys capture the reason behind a cancellation, feeding product decisions.
  • A targeted offer shown just before cancellation gives the customer a reason to stay.

Used together, these convert churn from a support queue into a feedback loop.

How each team benefits

The same dataset serves different jobs:

  • Marketing gets deep analytics and a cross-platform source of truth for customer data.
  • Data is freed from ad-hoc requests, troubleshooting, and re-checking accuracy.
  • Product can let user insight shape the roadmap because the underlying data is clean and cross-platform.
  • Support can debug issues and grant exceptions using a customer-level view of usage and purchase history.
  • Engineering can spend time on value-added features instead of IAP plumbing.

ConfigureTargetTest

A worked example

Suppose a product team wants to test a new annual price. They create the product in the app store, map it to an offering in the dashboard, and launch an A/B test through Experiments. Because the configuration is remote, no app update is needed. Charts then shows whether the new price changed conversion across the funnel, and the event stream forwards the purchase to the marketing stack so onboarding messages match the plan the customer chose. If the test loses, the team reverts the offering in the dashboard. The whole loop stays inside the product team's control.

Frequently asked questions

Do I need to write server code to handle purchases?

The platform is built so that in-app purchases and subscriptions work on iOS, Android, and the web without server code on your side. Purchase events are processed server-side by the platform and forwarded to your stack.

Which platforms are supported?

iOS, Android, and the web. For the exact list of platforms and frameworks the Purchases SDK supports, see {{OWNER_PLATFORM_SUPPORT_LIST}}.

Can we change pricing without an app release?

Yes. Remote configuration lets you manage pricing and products from the dashboard without shipping an app update.

How many metrics can we track?

Charts offers filters and segmentation for drill-down across its key subscription metrics. The current metric count is {{OWNER_METRIC_COUNT}}.

Does paywall testing show the full funnel?

Experiments is built for easy A/B deployment and reports how a test affects the entire subscription funnel, not only the paywall step.

How does the platform help with churn?

Three tools work together: a self-serve Customer Center for plan management, cancellation surveys that capture reasons, and a retention offer shown just before cancellation.

Can we try the dashboard before signing up?

A public demo of the dashboard is available at {{OWNER_DEMO_AVAILABILITY}}. Free-tier terms are {{OWNER_FREE_TIER_TERMS}}, and included features are {{OWNER_FEATURE_SUITE_STANDARD}}.