For current or prospective Kissmetrics customers who prefer to avoid the often lengthy and complex process of manually instrumenting events, Convizit offers an appealing alternative. With no need for a tagging plan or manual event coding, Convizit’s AI-driven solution automatically collects user behavior data in websites and web applications. Convizit sends this event data – already named and property-enriched – into Kissmetrics for reporting and analysis.
On-demand historical data backfill allows additional behavioral analysis at any time, by sending additional historical data into Kissmetrics, even if you initially decided not to receive those events and/or properties. And Convizit handles ongoing website changes automatically so that funnels and reports don’t break; no event tracking maintenance is required.
Convizit’s direct integration with Kissmetrics allows you to quickly and easily realize the full potential of the platform within days of deployment, with little or no manual effort required. This document describes how this integration works.
B. Getting Started
This is the process to begin receiving event data from your website/application into Kissmetrics via Convizit:
1. Add the Convizit tag to your website or application
As soon as the Convizit tag is operational in your website/application, Convizit will begin collecting, naming and structuring the user behavior data.
2. Provide Convizit with your Tracking API Key
Provide your Kissmetrics Tracking API key to your Convizit account manager. This key can be found in the Kissmetrics Product Settings page:
3. Customize the data that Convizit collects (OPTIONAL)
- To associate your own known customer IDs with Convizit’s event data (highly recommended), see: Customer Identification and Enrichment
- To prevent Convizit from capturing clicks on specific website elements, see: Ensuring Data Privacy
4. Convizit will deliver your user behavior data into Kissmetrics
- Convizit will typically begin sending data into Kissmetrics within about one week from the time the Convizit tag is added to your website. Low-traffic sites might take longer (Convizit’s AI needs a certain amount of actual user traffic in order to accurately model a website or application).
- Convizit sends data into Kissmetrics every 30 minutes.
- If, at any time, you wish to pause data delivery into Kissmetrics, inform your Convizit contact person.
5. Validate that you are receiving data from Convizit
You can see the events arriving from Convizit in Kissmetrics in the Event Manager > Tracked Events page. Note that it can take a few additional minutes for the data to appear on this page after it was received from Convizit.
If you also have other sources of event data in Kissmetrics, you can confirm that events from Convizit’s are arriving in Kissmetrics with these steps:
- Navigate to Reports.
- Click Create New Report.
- Select an event.
- Filter by Source equaling Convizit.
- Click Run report to see the data.
C. Customizing the Data Delivered by Convizit into Kissmetrics
Using Convizit’s visual interface, you can easily understand the data that Convizit is capturing, and adjust how events and properties are delivered into Kissmetrics:
- Review all the events and properties that Convizit is capturing.
- Select which events to receive in Kissmetrics.
- Change the names of events and event properties.
- Exclude specific event properties from some/all events.
D. The Kissmetrics Fields Populated by Convizit
For more technical users familiar with Kissmetrics, these are the specific fields that Convizit populates in Kissmetrics for each delivered event:
|Event Name||Name of the event (e.g., “Add to cart”, “Size chart click”)|
|Event Time||Timestamp of the event in UTC as reported by the visitor’s device|
|Visitor ID||Convizit’s unique ID of the visitor|
|Customer ID||Identified customer ID passed by the website to Convizit|
|Campaign Source||UTM Source parameter provided for the session, if available|
|Campaign Medium||UTM Medium parameter provided for the session, if available|
|Campaign Name||UTM Campaign parameter provided for the session, if available|
|Campaign Term||UTM Term parameter provided for the session, if available|
|Campaign Content||UTM Content parameter provided for the session, if available|
|KM Referrer||Referring URL to the session, if available|
|KM Returning||True for returning visitors, False for first-time visitors|
|KM Device Type||Visitor’s device type (e.g., desktop, tablet, mobile)|
|KM Operating System||OS of the event sender (e.g., Android, iOS, Windows, Mac OS)|
|KM Browser||Browser name (e.g., Chrome, Safari)|
|KM Browser Version||Browser version number|