S

What is Server-to-server notifications?

Definition, examples, and more

Definition

Real-time updates sent from app stores (Apple or Google) to your backend systems when subscription events occur. These could be renewals, cancellations, refunds, or billing issues. These are for maintaining accurate entitlements and powering real-time lifecycle messaging.

Example

When a user's payment fails, Apple sends a server-to-server notification to the app's backend within seconds. Botsi receives this event, updates the user's subscription status, and triggers a CRM campaign: a push notification prompting the user to update their payment method — all automatically, before the user even notices.

Why Server-to-server notifications Matters

S2S notifications are the backbone of real-time subscription management. A streaming app that relied on client-side receipt checks had a 6-hour delay in detecting cancellations, meaning churned users kept premium access for half a day. After implementing S2S notifications via Botsi, entitlements updated within seconds, and they could trigger instant dunning campaigns for billing failures — recovering 20% more failed payments.

Frequently Asked Questions

What events do S2S notifications cover?

Apple V2 notifications include: subscription purchased, renewed, expired, entered billing retry, grace period started, refund requested, price increase consent, and more. Google's RTDN (Real-Time Developer Notifications) cover similar events. Together they give complete real-time visibility into subscription lifecycle.

Do I need to implement S2S notifications?

Strongly recommended. Without them, your app has to poll for status changes, leading to delays and inaccuracies. S2S notifications enable real-time entitlement updates, instant dunning triggers, and accurate analytics. Botsi handles the parsing and routing for you.

How do I set up S2S notifications?

Configure your server endpoint URL in App Store Connect (Apple) or Google Play Console (Google). Your server receives JSON payloads when events occur. Botsi provides a managed endpoint that receives, validates, and processes all notifications — no custom server infrastructure needed.

Category
Subscription App Terminology
Related Area
Mobile App Growth & Monetization
Previous
Segment
Next
Session tracking

More terms starting with “S”

Sandbox environment

A development and testing environment provided by Apple or Google that simulates subscription flows without using real money. It's used to QA paywalls, trial logic, entitlement management, and billing error handling.

Segment

A defined subset of your user base, grouped by shared characteristics like geography, behavior, subscription status, or device type. Segmentation is essential for targeted messaging, pricing strategies, and paywall experiments.

Session tracking

The measurement of user sessions - including frequency, length, and recency of visits. Session data informs engagement metrics, triggers re-engagement campaigns, and identifies power users or at-risk churn cohorts.

Soft paywall

A monetization model where users are given limited access to premium features or content before being asked to subscribe. This try-before-you-buy approach helps build trust and improve conversion by demonstrating value early.

Software development kit (SDK)

A set of tools, libraries, and documentation that developers use to integrate specific functionality into their apps, such as subscription management (e.g., StoreKit, Botsi SDK), analytics, or attribution.

Back to full dictionary

Optimize your subscription pricing with AI

Botsi automatically shows the right price to every user. Stop guessing and start growing.