Marketing technology is evolving fast. There are new tools coming out every month, new A/B testing frameworks, new chat widgets that all allow access to their information in different formats. Optmizely might call the experiment identifier experiment_id while Google Optimize calls it experiment. One chat widget says chat widget opened, the other reports interaction started. It doesn’t really become a problem until you make changes to the technology that is running under your website. What usually happens at this point is that the data collected up until the switch becomes unusable.

Constant change makes long-term analytics cumbersome

On top of that your website design is constantly being outdated and adjusted. You change a button on your website which had a button click event, but later it becomes a newsletter signup. A couple months down the road nobody remembers what the previous event was and nobody knows how to connect the current data point to the previous one. Wouldn’t it be nice to have a solution for such scenarios?

One naming convention above all

Since ClientConscious comes with a clear and pre-defined naming convention, when your are using our platform all such problems (and many more 😃) are solved automatically. All clicks on a button are always called button click regardless of the intent (you can identify intent via button text or id) so even if you changed your desing you would be able to cross-reference old and new data across changes to the website design, A/B testing tools, chat widgets and many more.

But wait, there’s more

If you took an honest guess, when you implement a new platform, how many of the platform specific events that are available are you implementing on average? Based on my experience not a substantial part. Did you know for example that Optinmonster provides data on alll Campaign opens that could be available in GA4? Or that Snapchat and other chat widgets provide data on opens, closes and conversation flow?

The usual drill is implementing the most important events as we get to know them. But on a great average nobody goes to read through all platform documentation to seek for all events that are out there, if we listen to them. ClientConscious does this on your behalf. Whenever you add a new platfrom through the configuration interface, we add support for all of the events that it provides. If we can generalize something and always call experiment id experiment_id for your convenience, we will do so in a well documented fashion, otherwise we will just track the data for you in its native format.

So if you want to focus on analyzing your data and not to worry about how to collect it in forst place give ClientConscious a try and focus on what is important and unique to your customers.