What data does Triggerbee collect on visits?
As soon as the Triggerbee tracking code has been installed on your webpage, Triggerbee will start to collect data on the visitors. The data collected can be divided into groups, session data, and profile data. There is also a difference between static data and dynamic, event-handled data.
When a session starts, eg. a visitor appears on your webpage - Triggerbee will automatically collect the following static data:
- Date and time of the session
- Registered IP Company (if no Company is registered, the Internet Supplier will display).
- The country and city that the visitor is in.
- The number of sessions has happened with that session-cookie (eg. is this the first time they are visiting).
- The platform the session happened on, for example: "Chrome 15 / Windows 7"
- The length of the session.
- The referrer (eg. if the visitor came from Google, direct or any other platform).
- All URLs visited during the session and the length of each URL.
Depending on your setup, Triggerbee will also collect the following dynamic data:
- Any goals that were achieved during the session.
- Any Onsite Campaigns that were displayed to the visitor, and its outcome.
- Interest Profiles
- If the Company is detected in the connected Pipedrive CRM.
- Any attached Tags
Once the visitor has been identified, Triggerbee will create a profile for that visitor. Some of the historical session data will then be transferred to that profile, enhancing the following data:
- Phone number
- Interest Profile
- First Seen on the webpage
- Last Seen on the webpage
- Total number of actions on the webpage
- Important Events, such as achieved goals and referral campaigns (and when they happened)
- A list of the latest visits
Some of these data points can be used to target your Onsite Campaigns. That data is:
- Achieved (or non achieved) Goals
- Audiences in connected Email marketing tools
- Browser language
- Source of the visit (facebook, instagram, email and other UTM-targeting)
- Query Parameters