ListsA list is used to group actions or properties together. When actions belong to a list you are able to see all the actions in one graph. For example if you define a list named 'User Type' and add two types of actions to it 'Registered user' and 'Visitor' you will be able to see both types of visitors versus any other property you choose (e.g. original referrer). In addition we will be able to give you insights about the two actions. For example Zoom Analytics engine could uncover that users coming between 08:00-09:00 are more likely to be 'Visitors'. Other example of lists could be 'Article type' for a website that has several sections with articles. For example a newspaper that has 'News', 'Sports' and 'Economics' sections. When user reads an article from the 'Sports' section an action will be sent with 'list_name': 'Article type' and 'action_name': 'Sports'. Zoom Analytics engine will find hidden connections between the different sections user read and the goals you have defined. For example "Users who enter the website between 09:00-10:00 are more likely to read the 'Sports' section. 15% of them read the Sports section."
ActionsAn action can be any interaction the user has with the website. An action should be triggered only when user actively does something. An action can be a goal or a non-goal. If it is a goal then Zoom Analytics engine will look for insights that will help improve the goal. If it is a non-goal then the engine will look for connections between the action and all the other goals. Note that every page viewed is automatically an action.
If you want to send an action not as a result of a user interaction with the website it is usually a property which describes the user.
Action countersAn action counter can count any interaction of the user with the website. An action counter should be triggered when user actively does something. We recommend you focus on counting actions that have a business meaning, for example how many posts has the user read this session, how many photos has she enlarged, how many product reviews has she read. An action counter can be a goal or a non-goal. If it is a goal then Zoom Analytics engine will look for insights that will help improve the goal. If it is a non-goal then the engine will look for connections between the average number of occurrences of the action and all the other goals. For example 'Users who read more than 4 product reviews are less likely to complete the goal "Buy Item"'.
PagesYou can define any page to be a goal through the Account page. You can track the number of visits to that page through Analytics Page
GoalsA goal can be any interaction of the user with the website that you would like to find insights about. A goal is usually something positive you would like to maximize, such signup, share or buy. But you can also define a negative goal (by adding tag 'negative_action'). A negative action can be cart abandonment, or user that starts authenticating a service (e.g. Facebook) but cancels in the middle. A 'negative' goal that is defined automatically is 'Bounce', which is added whenever a user visits only one page during a session, and the visit duration is between 2-10 seconds (shorter visits are assumed to be uninteresting).
PropertiesA property is peace of information that describes the user. Many properties are added automatically such as referrer, entry page, country, language, entry time and many more. Using the API you can add additional properties such as 'days since signup' or 'Registered user' vs 'Visitor'. Zoom Analytics engine will look for insights between all properties (automatic and custom-defined) and all the goals defined. An insight could be 'Returning users who have signed up more than 20 days ago are more likely to buy again'.
int_valBoth action and property can have an integer value. When an integer value (int_val_property or int_val_action) is sent in the API call, we will keep track of the average value of that action or property. You will be able to see the average value versus any action defined. For example you could see the average amount bought by referrer or by entry page (or any other property or action). Zoom Analytics engine will try to find hidden connections between the average value and actions and properties of your users.
Tags for actions'signup' - e.g. signup to website
'buy' - e.g. buy a product or a service
'share' - e.g. facebook share, pin to pinterest
'watch_content' - e.g. read comment, read article
'add_content' - e.g. write comment
'preview' - e.g. preview product, preview photo album
'renew' - e.g. renew subscription
'positive_feedback' - e.g. 'like'
'contact_us' - e.g. contact us, feedback
'support' – ask for support
'negative_action' - a negative action. e.g. unsubscribe from service, unsubscribe from email list, cancel authentication of 3rd party
Tags for properties'user_type_registered', 'user_type_visitor' – to identify registered users and visitors
'days_since' - e.g. days since signup, days since last login, days since last purchase. Relevant only when using property_int_val.
'amount' - e.g. amount bought historically. Relevant only when using property_int_val.