Events and Attributes¶
LivePinch tracks multitude of events from various sources. Most of the events
tracked fall under
Sytem Events. System events generated during normal
operation. Examples of system events include
Web Push Received etc..
Apart from tracking these system events automatically, you can track any named event and associate any properties with the that event. This provides a rich source of engagement, interaction with a profile. How these events are tracked are covered and individual SDK. Here we describe, what makes a good candidate for custom event, what can be stored, and the other goodies Live Pinch makes available
Custom events can any name you associate with a user action, good examples would be
- Added to Cart
- Initialized a Game Play
- Booked a Hotel
You could attach any attributes with each event, apart from custom attributes LivePinch tracks several attributes such as acquisition sources, referrers, browsers, os, manufacturer, model, geo location etc…
When you first click on events section on the navigation, you’re directed to page that shows summary of all the events in the system. Below is an example illustration of the overview.
The overview page shows general summary event volumes over the recent past, The technographical landscape of such events
You can view all custom events in the list by navigating to
Click on each event, will show details of each event, Such as attributes associated with the
event. Recent Volume of the event, Technographical details of the said event
LivePinch allows for upload of events CSV Files via Uploads/HTTP/FTP methods. You can
upload events by navigating to
Upload Events section
Only CSV files are currently supported. The CSV file is expected contain first line with headers.
Following columns are mandatory
profile_key- This attribute maps the event to the profile identified by the profile key. See Profile Key section for how to use
event_name- This is the name of event performed by the user. See above for details on named events
Following columns are special, but optional:
_ua- If this column is given, the browser, os details are extracted from the user agent string
event_ts- This is considered the timestamp of the event, If this is not given, the import time is considered the event time, which is almost always wrong when it comes to uploaded events. Have a look at Date Formats for information regarding the date formats that are allowed
_ip- IP Address, If this column is given, Geo location is obtained from IP Location databases
All other attributes will be considered as custom attributes. The type will be autodetected. See Type Detection for more information regarding how types of given values are inferred.
Here is a Sample Events List CSV file for you to examine