Sometimes using ceid is not practical or desirable. For instance, if you have a very large number of elements which you want to track based on click position, you would have to assign unique ceid attributes to each of them. There is another option to consider if you are more interested in the click position than you are with knowing the precise element that was clicked.
By giving an element the CSS class -ce-capture, you force all clicks within that element to be “captured” by it. This means that all clicks will be tracked as if they occurred on the element with the class -ce-capture, even if they actually occurred on a sub-element. This way clicks within that part of the page will always appear in your reports, regardless of whether or not the actual clicked element could be matched with an element in your snapshot.
To modify the example above to use -ce-capture instead, it is necessary to wrap the images in a containing element. In this case we will use a <div>. Notice that no ceid attributes were added:
With this markup, any clicks on the images will be reported as if they occurred in the <div>. In addition, those clicks will be positioned in your report relative to the <div> rather than relative to the clicked image.
There is a trade-off with this approach. While your reports will always show the precise position of clicks within the <div>, the list and overlay views of your reports would not include any click data for the images themselves.
Was this article helpful?
Thank you! Your feedback is important to us.
Your feedback is greatly appreciated!