- User Guide
- Tracking Link
- Cross-platform Measurement
PC Game Measurement
PC game advertising incorporates various campaign strategies across different platforms. Airbridge ensures cross-platform advertising measurement on mobile devices, the web, and PCs to provide you with comprehensive insight into your PC game's growth.
Note
This feature is currently in beta. If you have any questions or suggestions for improvements, reach out to your Airbridge CSM. If you don't have a designated CSM, contact the Airbridge Help Center.
Using landing pages recommended
We recommend using a landing page for PC game measurement. In particular, a landing page is essential for measuring the Google Ads campaigns for PC games.
Cross-platform measurement is required to measure the effectiveness of PC game ads, as user engagement with the ads can occur across various platforms beyond the PC or console where the game is played. Airbridge supports data collection across mobile devices, the web, and PCs.
In this scenario, users who click an ad are redirected to a landing page where the Airbridge Web SDK is installed. Airbridge collects data from this website and the PC game to measure ad performance. This method is recommended when tracking campaigns where tracking links can’t be used. The collected cookie IDs can also be used for running effective retargeting campaigns.
Airbridge collects data using the tracking links across platforms to measure the performance of PC game ads.
For PC game measurement, data from mobile devices, the web, and PC games must be collected and sent to Airbridge. The data collected from websites can be sent to Airbridge through the Airbridge SDK, and the data collected from the PC games can be sent to Airbridge through API.
Attention
A landing page is essential for measuring Google Ads campaigns for PC games. Refer to the prerequisites to prepare a landing page and install the Airbridge web SDK.
The following pre-setup must be complete to continue.
Prepare a landing page to redirect users who click your ad. From the landing page, users can either start the PC game directly or navigate to other gaming platforms such as Steam or Epic Games Store.
Installing the Airbridge Web SDK to the landing page allows you to track ad performance without tracking links and run effective retargeting campaigns using the cookie IDs collected via the SDK.
Registering a mobile app is not required to get started. Simply enter a website or the desired landing page into the Website field. It can be changed afterward.
Refer to this article to learn more about getting started with Airbridge.
Install the Airbridge Web SDK to the desired landing page. By enabling the UTM parsing of the Web SDK, Airbridge can track data via UTM parameters without the use of tracking links.
Design the event taxonomy for your PC game measurement. The game events will be sent to Airbridge and recorded following the set event taxonomy.
Attention
Upon updating the probabilistic modeling settings, more conversions will be attributed to ad channels by Airbridge, and the change will be visible in the Airbridge reports.
To set up PC game measurement, the probabilistic modeling settings must be updated. Contact your Airbridge CSM for more details.
The in-game events collected from the PC game shall be sent to Airbridge via the S2S event API.
Refer to the information below and send the PC game events via the S2S event API. For more details on the S2S event API, refer to this . Make sure to send the game events to the in-app event endpoints and not to the in-web event endpoints.
The following table shows the different endpoints for the PC Game Installs, PC Game Opens, and In-game events.
In-game events are events that are performed after the user performs the PC Game Install or PC Game Open events, such as Complete Tutorial, Achieve Level 1, etc.
Event |
Endpoint |
|---|---|
PC Game Install |
|
PC Game Open |
|
In-game events |
|
Refer to the table below for the header configuration.
Header |
Is it required? |
Description |
|---|---|---|
| Required | The API tokenis required which can be found in the Airbridge dashboard. |
| Required | Send the IPs with the |
| Optional | Configure the preferred natural language and locale. ISO-639-1 applies. |
| Optional | The media type of the resource. Default value is |
Attention
The API token required for configuring the
Authorizationheader can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.
Refer to the following table for sending the PC game events to Airbridge. The events can be defined as Standard or Ecutom Events depending on the information sent to eventData.goal. To learn more about Standard and Custom Events, refer to this article.
Name |
Required or Optional |
Description |
|---|---|---|
| Required | Send the user ID that is used to identify users in your gaming service. This user ID will be used for attribution. For more details, refer to this article. |
| Optional | Send the device and platform information. |
| Optional | Send events collected from the PC game. The Information sent via the |
Airbridge supports the following devicesub-variables.
Sending device information recommended
We recommend sending the device information. The device information is required to view the PC game events by platform, OS, and other details in the Airbridge reports.
Name | Description |
|---|---|
device.platform | Platform supported by the device |
device.deviceType | Device type |
device.osName | OS name used on the device |
device.osVersion | OS version used on the device |
device.deviceModel | Device model name |
The PC game tracking results can be monitored in the Airbridge report by using the device information as GroupBys.
Attention
If the device information is not sent, you might see some unexpected results in your Airbridge reports.
Send the PC Game Install or the PC Game Open events before sending the in-game events to Airbridge. The attribution result of the in-game events sent afterward will vary depending on the event first sent.
Enabling Airbridge's reactivation tracking feature can measure the users who return to your game after a certain period of time. Refer to this articleto find out more.
User type |
Send first |
Description |
|---|---|---|
New users or users with no tracking records in Airbridge | PC Game Install | This is a , triggering attribution. Attribution is performed following the configured attribution rule. |
Existing users or users with tracking records in Airbridge | PC Game Open | This is not a Target Event, and attribution is not triggered. |
In the following scenario, the attribution window is set to 3 days.
Date |
User |
Events sent to Airbridge |
Description |
|---|---|---|---|
Jan 1 | User A | 1. PC Game Install event | The PC Game Install event triggers attribution. |
Jan 2 | User A | 1. PC Game Install event | The Purchase Item event occurred within the attribution window and is attributed to the same touchpoint that drove the PC Game Install event. |
Jan 3 | User B | 1. PC Game Install event | The PC Game Install event triggers attribution. |
Jan 4 | User C | 1. PC Game Open event | There is no prior Target Event. Therefore, all events are classified as Unattributed. |
Jan 5 | User A | 1. PC Game Open event | The events occurred beyond the attribution window of the PC Game Install event of User A, which triggered the attribution. Therefore, all events are classified as Unattributed. |
Refer to the examples below for sending PC game events via the S2S event API.
Refer to the example below.
curl --location 'https://api.airbridge.io/events/v1/apps/{{ APP_NAME }}/mobile-app/9161' \
--header 'Authorization: AIRBRIDGE-API-TOKEN {{ API_TOKEN }}' \
--header 'Content-Type: application/json' \
--header 'X-Forwarded-For: {{ CLIENT_IP }}' \
--data '{
"user": {
"externalUserID": "abrid123"
},
"device": {
"platform": "steam",
"deviceType": "desktop",
"osName": "Windows",
"osVersion": "11",
"deviceModel": "pc",
"screen": {
"width": 1920,
"height": 1080
}
}
}'Refer to the example below.
curl --location 'https://api.airbridge.io/events/v1/apps/{{ APP_NAME }}/mobile-app/9160' \
--header 'Authorization: AIRBRIDGE-API-TOKEN {{ API_TOKEN }}' \
--header 'Content-Type: application/json' \
--header 'X-Forwarded-For: {{ CLIENT_IP }}' \
--data '{
"user": {
"externalUserID": "abrid123"
},
"device": {
"platform": "playstaion",
"deviceType": "console",
"osName": "playstation_5",
"screen": {
"width": 1920,
"height": 1080
}
}
}'Refer to the example below to send various in-game events to Airbridge.
curl --location 'https://api.airbridge.io/events/v1/apps/{{ APP_NAME }}/mobile-app/9360' \
--header 'Authorization: AIRBRIDGE-API-TOKEN {{ API_TOKEN }}' \
--header 'Content-Type: application/json' \
--header 'X-Forwarded-For: {{ CLIENT_IP }}' \
--data '{
"user": {
"externalUserID": "abrid123"
},
"device": {
"platform": "iOS",
"deviceType": "desktop",
"osName": "iOS",
"osVersion": "17.1",
"deviceModel": "Mac",
"screen": {
"width": 1920,
"height": 1080
}
},
"eventData": {
"goal": {
"category": "buy_item",
"action": "weapon",
"label": "longsword",
"value": 1.234,
"customAttributes": {
"foo": "foo",
"bar": 1.234
}
}
}
}'It is advised to send revenue events as Airbridge Standard Events so you can use the revenue data for postbacks and view them in Airbridge reports such as the Revenue Report.
When configuring theeventData.goal.categoryas airbridge.ecommerce.order.completed, the revenue data is sent as the Order Complete event, and the eventData.goal.value will be reported as the revenue amount.
curl --location 'https://api.airbridge.io/events/v1/apps/{{ APP_NAME }}/mobile-app/9360' \
--header 'Authorization: AIRBRIDGE-API-TOKEN {{ API_TOKEN }}' \
--header 'Content-Type: application/json' \
--header 'X-Forwarded-For: {{ CLIENT_IP }}' \
--data '{
"user": {
"externalUserID": "abrid123"
},
"device": {
"platform": "Android",
"deviceType": "desktop",
"osName": "Android",
"osVersion": "7",
"deviceModel": "pc",
"screen": {
"width": 1920,
"height": 1080
}
},
"eventData": {
"goal": {
"category": "airbridge.ecommerce.order.completed",
"value": 1.234
}
}
}'Check the items below to make sure the PC game measurement is successfully set up.
Items |
What to test |
Troubleshooting |
|---|---|---|
Attribution | Make sure that the PC game installs and in-game events are attributed to the intended ad channel after clicking the tracking link. Check the attribution result of the PC game installs and in-game events you confirmed on the [Raw Data]>[App Real-time Logs] page in the Airbridge dashboard. | Make sure the IPs that have generated in-game events are sent with the |
API configuration | Make sure the events are collected according to the API configuration. The API configuration can be tested by sending events without the | Check the API configuration again. |
For PC game measurement, data from mobile devices, the web, and PC games must be collected and sent to Airbridge. The data collected from tracking links can be sent to Airbridge through the Airbridge SDK, and the data collected from the PC games can be sent to Airbridge through API.
Attention
If you want to measure the Google Ads campaigns for your PC game, you must use a landing page for the setup. Refer to this section of the article.
The following pre-setup must be complete to continue.
Create a tracking link to use for your ad. When creating an integration channel tracking link in the Airbridge dashboard, click [Website] in the Redirection section and configure the destination for all platforms as the desired landing page. If you don't have a landing page for redirection purposes, you can enter the URL of the game distribution platform, such as Steam, Epic Games Store, etc.
For detailed instructions on how to create tracking links, refer to this article.
Registering a mobile app is not required to get started. Simply enter a website or the desired landing page into the Website field. It can be changed afterward.
Refer to this article to learn more about getting started with Airbridge.
Design the event taxonomy for your PC game measurement. The game events will be sent to Airbridge and recorded following the set event taxonomy.
Attention
Upon updating the probabilistic modeling settings, more conversions will be attributed to ad channels by Airbridge, and the change will be visible in the Airbridge reports.
To set up PC game measurement, the probabilistic modeling settings must be updated. Contact your Airbridge CSM for more details.
The in-game events collected from the PC game shall be sent to Airbridge via the S2S event API. Refer to this section of the article.
Check the items below to make sure the PC game measurement is successfully set up.
Items |
What to test |
Troubleshooting |
|---|---|---|
Attribution | Make sure that the PC game installs and in-game events are attributed to the intended ad channel after clicking the tracking link. Check the attribution result of the PC game installs and in-game events you confirmed on the [Raw Data]>[App Real-time Logs] page in the Airbridge dashboard. | Make sure the IPs that have generated in-game events are sent with the |
API configuration | Make sure the events are collected according to the API configuration. The API configuration can be tested by sending events without the | Check the API configuration again. |
The PC game measurement results can be viewed in the Airbridge report by selecting the game events as the report metric. The game events will be recorded as app events, with “(App)” appended to the metric name.
The PC game events are defined by the information sent via the eventData.goal parameter. You can create a customized report view using the information sent via the eventData.goal parameters to fit your marketing needs.
Suppose the "Level Achieved" event parameters have been configured as below.
eventData.goal.action: The location information of the user who achieved a certain level within the gameeventData.goal.label: The method of achieving the level
In the Airbridge report, select level_achieved (App) as the metric and Channel, Event Action, and Event Label as GroupBy to create a report view like the following image.
Suppose the parameters of the “Purchase Item” event have been configured as below.
eventData.goal.category: purchase_itemeventData.goal.action: The type information of the purchased itemeventData.goal.label: The information on how the item was attached to the game character
In the Airbridge report, select purchase_item (App) as the metric and Channel, Event Action, and Event Label as GroupBy to create a report view like the following image.
Explore the wide range of report types and features offered by Airbridge.
Airbridge uses probabilistic approach for PC game measurement. The connection between touchpoints and conversions is inferred within a 6-hour timeframe, but the timeframe can be modified for PC game measurement.
Make sure to avoid the following mistakes.
IP not sent: Send IP with the
X-Forwarded-Forheader when an in-game event occurs.Wrong endpoint: Send events to the correct endpoints.
S2S API configuration error: Send data via the S2S event API for in-app events.
Was this page helpful?