Campaign landing perf.

Campaign landing perf. lives in the Marketing area of the dashboard, under Attribution.

At a glance#

What it does#

Campaign landing performance joins four things nothing else here puts in one row: the UTM campaign, the landing page it sent traffic to, that page's Core Web Vitals, and the conversion and revenue it produced. Every row deep-links to a session replay.

The question it answers: which campaign's landing page is wasting spend — and then lets you watch it happen.

When to use it#

When a campaign underperforms and the creative is not obviously the problem. Ad platforms report on the ad. This page reports on what happened after the click, which is where paid traffic is most often lost and least often measured.

The specific failure it catches: a campaign sending traffic to a page that takes six seconds to render on the devices that campaign targets. The ad works. The click happens. The visitor leaves before the page appears, and the ad platform records a click and no conversion — indistinguishable from bad targeting.

Workflow#

1. 1

   Sort by spend, then look at the vitals column

   Money going to a slow landing page is the highest-value row on the page.

2. 2

   Compare conversion rate across campaigns hitting the same page

   Same page, different conversion rates means the difference is audience or intent. Different pages with the same audience means it is the page.

3. 3

   Watch a replay from a poor row

   This is the step that ends the argument about whether the landing page is the problem.

4. 4

   Fix the page, then re-measure

   Landing-page performance responds fast, and the effect is visible here within days.

Permissions and prerequisites#

Web apps only. Requires all three inputs: UTM-tagged campaign traffic, Web Vitals reporting, and revenue events. Replay links need session replay capturing.

Limits and edge cases#

• Untagged campaigns cannot appear. If your links carry no UTM parameters there is nothing to group by — see Links.

• Correlation, not causation. A slow page and a poorly-converting campaign appearing together is strong evidence and not an experiment. The same audience is often responsible for both — cheaper devices are slower and convert less.

• Vitals need volume per row. A campaign with forty sessions has an unstable p75.

• Replay links depend on retention and on replay having been sampled for that session.

Troubleshooting#

Rows have no campaign. Traffic is arriving untagged. Tag your links.

Vitals column is empty. Web Vitals reporting is not enabled, or that page has too few samples.

Replay link goes nowhere. The session aged out, or replay was not capturing for it.

Where the data comes from#

Joins UTM campaign × landing page × Core Web Vitals × conversion, so it needs all of those reporting; each row deep-links to a replay.

From the SDK

• Performance

• Session replay

Served by

• Dashboard

• Analytics

Related#

• Web Vitals

• Landing pages

• Attribution overview

• Click fraud

• Self-attributing networks

• Postbacks

• Partner event mapping

• Server-side conversions

• Marketing overview