Custom Actions Dashboard

Once you enable action tracking, whether it is Click, Download or your custom ones, eventually, you will want to start analyzing these on your dashboard.

The Actions dashboard allows you to define an Action Filter and inspect metrics for view and user sessions based on these actions.

Moreover, you can pick two action filters and compare them side by side on a single screen. This feature unlocks A/B testing on your website, based on selected user interactions.

Create your filter

To add your first filter, go to your site, and switch the view to Actions. Once there, click Manage to add your first Action Filter.

First, select what kind of events you want to filter on. You can choose Click Event, Download or Custom Action. Depending on what action type you are filtering on, there will be different attributes you can select.

Second, give your filter a name. A name must be made of letters and numbers and can contain underscores or hyphens. For example case-study-client-xyz.

You can make your filter public. If the filter is public, users with access to this site can see and use it. However, only you can edit and delete that filter.

When filter is not public, only you can see and use the filter.

By providing a name and picking a type, you created a generic filter that allows filtering of all click, download or custom actions. If you want to be more specific, you can enrich your filters with additional attributes. These attributes must match the values used when the event was generated.

Depending on the type of event, there are either one or more predefined attribute names you can use.

Download Event

File-based events support the following attributes:

• href - a full URL of the file
• filename - a file name with extension, e.g.: brochure.pdf
• ext - a file extension, e.g., zip

The marked download events support the following options:

• href - a full URL of the file
• tag - name of the HTML tag that triggered the download event, for example, button
• name - a data-waa-click attribute associated with the element triggering the event

Example: We want to track download events on a specific PDF which contains a case study from Financial Services industry, published in May 2022.

Our website contains the following HTML:

<a href="https://cdn.example.org/assets/case-study-may-2022.pdf">Download Case Study</a>

To see downloads of these PDFs on the Actions dashboard, create the following filter:

Click Events

Click events have only one predefined attribute, the name. You can add additional three attributes to your filter to match more specific clicks.

Example: We want to compare which buttons on our website are clicked more often, depending on the source of incoming traffic.

Our HTML code looks as follows:

<button data-waa-click="newsletter-cta" data-waa-action="buy">Buy Now</button>
<button data-waa-click="newsletter-cta" data-waa-action="trial">Start Trial</button>

We can then create two filters to compare how these buttons perform next to each other.

In the Actions Dashboard, when you compare cta-action-trial with cta-action-buy, you can analyze the characteristics of traffic that leads to either paid or trial subscription.

Custom Action

Custom Action filters, like Click Events, have only one predefined parameter: name. Other attributes can be added and have to match the params that you passed in during the dispatchEvent call in JavaScript.