3rd party integrations
...
Purple Tracking
Tracking Configuration

Structure: Event types and attributes

6min

Event types and attributes level

Purple apps support tracking via several tracking services. Each tracking service usually distinguishes three types of events:

  • Actions
  • Views
  • Purchases

Some tracking services also support attributes.

  • Attributes

Attributes are fundamentally different from events because they do not represent an event that occurs at a specific time, but describe a state that a user or the app has.

Technical subdivision of events and attributes

Purple also use this division to reflect the behavior of the tracking services:

Name of key in configuration

Description

events

Groups all action events.

views

Groups all view events.

purchases

Groups all purchase events.

attributes

Groups all attributes.

Example

Introduction

We then show this division using an example (we have already learned the structure for this in chapter Structure: Tracking services):

First, let's assume a scenario where a Purple Customer wants to use Airship and Firebase. For example, the following structure would result at the tracking service level:

Document image


Add event types and attributes

Then the sections for the event types and attributes are added to the individual tracking services, as well as the default section. Sections can be omitted if no events or attributes are configured there.

For example, Firebase does not offer an API in its native SDK to send purchase events. It is therefore not necessary to configure the purchase section in Firebase and is omitted accordingly.



Document image


tracking_config.json