In-App Survey with WebEngage

This guide walks you through creating a simple NPS Survey, attaching it to a Digia Survey campaign, connecting that campaign to WebEngage, and testing it on a device.

Unlike a Nudge or Guide, a Survey has two parts: the reusable Survey content and the campaign that delivers it.

info

This guide keeps the Survey itself intentionally simple. For deeper survey design, read Understanding and Building Surveys, Survey Blocks Reference, Survey Branching and Logic, and Survey Global Settings.

info

Prefer a quick visual walkthrough first? Watch Creating Native NPS Survey Experiences.

Before You Start

Make sure you have:

• Access to the correct Digia Engage project created with WebEngage as the CEP integration.
• Access to the matching WebEngage project.
• Your app must already be integrated with Digia Engage and WebEngage. Share the WebEngage developer integration guide with your app team if this setup is not complete yet.
• The audience and trigger event decided in WebEngage.
• If you plan to target specific app screens, review usable pages in Component Registry.
• A test profile or test segment in WebEngage so you can verify the campaign before launch.

info

This guide is written for product managers and marketers. Developer-only setup is linked above so you know what must already be complete before campaign testing.

For this walkthrough, we will build a default Numeric 0-10 NPS Survey with Until completed delivery.

Create the Survey

Go to Surveys and choose New survey. Use an internal name such as:

NPS Feedback Survey

Create the reusable Survey before creating the campaign that will deliver it.

Add the Default NPS Block

In the Survey builder, choose Add a block, open the NPS category, and select Numeric 0-10. Keep the default scale and update the question copy.

Use the Numeric 0-10 block for a standard NPS-style question.

The builder has blocks on the left, mobile preview in the middle, and properties on the right. Keep the default welcome screen, Numeric 0-10 block, and result page for this first test.

Edit the NPS question in the preview and keep defaults unless you need a visual adjustment.

Check Logic and Survey Settings

For this default NPS Survey, keep Logic set to Linear. Every respondent should see the welcome screen, answer the NPS question, and then see the result page.

Keep the flow linear for the default NPS Survey.

Create a Survey Campaign

After the Survey is ready, go to Campaigns and choose New Campaign. Use a campaign name such as:

NPS Feedback Survey - WebEngage

On the Basics step, select Survey and continue.

Select Survey as the campaign type so you can attach survey content.

Attach the NPS Survey

On the Choose UI step, select the NPS Feedback Survey you created earlier. The Survey content stays reusable; the campaign controls delivery and the campaign key.

Attach the saved NPS Survey to this campaign.

info

Once the Survey is attached and saved, use Live Testing Campaigns to send it to a connected debug device and confirm the prompt, result page, and submit flow before moving into delivery, review, and WebEngage setup.

Set Delivery Rules in Digia

For most feedback Surveys, Until completed is a good starting point. It lets the Survey show again in a later session until the user submits it, then stops.

Use a frequency cap that avoids repeatedly asking users after they complete the Survey.

Review and Copy WebEngage Config

Check that the correct Survey is attached and the frequency cap matches your feedback plan. You can save as draft while WebEngage setup is pending, or activate when ready.

Review the campaign summary and launch checks before saving or activating.

Copy the Digia campaign key from the WebEngage setup section.

Create the WebEngage In-App Custom HTML Campaign

Create a WebEngage In-App campaign and use Custom HTML for the content step. WebEngage decides the audience, trigger event, schedule, and priority. Digia decides what renders after the campaign fires.

Name the WebEngage campaign, choose the target audience, and continue through the campaign setup.

Choose Classic Modal as the In-App layout. Then use Custom HTML for the message content so WebEngage can pass the Digia Survey campaign key to the app.

Select Classic Modal before opening the Custom HTML editor.

Link WebEngage to the Digia Survey

In the Custom HTML editor, add a digia-config block. Survey campaigns currently require only the digia_campaign_key meta tag.

<template id="digia-config">
  <meta name="digia_campaign_key" content="nps_feedback_survey_webengage">
</template>

Keep the Survey questions, answer options, branching, and result pages in Digia. WebEngage should only carry the campaign key.

Add the Survey campaign key inside the Custom HTML editor.

Test the Survey End to End

1. Use a test audience in WebEngage.
2. Activate or preview the WebEngage campaign for that audience.
3. Trigger the event from a test device.
4. Confirm the Survey appears in the app.
5. Select an NPS score and submit.
6. Confirm the result page appears.
7. Confirm the Survey does not appear again after completion, if you selected Until completed.

Use WebEngage's Test Campaign step to send the Survey to a test segment before launch.

If the Survey does not appear, check:

What to check	Why it matters
The Digia campaign is active	Draft campaigns will not render
The NPS Survey is attached	The campaign needs saved Survey content
digia_campaign_key matches exactly	The key is case-sensitive
The WebEngage campaign uses In-App Custom HTML	The Digia plugin only receives the expected payload format
The user qualifies in WebEngage	WebEngage owns audience and trigger rules
Frequency cap has not already been reached	Digia may suppress repeat renders after completion

info

WebEngage can sometimes take time to start delivering a newly activated campaign. If the campaign still does not appear after your usual campaign propagation window, reach out to Digia support.

Launch Checklist

• Survey content is complete.
• Digia Survey campaign is active.
• The correct NPS Survey is attached.
• WebEngage campaign uses In-App Custom HTML.
• digia_campaign_key matches the Digia campaign key.
• Audience and trigger rules are correct in WebEngage.
• The Survey was tested on at least one real device.