Target Audience

Overview

The Target Audience feature in AppNavi allows content to be selectively shown to users based on defined conditions. These conditions are grouped into target audiences, which are then applied to content such as posts, announcements, routes, pins, collections, or insights.
Target audiences can be created using rules for labels, countries, query parameters, and Identity Provider claims. This guide also explains how to set labels through custom code.

Purpose of Target Audience

The main goal is to control visibility of content for a specific set of users. Only users who match the conditions defined in a target group will be able to see the associated content.

Functions of Target Audience

The Target Audience menu in the portal displays all target groups for the current subscription. From this page, you can perform the following actions:
• Create a new Target Audience
• Simulate Target Audience
• Edit a Target Audience
• Delete a Target Audience
• Copy a Target Audience

Setup Target Audience for client side

To set up a target audience for client-side use:
• Create Target Audience
• Publish it with the required content through the portal.
• Call the API from the custom code of the required application.
• Set the time zone if required.

Navigating to Target Audience

To view and manage all target audiences:

  1. Navigate to the Target Audience section from the left-side menu.
  2. The Target Audience page will open, displaying a list of all created target groups.
  3. Each entry includes the Title, Description, and Usage Count to indicate how frequently the target audience is being utilized.

Target Audience page showing the list of configured target groups and their usage counts

Create Target Audience

  1. Click the three-dot menu.
  2. Click the + icon to create a target audience.
  3. Enter the Title and Description.
  4. Select a Logical Operator (AND / OR).
  5. Add Rules using Labels, Countries, Query Parameters and Identity Connect.
  6. Save the Target Audience.

Target Audience creation dialog for entering details, selecting an operator, and adding rules.

Deleting a Target Audience

When attempting to delete a Target Audience, a confirmation dialog is displayed showing a summary of where the Target Audience is currently in use. This helps prevent accidental removal of active configurations. The dialog displays usage counts across various modules:

Example:

This Target Audience has been used in:
Application (0), Content (0), Insights Configuration (), Insights Surveys (0), Area Configuration (0), BC Surveys (0), Route (0), Pins (0).

Are you sure you want to delete the Target Audience "TA"?

Deletion confirmation dialog showing where the selected target audience is currently used.

Rule Types in Target Audience

Target Audiences support multiple rule types (maximum of 5 rules per group):

Supported Rule Types

  • Labels
  • Countries
  • Query Parameters
  • Identity Provider (IDP)

Each rule supports up to 6 operators:

  • Equal
  • Not Equal
  • Contains
  • Does Not Contain
  • Starts With
  • Ends With

Logical Operators

  • AND: All rules must be true.
  • OR: At least one rule must be true.

Lables

Target audiences can include labels as rule conditions. Labels must match corresponding values in the custom code configuration.

Labels are custom tags used to group users or applications logically. They are defined within your AppNavi setup and can be used to control content visibility.

Use Case Example:
Show a specific route only to users who have the label “FinanceTeam.”

Steps:

  1. Navigate to Target Audience.
  2. Create a new audience group.
  3. Provide a Title and Description.
  4. Select a logical operator.
  5. In the rule section, choose Label.
  6. Select one of the six available operators.
  7. Enter one or more label values.

Label rule configuration with label values assigned to the target audience.

Set Labels with Custom Code

AppNavi allows you to filter content for specific groups (Target Audiences). For example, certain content can be displayed only for certain groups or a specific user. To enable audience filtering for an object, one or more labels must be specified when publishing. When an object with labels is published, it is not initially displayed in the avatar. The object only becomes visible when one of the assigned labels has been set via the setTargetAudienceConditions API. The functionality is shown in the following code example.

var configuration = {labels:['Group1', 'Group2']}
window.appnaviApi.application.setTargetAudienceConditions(configuration);
console.log('Labels: '+ configuration.labels );

In this case, all objects with the label Group1 or Group2 would be displayed in the avatar view. It is also possible to use the setTargetAudienceConditions API asynchronously. This can be the case, for example, if the objects like routes are to be displayed with the results of an AJAX call or another asynchronous event. In the example shown below, the two objects with the specified labels Group1 and Group2 would only become visible in the avatar after 5 seconds.

window.appnaviApi.application.resetCustomLabels();
window.setTimeout(function () {
	window.appnaviApi.application.setTargetAudienceConditions({labels:['Group1', 'Group2']});
}, 5000);

Since the custom labels are stored in local storage, it is necessary to reset the already set custom labels. This can be achieved by calling resetCustomLabels(). This method ensures that the custom labels are reset and a re-rendering of the corresponding view in the avatar takes place.

