# Getting started
In Intempt, you create a source for each website or app you want to track. While it’s not required that you have a single Source for each server, site or app, we highly recommend creating a Source for each unique source of data.
You can create new sources using the button in the Sources view (opens new window). Each source you create has a Source ID, which is used to send data to that source.
Sources can be picked from below listed categories:
- Web Tracker - for tracking all data flowing through your website.
- Mobile/iOS tracker - for tracking all data flowing through your iOS Application.
- API Source - send your data directly to our HTTP Tracking API. Prefered source if you don’t have a library for your environment yet. Allows to manually create collections, relations, identifiers, etc.
- Cloud apps - empower you to pull together data from all of your different third-party tools into the Intempt database or select destinations.
# Types of Data Sources
|Data source||How it works||Data collected|
|Web/mobile||Any web page/mobile application with Intempt tracker installed||Products, categories and pages browsed, clicks, store, interaction data, number of pages/sessions|
|API||Integrate communications directly from your servers||Track any data collected|
|Cloud apps||Export data from its third party tool and import it into Intempt platform (e.g. Google Ads, Shopify, Hubspot)||Customer information, deals, purchases, orders, campaign statistics|
Collections describe schemas for events or data of a certain type, while collection data items represent specific pieces of data in that collection. To put that in relational terms, collections are tables that describe columns (types, constraints, etc.), and collection data items are rows of values for those columns.
- Sign up
- Hotel booking
- Page view
Data item examples:
- Purchase amount
# Auotrack & Custom Collections
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 Collections
Custom collection (or custom events) allow you to collect any data that you specify in the collection. The main difference between autotracked and custom collections is that custom collections allow you 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 which 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.
- To add a custom collection, drag ‘Add collection’ from the schema builder.
- After creating the collection, drag ‘Add field’ from the schema builder to add a new field.
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.
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.