Know your user’s mind: Valentine’s campaign analysis – The aniakruk.pl Case

| March 11, 2021

There are more and more methods of measuring the effectiveness of campaigns. From traditional indicators and Google Analytics support, to more advanced tools focusing on campaign analysis. Most often, however, we target our analytical thoughts at the results themselves – whether presented in the form of numbers, percentages or visualized with charts. When trying to improve campaigns, we use trends and research of customer preferences, as well as “proven methods” from the market’s specialist. However, it soon turns out that the analysis of historical (or current) data on the campaign and the actual User Journey can be much more effective.

Valentine’s jewelry brand campaign

For aniakruk.pl, one of the Polish jewelry brands, we conducted a quick analysis of the Valentine’s Day campaign. Quick, because all we had to do was to compare the whole Valentine’s Day traffic to the traffic form campaign itself. It helped us understand what exactly customers were doing on the site. It also guided us on how to design new campaigns that will better suit users needs in the future.

But let’s start from the beginning. CUX automatically collects and generates heatmaps for all URLs that the user has accessed at least once. Thanks to this, we can analyze the data at any time. We do not have to plan in advance what address we will research and at what time we’ll do it. This allows – especially in a problematic – to use analytics to better understand any occurring event.

In the case of aniakruk.pl, right after Valentine’s Day, we started the analysis by checking how customers generally behaved on the page with products specially selected for the occasion. We used heatmaps for “direct” entries and for visits navigating within the Valentine’s Day offer.

aniakruk.pl and CUX: campaign analysis

The heatmap applies only to entries on a specific URL

By analyzing the clicks on the heatmap, we did not notice any unusual or questionable events. We’ve observed a rather natural, diffused flow of customers, without too much involvement in browsing individual products. Most of the clicks accumulate around the option to choose a specific assortment (on the left).

aniakruk.pl campaign analysis: CUX heatmap

Heatmap for the aniakruk.pl Valentine’s campaign

Filtering: Campaign only traffic

After the initial analysis, we’ve decided to check what the same entrances looked like in the case of customers who clearly came to the site from external campaigns. To do this, all you have to do is filter the entries after the given URL. The address should have an additional “tail” to recognize where a given client came from, e.g. fbclid.

Using filtering, we have prepared a list of all addresses of interest to us. Then we’ve generated a grouped heatmap for them (the function is in the upper right corner of the page). Such a heatmap allows to generate a collective image for many URLs. URLs under which there are pages with the same structure – e.g. product pages or just campaign entrances. Those addresses, in the basic analysis, will be only visable in the form of separate URLs.

aniakruk.pl campaign analysis: CUX grouped heatmap

Grouped heatmap allows you to see the same page displayed by visitors using different entry points.

In this case, the situation is slightly different from the case of “direct” entries. First, we see a clearly greater involvement of users who clicked more often (more red spots). The grouped heatmap also allows us to observe that customers did not click on the products themselves as eagerly as on the filtering options. They were trying in all possible ways to narrow down the range of products! The item in the top menu under the name “Czego szukasz” [eng. What are you looking for] was also very popular.

Searching for frustration

Interestingly, we did not see an increased or significant number of clicks in the menu after its expansion. Only a few clicks in the vicinity of the banner. Remember that a heatmap is only a visualization of a single page state. If customers expanded the menu, then in the classic heatmap we will observe clicks “floating in the air”. When in fact they may relate to elements such as pop-ups, widgets or just a sliding menu. From the analysis of the grouped heatmap, we can conclude that customers did not move further on the site. This may suggest that they did not find what they were looking for. A conclusion that is especially emphasized if we go deeper into the analysis.

aniakruk.pl and CUX: grouped heatmap

Grouped heatmap of the jewelry brand’s Valentine’s Day campaign

Changing the data display type to “rage clicks” only confirms our hypothesis. Customers were disappointed after clicking on the aforementioned category. In addition, it gave us valuable information about existing problems. Including the info about usefulness of a slider that allows filtering by prices. We could also observe the lack of decisiveness or difficulties of customers in choosing the way of displaying products.

Campaign analysis: CUX rage clicks

Grouped heatmap of the jewelry brand’s Valentine’s campaign focused on “rage clicks”

Conclusion

Contextual campaigns focused on individual product categories sell up to 3x more. Based on the above analysis, customers need to narrow down the results they get in e-commerce. It mainly shows in their behavior on the website. Things like moving mainly around the filtering options, clicking the “What are you looking for” menu bar or rage clicks around the price changing slider.

Our recommendation is to base the next campaign on segments, e.g. products in specific price ranges. In the meantime, we also recommend further investigating the usability problems of the price slider. Working out a new solution for it could significantly improve conversion.

Read also


Ready to start your journey with smarter analytics and UX automation? Drop us a line at team@cux.io

Want to harvest the freshest analytical crops? Sign up for the cux.io nourishing newsletter! Be careful! We may grow on you! 🥑 😉

Tags: , , , , ,

Categorised in: ,