# Auotrack & Custom Collections

# Auotrack

Our iOS and Javascript (Web) SDKs enable you to autotrack user interactions within the iOS app or a website without writing custom code. Autotrack works best for cases if you need to collect general event information (like URL, button type, etc.).

The initialized iOS SDK source will automatically collect the following events with data rich properties:

  • Interaction event. Aggregates all the “type” and “click” events. For example, the user clicks on a link, button, types a text into a form.
  • Launch event. Gathers data on the launch time (timestamp when the iOS app was opened), app name (e.g., Intempt Demo Shop App), iOS device (OS version, device name), geolocation (city, country) screen size (e.g., 667 x 376 px) also records unique visitorId and eventId values.
  • Scene event. Gets all the data from the UI structure - how and when (timestamp) your user transitions from one view to another. For example, the user goes from the main app view (Intemp_Demo_Shop.ViewController) to the login view (log_in.ViewController) – the event records this transition.

The initialized Web SDK source will automatically collect the following events with data rich properties:

  • Pageviews (page visits)
  • Clicks (on links)
  • Form submissions (including the data that was submitted with the form)

# Custom Event Collections

Custom collection (or custom events) allows you to collect any data you specify in the collection. The main difference between autotracked and custom event collections is that custom collections will enable you to get data without limitations - you can collect user name, email, address, or specific event information like purchase amount or product type. Autotrack only collects data that is predefined in the schema, so it is limited to the basic event information. We recommend using custom collections if you need to get as much contextual information as possible and choose autotrack if it is sufficient to have the basic event data.

# How to create a custom event collection

  • Create a web tracker source on the sources page.

  • After successfully creating a source, switch tabs to Schema.

img

  • To add a custom collection, drag ‘Add collection’ from the schema builder.

img

  • After creating the collection, drag ‘Add field’ from the schema builder to add a new field.

img

  • After creating a field, you set its properties. To update a previous field, click on it to update.

  • Make sure to add a visitorId and set profile identifier as one of its properties. See Developer docs (opens new window) for keys and identifiers to find out why.

img

  • Add an eventId to your schema.

  • Set up other custom field properties that match the data you plan to track.

Check the SDK documentation (opens new window) on how to to record custom event collections.