PC Game Measurement
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.PC game measurement scenario using a landing page (Recommended)
PC game measurement scenario using a landing page (Recommended)

PC game measurement scenario without a landing page
PC game measurement scenario without a landing page

PC Game Measurement Setup Using a Landing Page (Recommended)
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.Pre-setup
The following pre-setup must be complete to continue.Prepare a landing page
Prepare a landing page

Get started with Airbridge
Get started with Airbridge

Install the Airbridge Web SDK
Install the Airbridge Web SDK
Design the event taxonomy
Design the event taxonomy
Request updating the probabilistic modeling settings
Request updating the probabilistic modeling settings
Sending PC game events to Airbridge
The in-game events collected from the PC game shall be sent to Airbridge via the S2S event API.S2S event API configuration
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 article. Make sure to send the game events to the in-app event endpoints and not to the in-web event endpoints.Endpoints for key events
Endpoints for key events
| Event | Endpoint |
|---|---|
| PC Game Install | https://api.airbridge.io/events/v1/apps/{{APP_NAME}}/mobile-app/9161 |
| PC Game Open | https://api.airbridge.io/events/v1/apps/{{APP_NAME}}/mobile-app/9160 |
| In-game events | https://api.airbridge.io/events/v1/apps/{{APP_NAME}}/mobile-app/9360 |
Header
Header
| Header | Is it required? | Description |
|---|---|---|
Authorization | Required | The API tokenis required which can be found in the Airbridge dashboard. |
X-Forwarded-For | Required | Send the IPs with the X-Forwarded-For header when in-game events occur. If not, the server IP that called the API will be sent with the in-game events, and Airbridge will be unable to connect the ad click and in-game event. |
Accept-Language | Optional | Configure the preferred natural language and locale. ISO-639-1 applies. |
Content-Type | Optional | The media type of the resource. Default value is application/json. |
Authorization header can be found on the [Settings]>[Tokens] page in the Airbridge dashboard.
Parameters
Parameters
eventData.goal. To learn more about Standard and Custom Events, refer to this article.| Name | Required or Optional | Description |
|---|---|---|
user.externalUserID | 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. |
device | Optional | Send the device and platform information. |
eventData.goal | Optional | Send events collected from the PC game. The eventData.goal.category parameter carries the event names that appear in the reports. More information can be sent via the eventData.goal.action, eventData.goal.label, eventData.goal.value parameters, which can be viewed in the reports.Information sent via the eventData.goal.customAttributesparameter can only be viewed in raw data. |
devicesub-variables.
Send in-game events to Airbridge
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 Target Event, 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. It will be included in the prior attribution result or classified as unattributed. |
Attribution scenario
Attribution scenario
| Date | User | Events sent to Airbridge | Description |
|---|---|---|---|
| Jan 1 | User A |
| The PC Game Install event triggers attribution. |
| Jan 2 | User A |
| 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 |
| The PC Game Install event triggers attribution. |
| Jan 4 | User C |
| There is no prior Target Event. Therefore, all events are classified as Unattributed. |
| Jan 5 | User A |
| 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. |
S2S event API sending examples
Refer to the examples below for sending PC game events via the S2S event API.Sending PC Game Install events
Sending PC Game Install events
Sending PC Game Open events
Sending PC Game Open events
Sending in-game events without values
Sending in-game events without values
Sending revenue events
Sending revenue events
eventData.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.Testing
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 X-Forwarded-For header. |
| API configuration | Make sure the events are collected according to the API configuration. The API configuration can be tested by sending events without the X-Forwarded-For header. | Check the API configuration again. |
PC Game Measurement Setup Using Tracking Links
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.Pre-setup
The following pre-setup must be complete to continue.Create a tracking link
Create a tracking link

Get started with Airbridge
Get started with Airbridge

Design the event taxonomy
Design the event taxonomy
Request updating the probabilistic modeling settings
Request updating the probabilistic modeling settings
Sending PC game events to Airbridge
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.Testing
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 X-Forwarded-For header. |
| API configuration | Make sure the events are collected according to the API configuration. The API configuration can be tested by sending events without the X-Forwarded-For header. | Check the API configuration again. |
Reporting
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 theeventData.goal parameter. You can create a customized report view using the information sent via the eventData.goal parameters to fit your marketing needs.
View “Level Achieved” events
View “Level Achieved” events
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

View "Purchase Item" event
View "Purchase Item" event
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

Attention
User identification method for PC game measurement
User identification method for PC game measurement
Commonly made mistakes
Commonly made 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.