Check Event Tracking
Review user ID mapping and existing Airbridge events, then choose additional events and properties for your service.
Before using CUE, check that the events you already collect in Airbridge accurately record what users do in your app. Review your existing event tracking with the checks below.
Items to check
Check user ID mapping, app installs, and app opens before using CUE. If you use purchase predictions, also check Order Complete events.
User ID mapping
The ID you use in the Context API must identify the user you want to look up. Check that the user who generated the events is the same user you look up through the API.
Retrieve the ID from the SDK or configure its mapping according to the ID type you chose in Get Started. Braze Device IDs and external user IDs must be sent through the Airbridge SDK to connect them to an Airbridge user.
- To use
userId, initialize the Airbridge SDK and callAirbridge.fetchAirbridgeGeneratedUUID. Use the Airbridge Generated UUID returned in the callback asuserIdin your request. See Airbridge Generated UUID in the Data Fetching Guide for Android or Airbridge Generated ID in the Data Fetching Guide for iOS. - To use
brazeDeviceId, pass the Device ID from the Braze SDK to the Airbridge SDK as thebraze_device_iddevice alias. Use the same value in the request. See the Braze documentation for the setup instructions for each SDK. - To use
airbridgeExternalUserId, set your service's user ID withAirbridge.setUserIDin the Airbridge SDK. Use the same value in the request. See the Set up User ID section in the Android SDK documentation or the Set User IDs section in the iOS SDK documentation.
For a test request, open the app with this SDK setup and use the ID retrieved on the test device or set for the test account. brazeDeviceId is different from Braze's external_id.
App installs and opens
Check that Airbridge collects app install and open events correctly. CUE's prediction windows start at app installation. Churn predictions describe the likelihood that no activity events will be observed during a specified period after installation.
The Airbridge SDK collects app install and open events automatically. Check that your existing setup records actual installs and app usage. For details on these events and how to check them, see Testing the Airbridge SDK Integration for Marketers.
Order Complete events for purchase predictions
To use purchase predictions, check that you collect the standard Order Complete event, airbridge.ecommerce.order.completed. CUE's purchase prediction estimates the likelihood of this event.
Check the purchase events you already collect:
- The event category must be
airbridge.ecommerce.order.completed. - Your app must send the event after the user completes an order.
- Each completed order must be recorded without missing or duplicate events.
For details on event properties and when to send the event, see Event Types.
Recommendations for your service
We recommend choosing additional events and properties based on the actions and analysis that matter to your service. The examples below help you understand how people use your service. You do not need to track every event listed here to use CUE.
Key user actions
We recommend checking that events accurately record the actions that matter to your service. The examples below show what to review for different types of services.
| Goal | Example events | What to check |
|---|---|---|
| Understand the steps from product discovery to checkout in a shopping app. | Track Product View, Search Results, Add to Cart, and Initiate Checkout. | Check that product views, additions to the cart, and checkout starts are recorded as separate actions. |
| Understand whether sign-ups and sign-ins lead to service use. | Track Sign-up and Sign-in. | Distinguish successful sign-ups and sign-ins from visits to the sign-up screen and failed sign-in attempts. |
| Understand trials and subscription conversions in a subscription service. | Track Start Trial, Subscribe, and Unsubscribe. | Distinguish trial starts, subscription starts, and subscription cancellations. |
| Understand onboarding and progression in a game. | Track Complete Tutorial and Achieve Level. | Check whether users completed the tutorial and which level or stage they reached. |
Use an Airbridge standard event if one matches the action you want to collect. You can define a custom event for actions without a matching standard event. For event lists and definitions, see Event Types. The recommended event guides for commerce and gaming provide examples for each industry.
Event properties for analysis
We recommend collecting relevant properties when you need to analyze the products or actions behind an event. The examples below connect analysis goals to the information to check.
| Analysis goal | Information to collect | What to check |
|---|---|---|
| Review revenue by order. | Collect the purchase amount, currency, and transaction ID. | Check that the amount matches the amount paid and that the transaction ID identifies the order. |
| Compare views and purchases by product. | Collect product IDs, categories, prices, and quantities. | Check that the same product uses a consistent ID across events and that purchased products and quantities are recorded correctly. |
| Analyze Search Results events by search query. | Collect the search query. | Check that the query is recorded with its Search Results event. |
| Analyze game progression by level or stage. | Collect the level or stage reached. | Check that the Achieve Level event includes the level or stage the user reached. |
Use the Event Action or Event Label to break down events in Airbridge reports. Configure additional information, such as product lists, according to the relevant Semantic Attribute. For the purpose and format of each property, see Event Properties.
Properties that Airbridge requires, such as currency for Order Complete events, must be sent regardless of your analysis goals. For required properties and setup instructions, see Event Types.
Verify event collection
Review the events you already collect in the Airbridge dashboard. If you are unsure whether events are collected correctly, or if you recently changed a key app flow, you can test the action on a test device. Check that the event records the expected values at the intended time.
For instructions on registering a test device and checking the results, see Testing the Airbridge SDK Integration for Marketers.
After checking event collection, read Using Context to learn how to apply predictions and attribution information to screens and messages.