Dezerv is a SEBI-licensed wealth platform. Before working with Digia, every in-app experiment took the same route as a core feature build: a dev ticket, an engineering review, a build, and an app store release before one real user saw anything.

When testing a two-line nudge costs the same as shipping a feature, most small ideas never get tested. Sripad Panyam at Dezerv described the change plainly in Digia's published case study (2026): the team is no longer blocked by engineering for small experiments, so it tries things more often.

Server-driven UI means an app's screens and placement logic are served from a backend instead of being compiled into the binary, so a change ships from a dashboard rather than through app store review.

For a regulated app that split matters twice over. Compliance screens and disclosures stay governed the way SEBI expects. The experimentation layer runs on its own clock.

The winning experiment was one dismissible bottom sheet on Systematic Investment Plan screens, which drove more than $250,000 in new digital collections according to Digia's 2026 case study.

A SIP screen is where someone is actively setting up or reviewing a recurring investment. The nudge arrived while the user was already inside that decision, so it never had to fight for attention against an unrelated task. In fintech, placement precision does the work that aggressive copy does elsewhere, partly because SEBI's proposed Common Advertisement Code, under consultation through 2026, requires financial messaging to be true, fair, accurate, and unambiguous. Urgency tactics are off the table by design.

The format carried weight too. A bottom sheet swipes away. A full-screen interstitial demands an action before the user can continue, and on a screen where someone is committing real money, that reads as pressure.

Users reviewing their SIP are already high-intent. Some share of them would have added money with no nudge at all.

The only way to know what a surface actually caused is a randomised holdout: withhold the nudge from a slice of the qualifying audience, then compare behaviour across the same window. Digia's write-up is honest that it has not independently verified the measurement method behind the figure, which is the right posture and also the standard you should apply to your own dashboard numbers before you present them upward.

The article goes further than this summary does. It walks the regulatory backdrop shaping how the nudge was likely written, the reason a trust-first category makes a $250K result harder to produce than the same figure elsewhere, and the two questions Digia has not published answers to: the nudge's actual conversion rate, and the measurement window behind the $250,000.

Ask a vendor those two questions before you believe any case study, including this one.

You can now build in-app surveys inside Digia Engage and ship them without an app release, the same way you ship a nudge or a widget.

The branching is the part worth testing first. Answers can route respondents down different follow-up paths, so a detractor and a promoter stop getting the identical second question. Blocks cover the question and result types, and global settings control display, progress, and button behaviour.

Surveys are built independently of delivery, then attached to a CleverTap, MoEngage, or WebEngage campaign.

Read the live Survey guide → Survey