Export Module

Export (User Selection) Module is the action layer on top of user lists in the panel. It allows targeting users and performing follow‑up actions from the same screen, without switching contexts.

The module combines user list actions and data export into a single, consistent experience designed for operational workflows such as audience creation, tagging, and data handoff to external systems.

Key benefits:

  • Perform actions and exports without leaving the list view

  • Use a single, standardized export experience across the panel

  • Export multiple identifiers in one file for downstream matching and analysis

Where Is It Used?

Export Module appears on all screens that display user lists.

  • Targeting

  • Campaign Reports

  • Reports

  • Analytics

The available actions, identifiers, and export formats may vary depending on the screen context.

Typical Actions

Depending on permissions and screen context, the following actions can be available:

  • Add users to an audience

  • Tag users

  • Export selected users to a file

Actions apply to the current result set or selected users, depending on the screen behavior.

For tagging behavior and rules, see Tags.

Export Flow: Export Selected Users to File

When exporting from a user list, a standard Export dialog opens. This dialog is used consistently across the panel to download user data in a structured format.

End‑to‑End Flow

  1. Select users from the list or use the full result set

  2. Open the Export action

  3. Select identifiers

  4. Choose file format

  5. Start export and download the file

Step 1: Identifier Selection (Multi‑Select)

The export dialog supports selecting multiple user identifiers at the same time.

Common Identifier Fields

  • Email

  • External ID

  • MSISDN

  • Mobile Advertiser ID (for example, GAID or IDFA)

One or more identifiers can be selected in a single export.

Step 2: How Columns Are Created

  • Each selected identifier is exported as a separate column in the file

  • Column order follows the default UI field order

  • If a user does not have a value for a selected identifier, the corresponding cell is exported as null

This structure enables:

  • Carrying multiple matching keys in one file

  • Easier joins in CRM, CDP, or BI workflows

  • Reduced need for repeated exports

Step 3: File Format

Export output can be generated in the following formats:

  • .csv

  • .xlsx

Available formats can vary by screen.

Which Identifiers Should Be Selected?

The choice of identifiers depends on the downstream use case:

  • External ID: Primary user key in most integrations

  • Email: Required for email‑based matching

  • MSISDN: Required for SMS or WhatsApp matching

  • Mobile Advertiser ID: Useful for device‑level analysis and attribution

With multi‑select support, all relevant identifiers can be exported together in a single file.

Null Values

A null value when multi-select options are selected means the user does not have that identifier stored on their profile. This is not an export error.

Checks to Consider

If unexpected null values appear:

  • Verify that the identifier is set by the app SDK or server‑side integration

  • Check profile merge and ID mapping configuration

  • Confirm that the identifier exists on the user profile

Failed Users Export (Campaign Reports)

When a campaign fails partially or completely, failed users can be exported directly from the campaign report. This allows investigating delivery issues without rebuilding segments or rerunning the campaign.

Where to Find It

  1. Open the relevant Campaign Report (mobile push, web push, in-app, pop-up, email, sms)

  2. Navigate to the Failed section

  3. Use the Export action

What Is Included

The export file includes:

  • Only users who failed in the campaign

  • Selected user identifiers

  • A Fail Reason column that explains why each user failed

Fail reasons can include delivery, validation, configuration, or data-related issues, depending on the channel and campaign setup.

This export supports:

  • Root cause analysis for campaign failures

  • Identifying missing or invalid user identifiers

  • Detecting configuration or targeting issues

  • Reprocessing failed users in a follow-up campaign

  • Sharing failure data with analytics or operations teams

Last updated

Was this helpful?