Skip to content
AppDues
Log in
Contact salesSign up

Tracking Trial Conversions for SKAdNetwork Attribution

Subscription apps often judge ad quality by whether a free trial becomes paid, yet that change happens in the background after the trial ends. This guide explains how to record trial timing, detect the switch to paid, and report it within SKAdNetwork windows, comparing a local check with silent-push approaches.

Why trial conversion is the key signal

Many subscription apps offer a free trial, so teams care about two separate signals: how many installs start a trial, and how many of those trials later become paid. The second signal is harder to attribute because payment begins days later, often while the app is closed. SKAdNetwork 4.0 windows are used as the deterministic frame for judging campaign profitability, and the trial-converted event should carry high priority in the conversion-value mapping because it connects spend to revenue.

Match the event to the trial length

Choose the window from trial length before writing code. Trials shorter than seven days generally belong in window two, where postback sequence equals one. A seven-day trial belongs in window three, where postback sequence equals two. Starting a trial remains useful for diagnosing the funnel, but it does not tell you which campaigns produce paying subscribers.

The closed-app gap

SKAdNetwork only lets an app update conversion values during user interaction. That creates a gap for events that occur with the app closed, including trial-to-paid switches. Without a workaround, you cannot reliably judge paying-user quality, estimated revenue by campaign, or closed-app conversions. Adding an event name in an ad platform does not by itself change what the app can report.

Option 1: verify on app open

At purchase time, record whether a zero-price trial began, its start date, duration, and expiration date, deriving duration from the store product data. Then, each time the app returns to the foreground, check whether the trial has expired and whether the entitlement is now active with a normal period type. If both are true, send the premium trial-converted conversion value and clear the trial flag so it is not reported twice. The supplied purchase and manager implementations are protected modules code0001 and code0002.

Local check: trade-offs

This local approach is simple, needs no extra server, and centralises conversion-value handling. Its weakness is timing: the user must open the app before the SKAdNetwork window closes. Device-time manipulation can also distort local date calculations, although server-side entitlement validation reduces that risk.

Option 2: add silent push

A server can store the push token, trial start, and duration, calculate expiration, and send a silent push when the trial should end. The app then runs the same foreground check. If the user is still on trial, it can tell the server to retry later; if the user is premium, it reports the event. This raises the chance of reporting inside the window and reuses local logic, but it still depends on an in-app check. A fuller integration receives subscription-status changes directly from Apple server-to-server notifications, uses the transaction identifier to match the user, and sends a silent push so the app can report without the manager check. That route is more accurate and simpler in the app, but requires advanced Apple notification integration and full reliance on a server for event handling.

Decision checklist

Use a decision checklist: confirm trial length and target window; confirm the trial-converted value has highest priority across windows; decide whether app-open checks alone are timely enough; if not, add silent push; if accuracy matters most, integrate Apple server notifications; map values deliberately in the ad platform; and retest the mapping as SKAdNetwork and Ad Attribution Kit evolve. Server events can help track conversions when users are absent, but they do not guarantee perfect accuracy. All approaches must follow Apple policies.

Comparing reporting approaches
ApproachHow it triggers reportingMain benefitMain limitation
Local verificationCheck on app foreground after trial expirationSimple; no extra serverRequires app open before window ends
Silent push with server-calculated expirationServer sends silent push; app rechecks entitlementHigher chance of timely reportingStill needs in-app check
Apple server notifications plus silent pushApple notifies server of premium conversion; server pushes deviceMost accurate; less app logicAdvanced integration; server-dependent

Examples only; customise to your codebase and Apple policy requirements.

Frequently asked questions

Which SKAdNetwork window should hold the trial-converted event?

Place the event in the window that matches your trial length. Shorter trials under seven days point to window two, while a seven-day trial points to window three for free-to-paid analysis.

Can a server event update SKAdNetwork without the app opening?

No. SKAdNetwork conversion values can only be updated while the user interacts with the app, so a backend-only conversion needs local logic on app open or a silent push to wake the app inside the window.