Skip to content
AppDues
Log in
Contact salesSign up

Flexible discounts for Web Billing

Store promo codes are built for trials and introductory pricing, so a straight percentage off a regular subscription price has no home there. Web Billing discounts fill that gap: you define a percentage and a code, decide how long the reduction lasts, and choose how buyers receive it — a pre-filled link, a programmatic call, or a field they type into at checkout. This guide walks the three duration models, the three application routes, and the two rules that most often surprise teams: calendar-based expiry and the intro-offer conflict.

Why the web is the place for a real price cut

App Store and Google Play promo codes are limited to free trials and introductory pricing. Neither marketplace supports a percentage-off or fixed-amount reduction on your normal subscription price. That means a campaign like 30% off for a lapsed segment cannot be delivered through store codes at all — the web checkout is where it becomes possible.

Typical reasons to reach for a code: a seasonal sale, an influencer or partner arrangement, or a win-back push aimed at people who already churned. Each of those wants a visible, time-boxed price change rather than a trial, which is exactly the shape store codes do not offer.

Choosing a duration: one-time, forever or time-window

Every discount you create carries a duration rule, and that rule decides which invoices get the reduced price. The three options behave very differently once renewals start.

  • One-time — only the first invoice is discounted. Later renewals return to full price.
  • Forever — every future invoice keeps the discount, with no end date.
  • Time-window — every invoice generated inside a calendar period is discounted, then the price returns to normal.

The trap is the third option. A time-window is measured on the calendar, not on billing cycles. Picture a weekly subscription bought with a one-month discount: the initial payment and each weekly renewal inside that month are reduced. Now picture an annual subscription with the same one-month discount: only the first payment falls inside the window, so the renewal a year later is billed at full price. Same discount, same window, very different outcome — driven entirely by how often the customer is billed.

Three ways to get the code in front of a buyer

How the discount reaches the customer depends on the flow you are running.

  1. URL parameter — append the code to a Web Purchase Link, for example ?discount_code=SUMMER30. The discount arrives pre-applied, which suits email campaigns, influencer links and dedicated landing pages where you do not want the buyer to do anything.
  2. SDK — apply the discount programmatically through the Web Billing SDK, for in-app or server-side flows where the code is chosen by your system rather than typed by the buyer.
  3. Checkout UI — leave a promo code field in the web checkout so the buyer can enter a code themselves.

You also decide whether that field appears at all. Coupon-field visibility is set per Web Purchase Link or per Funnel checkout, so a flow that should feel frictionless can hide it while a campaign page can show it.

Scope, eligibility and the intro-offer conflict

Two scoping decisions sit on top of the duration rule. A code can be tied to specific products or applied across everything you sell. Separately, eligibility criteria can restrict which users are allowed to redeem a given discount — useful when a code is meant for one segment rather than the open public.

The hard rule to design around: discounts and introductory offers do not stack. If a discount is applied to a purchase, any configured intro offer is ignored. Before launching a campaign, check whether the products in scope still carry intro offers; if they do, decide deliberately which one you want the buyer to receive, because the discount wins and the intro offer silently drops out.

What is available now and what is still coming

Discount creation and management happen in the Web Billing dashboard. Whether your account has access is a product commitment you should verify before planning a launch around it — treat availability as something to confirm rather than assume. Two capabilities were announced as forthcoming rather than shipped: Funnels support and discount code analytics. Plan reporting around that gap — you can run the campaign, but do not assume per-code performance reporting is in place yet. Check the current status of both before you rely on them. The documentation linked below is the place to confirm current behaviour, and the setup path in your own dashboard is the one your account exposes.

Discount duration outcomes by billing frequency
Duration settingWhich invoices are discountedWeekly subscription, 1-month windowAnnual subscription, 1-month window
One-timeFirst invoice onlyInitial payment onlyInitial payment only
ForeverAll future invoices, no end dateEvery renewal, indefinitelyEvery renewal, indefinitely
Time-windowInvoices generated inside the calendar periodInitial payment plus weekly renewals within the monthInitial payment only; the next annual renewal is full price

Outcomes follow the calendar-based time-window rule described for Web Billing discounts; the weekly and annual columns illustrate that rule rather than quoting measured results.

Where to apply a discount code
MethodHow it is appliedBest fitBuyer action required
URL parameterAppend ?discount_code=CODE to a Web Purchase LinkEmail campaigns, influencer links, targeted landing pagesNone — discount is pre-applied
SDKApplied programmatically via the Web Billing SDKIn-app or server-side flowsNone
Checkout UIBuyer enters the code in the web checkout fieldOpen campaigns and self-serve redemptionTypes the code; field visibility set per Web Purchase Link or Funnel checkout

Field visibility is configured per Web Purchase Link or Funnel checkout, so the checkout-field route only exists where you have enabled it.

Pre-launch checks for a web discount campaign
CheckWhy it matters
Pick the duration model against actual billing frequencyA calendar window can cover many renewals on a weekly plan and only one payment on an annual plan
Confirm whether products in scope carry intro offersDiscounts do not stack with introductory offers; the intro offer is ignored when a discount applies
Decide product scopeCodes can target specific products or apply globally
Decide eligibility criteriaControls which users can redeem a given discount
Choose the delivery routeURL, SDK and checkout field reach buyers differently
Set coupon-field visibility per flowOnly show the field where self-serve entry makes sense
Check reporting expectationsDiscount code analytics were announced as forthcoming

A planning aid assembled from the described feature behaviour, not a record of a specific campaign.

Frequently asked questions

Can I offer 30% off to churned subscribers through the App Store or Google Play?

Not on your regular subscription price. Both stores limit promo codes to free trials and introductory pricing and do not support percentage-off or fixed-amount reductions on the standard price. A percentage-based win-back offer has to run through web checkout.

If a customer on a weekly plan gets a one-month discount, how many payments are reduced?

The initial payment plus every weekly renewal that falls inside that calendar month. The window is measured on the calendar, not on billing cycles, so a more frequent billing schedule means more discounted invoices within the same period.

What happens to an introductory offer when a discount code is used?

The discount takes precedence. Discounts do not stack with introductory offers or trials, and any configured intro offer is ignored once a discount is applied. Decide in advance which of the two you want a given buyer to receive.

Can I hide the promo code field on some checkouts?

Yes. Coupon-field visibility is configurable per Web Purchase Link or Funnel checkout, so you can keep it out of flows where a pre-applied link discount is the intended path.

Can a discount code be limited to certain products or certain users?

Both. Codes can be scoped to specific products or applied globally, and eligibility criteria can be configured to control which users may redeem a given discount.