In-App View Campaigns — AlgorithmX Docs

In-App View Campaigns display personalized messages and promotional experiences while customers are actively using your website or application. Use them to guide a customer toward a goal, promote a relevant offer, or provide contextual information without moving the customer away from the current experience.

Manage In-App View campaigns

The campaign list centralizes the campaigns created by your team. From it, you can create a new campaign, search for existing work, filter by status, and review high-level values such as audience size, sent count, conversion rate, variations, and available actions.

Each row makes it possible to compare campaign purpose and current results before opening a campaign. The list shows the campaign name and description alongside its variation count, eligible audience, users sent to, conversion rate, status, creation date, and actions menu.

In-App View Campaigns list with campaign metrics and statuses — Use the list to search, filter, and compare in-app campaigns before opening the campaign you want to review or manage.

Create an In-App View campaign

The Create In-App View Campaign flow has four steps: Audience, Campaign Information, In-App View Builder, and Timing.

1. Define the audience

The first screen provides an Audience (comma-separated) field. Enter the audience members separated by commas; the helper text also supports using Enter or a comma to add each member. Review the audience before continuing because it determines who is eligible to see the experience.

Use a consistent identifier for each audience member, such as the identifier used by your application. Adding one member at a time is useful for a small, specific group; add several values separated by commas when preparing a larger controlled audience.

Audience step of the Create In-App View Campaign flow — Enter eligible audience members in the comma-separated field, then select Next to continue to the campaign configuration.

2. Add campaign information

Use Campaign Information to identify the campaign and establish its purpose. The campaign details later show the name, description, goal type, audience size, status, dates, and total number of variations, so these settings should be meaningful to the team that will monitor the campaign.

The In-App View Settings control the delivery rules for the experience. Max Show Time limits how many times an eligible user can see it. Interval (Minutes) sets the minimum time between displays. Expires At defines when the experience stops being eligible, while Show Again After (Days) controls when a user may see it again. Priority helps resolve competing experiences, and Goal Type identifies the action used to measure success, such as a click.

Campaign Information and In-App View Settings step — Set a clear campaign name and description, then configure frequency, expiration, priority, and the success goal for the in-app experience.

3. Build the in-app experience

Use the In-App View Builder to select and configure the experience that users will see. Create variations when you want to compare different templates or content. Assign traffic allocation deliberately so each variation receives the intended share of eligible users.

Give each variation a recognizable internal name, choose an In-App View Template, and use the Traffic Allocation control to set its portion of the eligible audience. Add another variation only when you need a meaningful comparison. The allocation across all active variations should total 100%; any remaining share is held by the control group that does not see an in-app view.

In-App View Builder with variation name traffic allocation and template selector — Create a variation, assign its traffic allocation, and select the in-app template that will be shown to that group of users.

4. Set timing

Use Timing to control when the campaign can run. Confirm the audience, goal, and experience before completing the creation flow.

Review campaign details

The campaign details page combines configuration and performance in one view. The summary cards at the top can show:

Sent To: the number of users targeted by the campaign.
Unique Users: distinct users who were reached.
Impressions: how many times the experience was displayed.
Clicks: recorded click interactions.
Dismissed: views closed or dismissed by users.
Conversion: the campaign's conversion rate.

The campaign overview below the cards includes the campaign description, goal type, audience, publish or update dates, total variations, campaign status, and any in-app view data required by the configuration. The Revenue Overview card summarizes total revenue generated and the average revenue per variation when revenue data is available.

The example below illustrates how the dashboard connects reach, engagement, conversion, and revenue with the campaign settings. Use the top cards for a quick outcome summary, the overview card to verify the live configuration, and the table to compare each template variation with the same metrics.

In-App View campaign details with summary metrics revenue and variation performance — Campaign Details combines headline results, the in-app delivery rules, revenue overview, and per-variation performance in one screen.

Compare variation performance

The Variations Performance table is the place to compare versions of the same in-app experience. Each row can include:

Variation name and template.
Traffic allocation.
Users sent to and impressions.
Clicks and dismissed views.
Conversion rate and interactions.
Revenue generated.
Creation date and current status.

Use this table to identify whether a particular design, placement, or message is driving stronger engagement or revenue. A variation with a high allocation but weak conversion may need a different template or a more targeted audience.

Use the results

Review the campaign after it has been shown to enough users to make a useful comparison. Start with reach and impressions, then compare clicks, dismissals, conversion, and revenue by variation. Use the strongest result to refine the next in-app experience.