Country

The Country rule allows content to be shown only to users from specific regions. It helps you localize experiences or announcements.

Use Case Example:
Display a regional campaign only to users from Germany or France.

Steps:

  1. Navigate to Target Audience.
  2. Create a new audience group.
  3. Provide a Title and Description.
  4. Select a logical operator.
  5. In the rule section, choose Country.
  6. Select countries from the dropdown list.

Ensure the selected time zone in the client side aligns with the country used in the rule.

Country rule configuration with countries selected from the available list.

Query Parameters

This rule uses URL parameters to determine which users can access content. It’s useful for deep linking or campaign-specific pages.

Use Case Example:
Show a post only when the URL contains ?region=EU.

Steps:

  1. Create a new Target Audience.
  2. In the rule section, select Query Parameter from the dropdown.
  3. In the Query Parameter field, provide a key (e.g., random).
  4. In the Value field, provide a value (e.g., value).
  5. Save the target audience.

Query Parameter rule configuration with a key and value used for URL-based targeting.

Usage in URL:The content will only appear when the following pattern is matched:

https://www.example.com/?random=value

This method enables deep linking and conditional content visibility based on dynamic URLs.

Example URL containing the query parameter required by the configured audience rule.

Identity Provider (IDP)

This is the most dynamic rule type built to integrate with Identity Providers (IdP) such as Azure AD, Okta, or other SSO systems via Identity Connect. OIDC rules use Claim Fields, which are user attributes fetched directly from the IdP enabling automatic targeting without manual tagging.

Purpose:
To personalize content based on user identity information such as department, role, or email. Once the IdP is connected, its claims can be used in Target Audience rules for smart, identity-driven control.

How It Works:

  1. Ensure Identity Connect (IdP) is properly configured in the portal.
  2. Once connected, available claim fields (like department, email, username, etc.) will appear.
  3. These claim fields can then be used to build Target Audience rules.
  4. Common Claim Fields:
    1. department
    2. name
    3. email
    4. family_name
    5. username

Use Case Examples:

  • Show onboarding content only to users from the HR department.
  • Hide an internal post if email domain doesn’t match your company’s.
  • Display a route only for username = demouser.

Steps:

  1. Create a new Target Audience.
  2. Enter a Title and Description.
  3. In the rule section
    • Select Type → OIDC (visible only when identity connect is connected).
    • Select Claim Type, e.g., department, username, email.
    • Choose the Operator (equals, starts with, contains).
    • Enter the Value (e.g., demoUser, HR, Finance).
  4. Click Save to create the Target Audience.
  5. To verify, click the three dots again and choose Simulate Target Audience to test the configured conditions.

Identity Provider rule configuration using an OIDC claim, operator, and value.

Setup API in Custom Code
You may find some more information regarding API setup in custom code, under the heading:
setTargetAudienceConditions : method
https://docs.appnavi.eu/docs/custom-code

Setup Time Zone

  1. Open the Time Zone settings on the client device.
  2. Select the time zone of the country that the user has selected in the target audience.
  3. Open the Avatar.
  4. Check the route list and confirm that the expected route is present.

Client device settings used to select the time zone required for country-based targeting.

Simulate Target Audience

You can simulate a target audience to verify how assigned content will behave. Provide the relevant label, country, query parameter, or Identity Connect value, then run the simulation. A green result means the conditions evaluate to true and the content will be shown in the client-side avatar. A red result means the conditions evaluate to false and the content will not be shown.

Target Audience page showing the menu option used to open the simulation tool.

How to use simulate Target Audience

To simulate a target audience:

  1. Select one or multiple Labels.
  2. Select one or multiple Countries
  3. Select one or multiple Query parameters
  4. Select one or multiple identity connect values
  5. Click the "+" Icon and select one or multiple Target Audience, the maximum limit is 10.
  6. Complete the Title field
  7. Select the Target Audience
  8. Click "Add"
  9. Click "simulate"

Simulate Target Audience dialog used to test whether configured conditions evaluate as expected.

Summary

The Target Audience feature in AppNavi enables precise control over content visibility by defining rules based on labels, countries, and query parameters. These rules group users into audiences that can be applied to announcements, routes, pins, and insights.
Target audiences are easily created, managed, and simulated within the portal. The addition of query parameter support allows content to be dynamically shown based on specific URLs. Business teams benefit by delivering tailored experiences, ensuring content reaches only the intended users—enhancing personalization, reducing confusion, and improving engagement across applications.


Did this page help you?