Skip to main content

Using Pageview and Engagement as a secondary goal

Updated over 2 months ago

Page Visit (Pageview) and Engagement are default metrics you can add as secondary goals in an experiment. You don’t need to create a custom goal — you add them when you set up or edit your test. They help you see how each variant affects not only your main conversion but also page views and clicks (e.g. thank-you page visits or sign-up button clicks).


What they are

  • Page Visit (Pageview) — Counts each time a visitor loads a page where Mida is installed. Tracked automatically; no setup needed.

  • Engagement — Counts clicks on links, buttons, submit inputs, and similar elements. Also tracked automatically; no setup needed.

Both can be used as secondary goals so you can compare variants by “did they view this page?” or “did they click this element?” in addition to your primary conversion.


Why use them as secondary goals

  • Page Visit — Tells you whether a variant leads to more (or fewer) page views per visitor, or whether more people reach a specific page (e.g. thank-you page).

  • Engagement — Tells you whether a variant leads to more (or fewer) clicks overall, or more clicks on a specific button or link (e.g. “Sign Up”).

Using one or both as secondary goals gives you a clearer picture: not only “which variant converted more?” but also “which drove more traffic to key pages?” and “which got more of the right clicks?”


How to add them

  1. When creating or editing an experiment, go to the step where you choose Secondary goals (or additional metrics).

  2. In the list of events/default metrics, select Page Visit and/or Engagement.

  3. Save. They will appear in the report next to your primary goal so you can compare variants.


Customizing with the attribution filter

By default, Page Visit counts all page views and Engagement counts all qualifying clicks. To focus on a specific attribution (e.g. thank-you page only, or only the “Sign Up” button), use the attribution filter (in the report this is Filter by attributes).

  • What it does — It narrows the metric so the secondary goal counts only events that match your conditions (e.g. URL, element text, class, or other attributes).

  • Where to set it — In the experiment report, open the secondary goals section, select the metric (Page Visit or Engagement), and click Filter by attributes (or the equivalent in your app). Add one or more conditions and save.

You can combine conditions (e.g. “URL contains thank-you” or “element text equals Sign Up”) so the secondary goal is full and clear: “visits to thank-you page” or “clicks on the Sign Up button.”


Examples

1. Thank-you page

  • Goal — See which variant sends more visitors to your thank-you (or confirmation) page.

  • Steps — Add Page Visit as a secondary goal. Open Filter by attributes and add a condition on URL (e.g. URL contains /thank-you or equals your thank-you page URL). Save.

  • Result — The secondary goal counts only page views that match that URL, so you see how many visitors per variant reached the thank-you page.

2. Click on a certain button, e.g. “Sign Up”

  • Goal — See which variant gets more clicks on the “Sign Up” button (or another specific button/link).

  • Steps — Add Engagement as a secondary goal. Open Filter by attributes and add a condition on element text (e.g. text contains “Sign Up” or equals “Sign Up”). Save.

  • Result — The secondary goal counts only engagement events where the clicked element’s text matches, so you see how many “Sign Up” clicks each variant generated.

Did this answer your question?