Create an audience in Airbridge and export the Airbridge Device ID list of users as a CSV file. You can send the audience to various ad channels for campaign optimization.
Airbridge Device ID
Airbridge Device ID is a Universally Unique ID used to identify devices. As a default, GAID for Android and IDFA for iOS are used. If GAID or IDFA is unavailable due to LAT (Limited Ad Tracking) or ATT (App Tracking Transparency), IDFV or a randomly generated value is used instead.
Navigate to [Audience]>[Audience Manager] in the Airbridge dashboard. Only Owner and In-house Marketer users have access to the [Audience Manager] page.
Click + Create an audience in the [Audience] or [Request History] tab to start creating a new audience.
Audiences can be defined by event, event property, event frequency, and date range.
To define an audience, click + performed Event or + didn’t perform Event and select an event to sort out users who have or haven’t performed the event.
You can add conditions by event properties, event frequency, and date range. To select event properties, you must first click + had Property.
The following conditions are available.
Condition | Description |
|---|---|
performed or didn’t perform | Event |
where | Event property |
with | Event frequency |
when | Date range |
As you define the audience, you can see the estimated audience size on the right. The estimated audience size is calculated from a sample of 10% of all users and, therefore, can differ from the actual audience size.
For more details on the conditions you can set, refer to the below.
Click + performed Event or + didn’t perform Event and select an event.
The following conditions are available.
Condition | Description |
|---|---|
performed | The audience should include users who performed Event X. |
didn’t perform | The audience should include users who didn’t perform Event X. |
Click +had Property and select the event property and the property conditions.
The following conditions are available. X is the event property, and Y is the property condition.
Condition | Application | Description |
|---|---|---|
is | X is Y | The audience should include users who performed the event of which the event property X is Y. |
is not | X is not Y | The audience should include users who performed the event of which the event property X is not Y. |
contains | X contains Y | The audience should include users who performed the event of which the event property X contains Y. |
does not contain | X does not contain Y | The audience should include users who performed the event of which the event property X does not contain Y. |
exists | X exists | The audience should include users who performed the event with the event property X. |
does not exist | X does not exist | The audience should include users who performed the event without the event property X. |
Select a condition and enter a number to filter users by event occurrence.
The following conditions are available.
Condition | Application | Description |
|---|---|---|
equals | equals N time(s) | The audience should include users who performed the event N time(s). |
more than or equals | more than or equals N time(s) | The audience should include users who performed the event N time(s) or more than N time(s). |
more than | more than N time(s) | The audience should include users who performed the event more than N time(s). |
less than or equals | less than or equals N time(s) | The audience should include users who performed the event N time(s) or less than N time(s). |
less than | less than N time(s) | The audience should include users who performed the event less than N time(s). |
Set the date range and enter a number to filter users by event timestamp.
The following conditions are available. The date range can’t exceed 175 days, including today.
Condition | Application | Description |
|---|---|---|
during last | during last N day(s) | The audience should include users who performed the event during the last N day(s). |
between | between yyyy-mm-dd ~ yyyy-mm-dd | The audience should include users who performed the event during the set date range. |
since | since yyyy-mm-dd | The audience should include users who performed the event since the set date. |
An audience may consist of multiple user segments, each defined by a single event. In this case, you must also set a condition defining the relationship between the user segments.
The following conditions are available.
Condition | Application | Description |
|---|---|---|
or | X or Y | The audience should include users who belong to either user segment X or user segment Y. |
and also | X and also Y | The audience should include users who belong to both user segments X and Y. |
and not also | X and not also Y | The audience should include users who belong to user segment X but not user segment Y. |
Once you have finished defining the audience, click Next to set the saving option. You can select “Save audience” and enter an audience name to save the audience in Airbridge. By selecting “Export CSV,” the audience will be exported as a CSV file, which you can download from the [Request History] tab.
When you request to export a saved audience, Airbridge sorts out users based on the date of the export request.
Let’s say the date range for the audience is set to “during the last 31 days, not including today.” If the export is requested on Feb 1, the audience will include users who meet all the set conditions throughout the entire month of January.
To download an audience as a CSV file, you first need to request an export. The process may take longer if there is a larger number of users meeting the set conditions. Once the export is complete, you will receive a confirmation email at the address associated with your Airbridge account.
You can request the audience export using the following methods:
Navigate to [Audience]>[Audience Manager] and select the [Audience] tab. Find the audience you want to export from the list and click Export.
Navigate to [Audience]>[Audience Manager] and select the [Audience] tab. Find the audience you want to export from the list, click on it to open the side panel, and click Request export on the top right.
After you define a new audience, select “Export CSV” and click Request export.
Once you have received the confirmation email, navigate to the [Request History] tab. If the Status·Download column shows the CSV file size, click on it to download the file. If the column shows “Failed” or “Canceled,” it signifies that the request has been interrupted before the audience could be exported. If the export continues to fail, contact your Airbridge CSM.
The CSV files can be downloaded within 180 days after export. If the download link expires, request the audience export again.
In the [Audience] tab, you can find features essential for managing your saved audiences.
Feature | Description |
|---|---|
Re-estimate | Click the […] icon and select Re-estimate to re-estimate the size of the audience. |
Duplicate | Click the […] icon and select Duplicate to duplicate the audience. |
Delete | Click the […] icon and select Delete to delete the audience. |
Change conditions | Click the audience to open the side panel and select the [Definition] tab to change the conditions defining the audience. |
Change audience name | Click the audience to open the side panel and select the [Audience Info] tab to change the audience name. |
Airbridge uses a number of identifiers to ensure attribution accuracy. If you want to define an audience that only includes users identified by IDFA and GAID, you need to set the conditions accordingly. If not, users identified by other identifiers, such as IDFV, will also be included.
To define the audience, click + had Property. Set the event property to “Airbridge Device ID Type,” the condition to “is,” and the property condition to “IDFA” and “IDFV.”
When you set a date range to define an audience, Airbridge assumes that each day starts at 12:00 AM. If you opt for “Include Today,” the date range is applied up to the time of export.
For instance, if you exported an audience at 6:00 PM on Jan 4, 2023, the date range is applied as shown in the table below.
Condition | Input Value | Date Range | Description |
|---|---|---|---|
during last | 3 days, not including today | 2023-01-01 00:00:00 ~ 2023-01-04 00:00:00 | The audience should include users who met the conditions from 1 to 3 days before Jan 4. |
during last | 3 days, including today | 2023-01-02 00:00:00 ~ 2023-01-04 18:00:00 | The audience should include users who met the conditions from 0 to 2 days before Jan 4. |
between | 2023-01-01 ~ 2023-01-02 | 2023-01-01 00:00:00 ~ 2023-01-03 00:00:00 | The audience should include users who met the conditions from Jan 1 to Jan 2. |
since | 2023-01-03 | 2023-01-03 00:00:00 ~ 2023-01-04 18:00:00 | The audience should include users who met the conditions from Jan 3 to 6:00 PM on Jan 4. |
In compliance with the updated Google EU user consent policy, audiences to be sent to Google Ads will only include end users meeting the following conditions:
The user is not based in a region where the Digital Markets Act applies
The user is based in the region where the Digital Markets Act applies, but gave consent to use their data for Google’s ad personalization and to send their data to Google for ad-related purposes
This explains why the actual audience size shown in the Google Ads dashboard may be smaller than the estimated audience size shown in the Airbridge dashboard.
Was this page helpful?