Skip to content
AppDues
Log in
Contact salesSign up

How Unscripted Photographers Scoped a Seasonal Sale Paywall to iOS v3.1.16

When a subscription app runs a limited-time promotion, the hard part is often not the offer itself but making sure it reaches only the people who can actually use it.

This guide walks through how the Unscripted Photographers team used audience targeting to launch an end-of-year sale on iOS while leaving Android and older iOS builds untouched, then offers a checklist for planning a similar rollout.

How targeting scoped the offer

The team used a targeting feature that {{OWNER_TARGETING_CAPABILITY}}. The end-of-year sale paywall was scoped to iOS users on app version 3.1.16. That single constraint was intended to keep the promotion away from Android and from older iOS versions, so existing paywalls stayed as they were. The team also said that {{OWNER_SCHEDULING_CAPABILITY}}, which would let a future holiday promotion start and stop without manual intervention.

Checklist for scoping a targeted promotion

Before you schedule a platform- or version-scoped offer, confirm each of the following:

  • Which platform(s) the offer applies to, and whether the other platform's build will be ready.
  • The minimum app version that can render the offer, and what older versions should continue to see.
  • The exact start and end times, including time zones, and whether scheduling is available in your setup.
  • A rollback path if the offer reaches the wrong audience or fails to appear.
  • How you will confirm the offer is visible to the intended group and hidden from everyone else.
  • Who owns the launch and who can pause it if something goes wrong.

Worked example: the iOS v3.1.16 sale

Using this scenario as a model: the offer was an end-of-year sale paywall. The audience was iOS users on version 3.1.16. Android users and older iOS versions were excluded so their existing paywalls were unaffected. The offer was controlled remotely, which lets you change it without shipping a new build. If you mirror this pattern, the two fields that do the most work are the platform condition and the version floor; everything else (price, packaging, paywall layout) sits inside that scope.

Two different failures to watch for

A targeted promotion can fail in two distinct ways, and they need different fixes. First, the offer may not appear for the intended audience, which usually points to a version-floor mismatch, a scheduling error, or a paywall that was not attached to the right audience. Second, the offer may appear for the wrong audience, which usually points to a scope that is too broad or a missing platform condition. Check which one you are seeing before changing anything, because widening the audience to fix a missing offer can create the second problem.

ConfigureTargetTest

Frequently asked questions

Can a paywall promotion be limited to one app version?

In this case, the end-of-year sale paywall was scoped to iOS users on version 3.1.16, which kept the offer away from Android and older iOS builds. The exact controls available depend on your subscription platform and how your paywalls are configured.

What happens to users on older app versions during a targeted sale?

They continue to see whatever paywall their version already supports. Scoping the offer to a version floor is what prevents older builds from receiving a promotion they cannot render correctly.

Can targeted offers be scheduled in advance?

The team in this case said that {{OWNER_SCHEDULING_CAPABILITY}}, which would let a future holiday promotion start and stop without manual intervention. Whether scheduling is available to you depends on your current feature set.

How do I tell whether an offer failed to show or showed to the wrong people?

Check the intended audience first. If they do not see it, look at version floor, scheduling, and paywall attachment. If unintended users see it, look at platform and audience scope. Fixing a missing offer by broadening the audience can cause the second problem.