Analytics
Custom User Properties
Attach whatever you know about a user, then target paywalls, branch experiments, and personalize copy by it — no app release required.
You already know things about your users — what plan they're on, how long they've been around, which features they touch, where they came from. The hard part has never been knowing it. It's acting on it inside the paywall without filing an engineering ticket for every "what if we showed power users a different offer?" idea. Custom user properties close that gap. You pass Superwall whatever you know about a user, and from then on you can target paywalls, branch experiments, and personalize copy by it — from the dashboard, with no new app build.
Send what you know, once
A single call to setUserAttributes attaches any key-value data you have to the current user — plan tier, signup date, lifetime spend, A/B cohort, referral source, favorite category, anything. It's a merge, so each call updates the keys you pass and leaves the rest alone, and passing nil clears a value. You define the vocabulary; Superwall stores it against the user and makes it available everywhere campaigns are decided.
Your data, your names: set strings, numbers, booleans, URLs — whatever describes the user in terms your team already thinks in.
Device context comes free: alongside your custom properties, Superwall automatically exposes device properties like
deviceLocale,deviceCurrencyCode,osVersion,daysSinceInstall, andtotalPaywallViews— no instrumentation needed.A built-in test seed: every user also gets a
seedvalue from 0–99, so you can split experiments evenly without inventing your own bucketing.
Target paywalls by who the user actually is
Once a property exists, it becomes a filter you can reference in campaign audiences. Audiences are evaluated top to bottom, and the first one a user matches decides which paywall they see. So "annual subscribers who churned" can get a win-back offer, "trial users on day 6" can get an urgency paywall, and everyone else falls through to your default — all configured in the dashboard, all changeable in minutes.
Build a campaign audienceYou're not limited to a single equality check. Audiences support rule groups that combine your custom properties with device context, entitlement status, and event counts over time using AND/OR logic — for example, "plan = free AND opened the app at least 3 times this week AND deviceCurrencyCode = USD." The segment is as precise as the data you send.
Run experiments on real segments
Custom properties turn your A/B tests from "show everyone the same two variants" into "test the right offer on the right people." Define an audience by a property, then split it across paywalls by percentage — show one variant to 70% and another to 30% — and read the results per segment. Assignments are sticky: changing a split only affects new users, so people who already entered a test keep the experience they were assigned and your data stays clean.
Personalize the paywall itself
The same properties you target on can be dropped straight into paywall copy. Reference them as template variables so a paywall can greet someone by name, call out the plan they're on, or reflect their currency and locale — without designing a separate paywall for every variation. One template, personalized per user at display time.
Browse template variablesWhat you can do with it
Show lapsed subscribers a win-back offer while new users see your standard paywall.
Gate a premium price test to high-intent users and leave everyone else untouched.
Branch onboarding and paywall flows by referral source, plan tier, or signup cohort.
Personalize headlines and pricing copy with the user's name, plan, or local currency.
Adjust any of the above from the dashboard the moment a segment behaves differently — no release cycle.
Get started
Set your first attributes with setUserAttributes, then build an audience around them in a campaign. Follow the quickstart to install the SDK, or create a free Superwall account and start targeting by what you already know.