Structure: Event types and attributes

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 true false 154false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type example introduction we then show this division using an example (we have already learned the structure for this in chapter structure tracking services docid 28levq2nvel a perh1rd ) 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 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 tracking config json example code { "default" { "events" { }, "views" { }, "purchases" { }, "attributes" { } }, "airship" { "events" { }, "views" { }, "purchases" { }, "attributes" { } }, "firebase" { "events" { }, "views" { }, "attributes" { } } }