> ## Documentation Index
> Fetch the complete documentation index at: https://help.airbridge.io/llms.txt
> Use this file to discover all available pages before exploring further.
# 4. Appendix: Event taxonomy examples
## Introduction
Are you designing an **Event Taxonomy** for the first time, or finding it difficult to align your taxonomy with Airbridge’s event structure?
Use this step-by-step guide to build an Event Taxonomy that works well with Airbridge reporting and analysis.
***
## 1) List the events you need to measure ad conversions
Start by listing the events required to evaluate advertising performance.
**Examples by vertical:**
* **Commerce:** Purchase Completed, Add to Cart, Product Detail View, Sign Up
* **Gaming:** Sign Up, Game Play, Level Achieved, In-App Ad Impression, Purchase Completed
If you’re unsure where to begin, think through the **user journey** first, then identify the actions that match your campaign goals.
You can also refer to Airbridge’s recommended events and taxonomy examples by vertical:
* [Recommended Airbridge events for **Gaming**](/en/guides/recommended-gaming-airbridge-events)
* [Recommended Airbridge events for **Finance**](/en/guides/recommended-finance-airbridge-events)
* [Recommended Airbridge events for **Commerce**](/en/guides/recommended-ecommerce-airbridge-events)
📌 Note: The Commerce Event Taxonomy example is shown here. For Gaming and Finance, please refer to the images in each vertical-specific user guide.
***
### ❓ “I’m not sure which events to track.”
If you’re unsure, consider the following:
* Is this a user action you need to measure ad performance **after app install**?
* Is this action used as a **settlement basis** for CPA campaigns (e.g., Sign Up, Purchase Completed, Level Achieved)?
✅ In most cases, we recommend tracking **around 5–15 events total**, combining **Standard Events** and **Custom Events**.
***
## 2) Add the events to **Event Category**
Next, enter the events you listed into the **Event Category** section.
### ✅ Events collected automatically (no need to add)
Once the Airbridge SDK is installed, the following events are collected automatically:
* **Install**
* **Deeplink Open**
* **Open**
You do not need to include these in your Event Taxonomy.
### ⚠️ Naming rules (important)
When defining **Custom Events**, follow Airbridge naming rules (for example, do not use the `airbridge.` prefix for Custom Events). Make sure to review the restrictions before finalizing event names.
* ▶ [Event Category naming rules and restrictions](/en/guides/airbridge-event-elements#rules-and-limitations-for-event-category)
***
### ✅ What are the benefits of using **Standard Events**?
Using Standard Events provides several advantages:
* **Better reporting support:** You can use localized metrics in **Actuals Report**, and view collected data (including values) immediately through built-in metrics.
* **Faster feature support:** Standard Events are supported first when new Airbridge features or reports are released. Some reports may support Custom Events later—or not at all.
* **Automatic mapping:** Standard Events are automatically mapped when sending events to ad channels via **Postback**, or when integrating with third-party solutions.
***
### ✍️ Example: Event Taxonomy (Step 2)
| Index | When to track | Event Category | Event Action | Event Label | Event Value | Semantic Attributes | Custom Attributes |
| ----- | -------------------------------------------------------- | ------------------------------------- | ------------ | ----------- | ----------- | ------------------- | ----------------- |
| 1 | After order is completed and the confirmation page loads | `airbridge.ecommerce.order.completed` | - | - | - | - | - |
| 2 | When a user clicks an event banner | `banner_click` | - | - | - | - | - |
***
## 3) Choose up to **3 properties** you want to see in Airbridge Reports
Collecting only **Event Category** allows you to see whether an event occurred—but not the details.
To view more meaningful insights in Reports, define:
* **Event Action** (String)
* **Event Label** (String)
* **Event Value** (Float)
For detailed constraints:
* [Event Action / Event Label naming rules and restrictions](/en/guides/airbridge-event-elements#rules-and-limitations-for-event-action-and-event-label)
* [Event Value restrictions](/en/guides/airbridge-event-elements#limitations-for-event-value)
***
### ✅ Example: How to define Action/Label/Value
If you want to segment **Purchase Completed** by product category and payment method:
* Set **Event Action** = “Product Category”
* Set **Event Label** = “Payment Method”
* Set **Event Value** = Final purchase amount
If you want to segment **banner\_click** by where the banner was clicked:
* Set **Event Action** = “Banner Position”
✅ Recommendation: Use higher-level groupings (e.g., category, payment method) rather than highly granular values (e.g., product name).
Too many unique values can make reports difficult to read.
***
### 🔎 How to view Action/Label/Value in Airbridge Reports
* In Reports, you can **Group By**:
* `Event Action`
* `Event Label`
* In Metrics, you can select:
* `Event Value` (to display numeric values)
***
### ✍️ Example: Event Taxonomy (Step 3)
| Index | When to track | Event Category | Event Action | Event Label | Event Value | Semantic Attributes | Custom Attributes |
| ----- | -------------------------------------------------------- | ------------------------------------- | ------------------------------ | ---------------------------------- | --------------------------- | ------------------- | ----------------- |
| 1 | After order is completed and the confirmation page loads | `airbridge.ecommerce.order.completed` | \{Product Category} e.g., Tops | \{Payment Method} e.g., creditcard | \{Final Amount} e.g., 53250 | - | - |
| 2 | When a user clicks an event banner | `banner_click` | \{Banner Position} e.g., Top | - | - | - | - |
***
## 4) Define additional properties for **Raw Data**
In Reports, you can only view three properties:
* **Event Action**
* **Event Label**
* **Event Value**
If you need more detailed attributes in **Raw Data**, define **Semantic Attributes**.
Semantic Attributes may include:
* Product name / Product ID
* Category name / Category ID
* Brand name / Brand ID
* Transaction ID
* Currency
### 💡 Tip (recommended for retargeting)
Semantic Attributes can also be used in **Postback** settings.
If you run retargeting campaigns, it’s helpful to collect relevant properties in advance.
Commonly useful properties:
* `Currency`
* `Product ID`
* `Product Price`
* `Product Quantity`
You can find recommended properties in the vertical taxonomy examples referenced at the top of this guide.
***
### Custom Attributes vs Semantic Attributes
If you need additional properties beyond Semantic Attributes, you can use **Custom Attributes**.
However:
* **Semantic Attributes** are recommended whenever possible
* In **Raw Data export**, Semantic Attributes are provided as separate columns
* **Custom Attributes** are provided as a single JSON string field (which is harder to analyze)
Airbridge-supported Semantic Attributes can be found here:
* [Semantic Attributes guide](/en/guides/airbridge-event-elements#limitations-for-event-value)
***
### ✍️ Example: Event Taxonomy (Step 4)
| Index | When to track | Event Category | Event Action | Event Label | Event Value | Semantic Attributes | Custom Attributes |
| ----- | -------------------------------------------------------- | ------------------------------------- | ------------------- | ----------------- | --------------- | ------------------------------------------------------------------------------------------------------ | ----------------- |
| 1 | After order is completed and the confirmation page loads | `airbridge.ecommerce.order.completed` | \{Product Category} | \{Payment Method} | \{Final Amount} | Transaction ID, Currency, Product ID, Product Price, Product Quantity, Category Name/ID, Brand Name/ID | - |
| 2 | When a user clicks an event banner | `banner_click` | \{Banner Position} | - | - | - | - |
***
### ✅ Why choose **Semantic Attributes** over Custom Attributes?
**1) Automatic mapping**
During ad channel Postback or third-party event forwarding, Semantic Attributes are often mapped automatically.
For example, if an ad channel supports search query tracking, Airbridge can map `semanticAttributes.query` during Postback integration—without additional setup from the advertiser.
**2) Cleaner data export**
In Raw Data export:
* Semantic Attributes are separated into individual columns by attribute
* Custom Attributes are exported as a JSON string
***
## ✅ Wrap-up
If you have completed all steps above, your **Event Taxonomy design is complete**.
Return to **1. Preparing for Airbridge Onboarding** and continue with the next onboarding tasks.
If you need further assistance or have questions, please use the **“Contact Us”** feature in the dashboard at any time.