ClientConscious is designed to create an event on all meaningful user clicks that actually trigger some action on your website. You will receive all events for example on video player interactions, form interactions and from submissions, interactions with images, but you will not get information on any clicks that happens on non-clickable areas like your background. 

No duplication

Apart from a few very rare cases 1 click will trigger 1 event only to avoid tracking multiple events that represents the very same user interaction and to spare bandwidth and analytics storage too. To take an example if the user clicks a button that also happens to be an add-to-cart button, then only the add to cart event will be tracked, since that is the more specific one. You can find more information on when a ceratain event is considered to be more specific compared to another one in the detailed descriptions for events.

No bucketing

When an event is created it is received by all platfroms that you have added to your configuration and are active on the page ( they are not probably restricted to other pages only ). This means that if you have a Google, a Meta and a Pintetrest pixel on your website and the page is loaded, all platforms will receive a page view event. This enables you to select the same user groups within platfroms and to look at the same data in different analytics systems.

Native event names when possible

To stick with the page view event, Google uses page_view, while Meta and Pinterest uses PageView as their native format. When a native format of the event name exists, that format will be used to push the event  to the given platform. Google will receive page_view, while Meta and Pinterest will get a PageView. This is happening under the hood automatically to enable all platfroms to make complete sense of your data and to help their built-in AI to operate to its fullest potential. If a native event name does not exist, then the platform will receive the underscore, all lowercase version of the event name, page_view in the case of a page view event.

Rich event data

All events come with a set of specific and common attributes. Common attributes are added to all events next to their specific ones. You can find all information about common attributes in the Rich Data section. To give an idea on what they are they include information like weather data or a reliable page depth. 

Information on specific attributes can be found in the descriptions for events. We try to push all attributes to all platforms but unfortunately X ( formely Twitter ) for example does not accept any custom attributes and in this case you are not able to get this data in X but only in other platforms like Google or Meta, which do allow to add more information.