Create audiences in Airbridge to optimize targeted ad campaigns by sending them to ad channels, or export them as CSV files for upload and analysis in external systems.
Make sure you have the following ready before creating an audience.
Owner or In-house Marketer permission is required to use [Audience Manager]. See Airbridge User Management for details.
Each event used as a condition must have been collected at least once.
When sending audiences to ad channels, devices without a collected GAID or IDFA are excluded. See Identifiers for details.
To send audiences to ad channels, channel authentication must be completed in advance. See Send Audiences to Ad Channels for details.
Create audiences in the Airbridge dashboard at [Integrations]>[Audience Manager]. Click 'Create an audience' in the [Audience] or [Request History] tab.
Audiences can be defined by four conditions.
Defining an audience starts with selecting whether the event was performed. Click 'performed event' or 'didn't perform event' to begin. As you add conditions, the matching user count appears on the right of the dashboard in real time.
Set whether the event was performed and select the target event. Click performed event or didn't perform event, then select the event.
Note
Starting February 4, 2025, the Overview Dashboard, Actuals Report, Trend Report, Retention Report, Revenue Report, Active Users Report, and Audience Manager will only display events and metrics measurable using the collected data.
Set a condition based on an event property. Select a property, then choose a condition and value from the table below.
Set a condition based on how the event is aggregated. Select an aggregation criterion from the table below.
Then, select an aggregation condition from the table below.
Set the date range when the event occurred. Select a condition from the table below, then enter or select the date range. For 'Last', click 'Include today' to include today in the range.
An audience is defined per event. To include two or more events as conditions, combine multiple conditions. Click 'or' in [Condition 1] to add an event, or click 'Add condition' to define a new [Condition 2]. When adding new conditions, use 'and also' or 'and not also' as described below.
Conditions are applied from top to bottom, as shown in the example below.
Select the identifier types to export from the defined audience.
Note
Identifier types can't be changed after the audience is created. The identifiers used vary by purpose, so decide your use case in advance.
For sending to ad channels: Only GAID and IDFA are used, regardless of the selection.
For CSV export: All selected identifiers are used.
Recommended identifiers by use case are listed below. Selecting multiple identifiers doesn't mean every device has all of them. Unavailable identifiers appear as empty cells in the exported CSV file.
Make sure you note the following.
Identifier types selected during audience creation are only used for CSV file exports. For sending audiences to ad channels, only GAID and IDFA are used, regardless of the selection. For example, even if you selected User ID and IDFV as identifier types, GAID and IDFA are used when the audience is sent to ad channels.
You can't change the identifier types of a created audience.
When you export audiences as CSV files, you can view all selected identifier types of each user. Each row shows one user's identifier types, and empty cells indicate unavailable identifiers.
For example, suppose you selected Airbridge Device ID, GAID, IDFV, User ID, and Hashed User ID as identifier types and the file was exported as shown below. The first row's user has all identifier types, while each user from the second row to the last row has only some, with empty cells for unavailable ones.
Once conditions are set, click 'Next' to choose a saving option. Enter an audience name and click 'Save' to save the audience in Airbridge. Select 'Export CSV' to request an immediate export without saving.
Audiences created in Airbridge can be exported as CSV files. Airbridge counts the matching users based on the export date. For example, exporting an audience with a date range of "last 31 days, not including today" on February 1 counts users matching the conditions throughout January.
To export an audience, first request the export. The more users that match the conditions, the longer the export takes. Once complete, a confirmation email is sent to the address linked to your Airbridge account.
You can request an export in three ways.
Saved audiences appear in the [Audience] tab. Click Request export.
Click a saved audience to view its conditions in detail. Click Request export.
While creating an audience, select Export CSV as the saving option. Click Request export.
After requesting an export, download the CSV file from the [Request History] tab. The file size appears once Airbridge processes the request. If you cancel before processing, the status shows 'Canceled'. If processing fails, contact us through [Support]>[Contact Us] in the Airbridge dashboard.
CSV files expire 180 days after export. If a file expires, request the export again.
Airbridge provides the basic features needed to manage saved audiences.
Note the following.
When you set a date range to define an audience, each day starts at 12:00 AM. If the export date falls within the range, the range extends to the export time. See the example below.
For example, if you export an audience at 6:00 PM (18:00) on January 4, 2023, the date range applies as follows.
Under Google's updated EU user consent policy, only the following users are included in audiences sent to Google Ads.
Users not based in regions where the Digital Markets Act (DMA) applies
Users in DMA regions who consented to both data collection for Personalized Ads and data transmission to Google for ad-related purposes
As a result, the audience size shown in Google Ads may be smaller than the estimate provided by Airbridge.
Condition | Description |
|---|---|
Event | The type of event a user did or didn't perform |
Event property | A specific attribute of the event |
Aggregation criteria | How the event is measured: by count, sum, or unique days |
Date range | The time period during which the event occurred |
Condition | Description |
|---|---|
performed event | Includes users who performed the selected event |
didn’t perform event | Includes users who didn't perform the selected event |
Condition |
Application |
Description |
|---|---|---|
is | A is B | Includes users who performed events where property A equals B |
is not | A is not B | Includes users who performed events where property A doesn't equal B |
contains | A contains B | Includes users who performed events where property A contains B |
does not contain | A does not contain B | Includes users who performed events where property A doesn't contain B |
exists | A exists | Includes users who performed events that have property A |
does not exist | A does not exist | Includes users who performed events without property A |
Aggregation criteria | Description |
|---|---|
times | The total number of times an event occurred. Use this to filter users by the number of event occurrences. |
sum | The sum of values (Event Value) collected with events. For example, use this to target high-value customers whose total purchases exceed 100,000 KRW over the last 90 days. |
unique days | The number of unique days an event occurred. Multiple occurrences on the same day count as one. For example, use this to identify active users who opened the app on 20 or more days in the last 30 days. |
Condition | Application | Description |
|---|---|---|
equals | equals N | Includes users who performed the selected event exactly N times |
more than or equals | more than or equals N | Includes users who performed the selected event N or more times |
more than | more than N | Includes users who performed the selected event more than N times |
less than or equals | less than or equals N | Includes users who performed the selected event N or fewer times |
less than | less than N | Includes users who performed the selected event fewer than N times |
Condition | Application | Description |
|---|---|---|
Between | between yyyy-mm-dd ~ yyyy-mm-dd | Includes users who performed the event within the set date range |
Since | since yyyy-mm-dd | Includes users who performed the event from the set date through today |
Last | last N days/weeks/months | Includes users who performed the event in the last N days/weeks/months, ending yesterday or today |
Condition | Description |
|---|---|
or | Includes users who match either condition A or condition B |
and also | Includes users who match both conditions A and B |
and not also | Includes users who match condition A but not condition B |
Section | Details |
|---|---|
Condition 1 | Performed the Purchase (App) event at least once with property Country is KR in the last 7 days |
Condition 2: and not also | Performed the Refund (App) event at least once in the last 7 days |
Resulting audience | Users in Korea who purchased but didn't refund in the last 7 days |
Use case | Identifiers used | Recommended selection |
|---|---|---|
Sending to ad channels | GAID, IDFA | GAID, IDFA |
CSV export to external systems | All selected identifiers | Identifiers matching your use case |
Both ad channels and CSV export | GAID, IDFA for ad channels / All selected for CSV | GAID, IDFA plus additional identifiers matching your use case (Airbridge Device ID, User ID, Hashed User Email, etc.) |
Identifier type | Description |
|---|---|
Airbridge Device ID | User identifier determined by Airbridge based on the device. Ad channels can use it for optimizing targeted campaigns. See the for details. |
GAID | Unique identifier provided by Android for each device. |
App Set ID | Identifier provided by Android for each developer account. The same identifier is provided for different apps developed by the same developer. |
IDFA | Unique identifier provided by iOS for each device. Starting from iOS 14.5, users must consent to data collection in the ATT (App Tracking Transparency) prompt for this identifier to be provided. |
IDFV | Identifier provided by iOS for each developer account. The same identifier is provided for different apps developed by the same developer. |
User ID | User identifier obtained from sign-up or sign-in data in your service. Use it for CRM campaigns. |
Hashed User ID | SHA-256 encrypted User ID. Use it when you need additional identifiers beyond the regular ones. |
Hashed User Email | SHA-256 encrypted email. Use it when you need additional identifiers beyond the regular ones. |
Hashed User Phone | SHA-256 encrypted phone number. Use it when you need additional identifiers beyond the regular ones. |
Airbridge Device ID | GAID | IDFV | User ID | Hashed User ID |
|---|---|---|---|---|
ADID 1 | GAID 1 | IDFV 1 | UID 1 | HUID 1 |
ADID 2 | GAID 2 | - | UID 2 | - |
ADID 3 | - | IDFV 2 | UID 3 | - |
ADID 4 | GAID 3 | - | UID 4 | - |
ADID 5 | - | IDFV 3 | - | HUID 2 |
Feature | Description |
|---|---|
Re-estimate | Re-estimates the number of users in the audience |
Duplicate | Duplicates existing conditions to define a new audience |
Delete | Deletes the audience |
Change conditions | Modifies the existing conditions. Click a saved audience and edit in the [Definition] tab |
Change audience name | Modifies the audience name. Click a saved audience and edit in the [Audience Info] tab. |
Condition | Input | Applied range | Description |
|---|---|---|---|
Last | 3 days (excluding today) | 2023-01-01 00:00:00 ~ 2023-01-04 00:00:00 | Includes users matching the conditions from 3 days before Jan 4 through yesterday |
Last | 3 days (including today) | 2023-01-02 00:00:00 ~ 2023-01-04 18:00:00 | Includes users matching the conditions from 2 days before Jan 4 through today |
Between | 2023-01-01 ~ 2023-01-02 | 2023-01-01 00:00:00 ~ 2023-01-03 00:00:00 | Includes users matching the conditions from Jan 1 to Jan 2 |
Since | 2023-01-03 | 2023-01-03 00:00:00 ~ 2023-01-04 18:00:00 | Includes users matching the conditions from Jan 3 through 6:00 PM on Jan 4 |
このページは役に立ちましたか？