Skip to Content
GuidesWalkthrough: Wallet CES

Walkthrough: Wallet CES

A complete example: ask users how easy it was to understand their wallet, right after they view it. This is the canonical “contextual micro-survey” flow.

Goal: a 1–7 Customer Effort Score question — “How easy was it to understand your wallet balance and payment methods?” — triggered by the wallet screen-view event, capped to once per user per 30 days, at 100% sampling.

Prerequisites

  • A project with your analytics connected.
  • The wallet screen fires an event you can target — e.g. page_view with a property screen = "Wallet".
  • The iOS SDK installed and running with your key.

Create the survey and question

In the survey builder, add one CES question:

  • Prompt: How easy was it to understand your wallet balance and payment methods?
  • Scale: min 1 (“Very difficult”) to max 7 (“Very easy”).
  • Required: yes.

Define the trigger

Add a SINGLE trigger:

  • Event: page_view
  • Match: screen = Wallet
  • Delay: 3 seconds (let the screen settle before presenting).

Prefer a SEQUENCE when the moment is defined by more than one action — e.g. page_view {screen: Wallet} then wallet_tap within 60 seconds.

Set eligibility

  • Audience: everyone (leave audienceMatch empty), or narrow to e.g. plan = pro.
  • Sampling: 100%.
  • Frequency cap: maxPerUserDays = 30.

Publish

Set the survey status to Active and save. The SDK picks it up on its next config fetch (immediately on app start, otherwise within the 12-hour foreground refresh window).

Verify on device

Run your app, navigate to the wallet screen, and — after the 3-second delay — the survey appears as a bottom sheet. Submit a score.

With debug logging on, filter the Xcode console by [MicroSurveys] to watch the trigger match and each eligibility gate.

See the response

Open the survey’s analytics in the dashboard: the impression and the CES score appear once the SDK flushes them (immediately when online).

What just happened

The SDK matched your page_view event locally, ran the full eligibility order, waited the delay, presented the survey with your dashboard theme, and reported the impression and response — all without any survey-specific code in your app. Change the prompt, targeting, or look, and it’s a dashboard edit, not a release.

OverviewFAQ