UA Campaign

Overview

The UA Campaign section is designed for managing advertising campaigns imported into the system from MMP grabbers such as Adjust and AppsFlyer.

UA Campaign acts as a configuration and normalization layer between raw MMP data and the system’s analytical reports.

The UA Campaign list is available in: 

Magify > Configuration > UA Configurations > UA Campaign

In this section, you can:

  • review imported campaigns;
  • configure and validate key campaign parameters;
  • ensure correct campaign participation in analytics and reports.

Proper configuration of UA Campaign directly affects:

  • accuracy of spend and revenue attribution;
  • correct aggregation by traffic sources and ad networks;
  • data consistency across all analytical reports.

Role of UA Campaign in Analytics

Each campaign in the UA Campaign section represents a link between MMP data and all analytical layers of the system, including:

  • performance reports;
  • ad network and traffic source analytics;
  • aggregated analytical reports.

If key campaign parameters (especially Type) are missing or incorrect, the campaign may:

  • be partially excluded from analytics;
  • be excluded from certain analytical reports.

Data Synchronization

Campaigns are imported from MMPs automatically.

  • Campaign names, Media Source, and technical identifiers are received directly from the MMP.
  • Data synchronization runs automatically.
  • Fields received from the MMP must not be edited manually unless explicitly allowed.

In the campaign details view, it is visually indicated which fields are editable and which are locked.

Main Fields

Application

The application to which the campaign belongs.

  • Automatically filled during MMP import.
  • Not editable manually.
  • Always matches the data received from Adjust or AppsFlyer.

Used to ensure correct aggregation of analytics by application.

Name

The campaign name imported from the MMP.

  • Used to identify campaigns in analytics and reports.
  • Changes made to the campaign name in the MMP are not synchronized automatically.

Media Source

The traffic source as defined by the MMP (Adjust or AppsFlyer).

  • Imported automatically if provided by the MMP.
  • Not editable if the value was received from the MMP.
  • Used for technical mapping and report consistency.

AppsFlyer specifics

For campaigns imported from AppsFlyer:

  • Media Source may not be set automatically;
  • in such cases, Media Source must be set manually.

If Media Source:

  • is set correctly — analytics and reports work as expected;
  • is set incorrectly — the campaign receives the status Just Created Campaign and may be excluded from analytics.

If Media Source was received from the MMP:

  • the field becomes disabled;
  • manual changes are not allowed.

Ad Network

The advertising network through which traffic is purchased (e.g. Unity Ads, AppLovin, IronSource, Mintegral).

  • Represents the actual buying partner.
  • Used for ad network–level performance analysis.

Ad Network:

  • is usually imported from the MMP (primarily Adjust);
  • can be set manually only in exceptional cases if no value was received from the MMP.

Ad Network vs Media Source

UA Campaign uses two related but different parameters: Ad Network and Media Source.

Ad Network answers the question:“Which advertising network performs better overall?”

It represents the platform or network that sells and manages ad inventory.

Media Source answers the question:“Which source or inventory within this network performs better?”

It reflects a specific channel or identifier defined by the MMP.

Using both parameters allows performance analysis at different levels:

  • network-level (Ad Network);
  • source-level within a network (Media Source).

Original Network Name

The original campaign or source name exactly as received from the MMP, without normalization.

Purpose of the field:

  • used as a technical service field for internal mapping;
  • helps match different naming variations to a single Media Source.

This field:

  • is not used for filtering or reporting;
  • is not intended for analytical analysis.

Type (Campaign Type)

Defines the traffic acquisition model and determines campaign participation in analytics and reports.

Campaign Type must always be set manually.

If Type is not defined:

  • the campaign receives the status Just Created Campaign;
  • the campaign may be excluded from analytics.

Status

The current campaign state:

  • Running — active campaign.
  • Archived — campaign manually marked as inactive by the user.
  • remain available for historical reference;
  • do not participate in active analytics.

Campaign Types

Ad ROAS Campaign

Campaigns optimized for return on ad spend.

CPI Campaign

Paid per install.

CPE Campaign

Paid per in-app event.

CPP Campaign

Paid per purchase.

CPC Campaign

Paid per click.

CPM Campaign

Paid per 1,000 impressions.

CPA Campaign

Paid per action.

Retargeting Campaign

Re-engagement of existing users.

Cross-Promo Campaign

Promotion of your own apps.

Branding Campaign

Awareness-focused campaigns.

Other

Temporary classification.

Campaigns Without Type: System Notifications

After campaign import, the system checks whether all campaigns have a defined Type.

If at least one campaign has no Type, a system notification is shown.

Where notifications appear

  1. In the notification center on the main screen.
  2. In the UA Campaign list, where campaigns without a Type are marked with a warning indicator.
magify-ua-campaign-type

The notification remains visible as long as at least one campaign has no Type assigned.

Once all campaigns have a Type, the notification disappears automatically.

Campaign List Filtering and Table Settings

Filters

The UA Campaign list can be filtered by:

  • Application
  • Type
  • Media Source

Filters help quickly locate incorrectly configured or unclassified campaigns.

Edit Table

Using Edit table, you can customize which columns are displayed in the campaign list.

Available columns:

  • Name
  • Application
  • Type
  • Status
  • Ad Network

Selected columns are saved per user and help adapt the table to different workflows.

Campaigns Imported from MMPs

The system may receive the following campaign types from MMPs:

  • user acquisition campaigns;
  • cross-promo campaigns;
  • search campaigns (may appear as organic depending on MMP logic).

Campaign Type in UA Campaign reflects the acquisition model, not the marketing naming used in the MMP.

Best Practices

  • Assign Campaign Type immediately after import.
  • For AppsFlyer campaigns, always verify and set Media Source and Type manually.
  • Do not edit MMP-imported fields if they are locked.
  • Use filters and table settings to monitor campaign configuration.
  • Archive campaigns only when they are truly finished.

Summary

UA Campaign is a core configuration section for user acquisition analytics.

Correctly configured campaigns ensure:

  • clean and consistent analytics;
  • correct source and network attribution;
  • reliable data across all analytical reports.

Misconfigured campaigns directly impact data quality and should be corrected as early as possible.