Here are answers to some commonly asked questions about Convizit.

Simply add the Convizit JavaScript snippet to your website (see here for details) and, within days, Convizit will begin sending you complete, context-enriched and structured user activity data. Regardless of how often or how significantly your website changes, there is no further setup, configuration or other effort required.

No. Convizit’s client-side JavaScript code runs asynchronously, and impacts performance even less than the Google Analytics snippet that’s running on millions of websites. There is absolutely no impact on user experience or SEO rankings.

Convizit provides you with a data stream of every action that every user performs on your website – including every click on every element within every webpage – along with fully named and already-structured context details for each individual click performed by each user. With absolutely no effort on your part. Learn more here.

Absolutely none! While data scientists typically spend a huge amount of their time preparing data for analysis (including cleansing it, standardizing it, naming it and structuring it), Convizit’s data arrives already fully named, tagged and structured – and ready for immediate insight generation or marketing activation!

Convizit can continuously deliver a complete, ongoing data stream directly to your data warehouse, CDP or other platformIf you need to receive the event data stream in realtime (important for realtime applications, such as website personalization), Convizit can deliver the user behavior data stream directly from the client, for true realtime data delivery. In addition to the data stream (or instead of it, if you prefer), you can query the Convizit API at any time to retrieve the particular data you’re interested in using.  

Convizit supports direct, ongoing sync with a number of systems (see the list here; additional integrations can be provided upon request), as well as via a rich API (complete documentation of the Convizit API can be found here).

If you want to retrieve user activity data on demand, using the Convizit API, you decide how long you want Convizit to retain the data. If you opt to only receive the complete data stream directly into your systems, Convizit deletes all captured data within 10 days (retaining the data for this period of time allows Convizit’s machine learning algorithms to improve their understanding of the website).

Convizit is dedicated to ensuring compliance with all applicable company policies and regulatory requirements as regards capturing private customer data. To ensure that no personally identifiable information (PII) or other regulated data is collected, Convizit combines automatic exclusion of certain types of website content with a manual mechanism that allows site owners to exclude portions of their website from being captured by Convizit. More detail about these mechanisms is here. Because of the great importance of data privacy in today’s world, Convizit is continuing to refine and develop its technology to help its customers avoid capturing, transmitting or storing any sensitive or regulated data.

Yes! Unlike other auto-capture solutions, which rely on identical coding of similar elements, Convizit groups functionally identical elements, by intelligently analyzing element and context similarity. The result is consistent, complete and reliable event data, even when minor differences in coding or page structure would trip up less advanced solutions.

Convizit ensures the continuity of element tracking over time, even when minor visual/code changes are made to elements – as is typical, for example, during A/B testing. By intelligently analyzing element and context similarity, Convizit’s tracking of particular elements doesn’t become obsolete and funnels don’t break. Tracking continuity is one of the big problems with previous attempts to automatically capture user events on websites. Because other auto-capture tools rely on hard-coded element identifiers, they are unable to continue to track elements when minor changes are made to an existing UI element (e.g., changing its class, ID or text) or the webpage in which they exist (e.g., other elements are removed or relocated, changing the DOM structure of the page).