Audience and dynamic values
Audience rules refine who can see an in-product survey after page targeting matches. Dynamic values let you personalize content with data from your application.
Audience rules
Section titled “Audience rules”Use attribute-based conditions when URL and device targeting are not enough. Typical attributes teams send:
- Plan or tier
- Role (end user versus admin in your product, not FromUsers roles)
- Account age or activation flags
- Beta feature enrollment
Configure audience rules
Section titled “Configure audience rules”- Instrument your app to provide user attributes to the SDK (see JavaScript API and
FromUsers.init). - Open the survey’s audience settings.
- Add rules that must match for eligibility.
- Test with two staging users: one who should match and one who should not.
Keep attribute names stable. Renaming fields in your app without updating rules silently stops matches.
Dynamic values
Section titled “Dynamic values”Dynamic values inject application data into survey experiences (for example greeting text or logic variables). Flow:
- Send values when you initialize or update the SDK context.
- Reference those values in survey content or logic where the builder allows.
- Preview with sample values before Live.
Only send values you are comfortable storing with responses under your privacy policy.
Combined example
Section titled “Combined example”You want feedback from Pro-plan editors on the new editor page:
- Page targeting: URL starts with
/editor. - Audience: plan equals
proand role equalseditor(your product attributes). - Trigger: time on page 15 seconds.
- Frequency: once ever.
- Dynamic value: include the feature flag name in the question text if you pass it.
Privacy and compliance
Section titled “Privacy and compliance”- Do not send passwords, full payment data, or unnecessary personal data.
- Disclose in-product research in your privacy notice when required.
- Limit who can export results that include attribute payloads.
Limitations
Section titled “Limitations”- Audience rules cannot evaluate attributes you never send.
- Client-provided attributes can be changed by a technical user. Treat them as UX targeting, not security authorization.
- Page targeting and frequency still apply even when audience matches.
Related
Section titled “Related”Common questions
How do user attributes reach FromUsers?
Pass them through the SDK initialization or related JavaScript API usage so audience rules can evaluate plan, role, or other properties you send.
What are dynamic values?
Values from your app that can personalize survey content or logic, such as plan name or feature flags you choose to send.
Can I target only paying customers?
Yes, if your app provides an attribute the audience rule can match, for example a plan attribute you set at init.