Getting Started

Monitor landing pages with HeartBeat

Monitor landing pages with HeartBeat in YieldBI. Compare arrival rates, loading and uptime, filter page status, and configure alert rules and recipients.

YieldBI TeamGrowth ResearchUpdated Oct 2026

Silent video with English on-screen examples.

On this page

A strong ad still depends on a working destination. HeartBeat shows every landing page your ads point to, side by side, so you can spot the ones losing visitors or failing to convert.

Check HeartBeat when you launch a new offer, when results drop, or before you increase spend.

For related setup tasks, read Tracking & Events and Manage leads with Leads & CRM.

Read the overview

Select the account and a conversion target (for example, website registrations). Compare pages using the same target.

Area	What it tells you
Summary cards	Active URLs, arrival rate, click leak and conversion rate across the account
Traffic columns	Spend, Clicks, LP views, Arrival rate, Click leak and Conv. rate per page
Health columns	Load speed, 48h uptime, Trend and Attention per page
HeartBeat toggle	Whether monitoring is on for that page

Account-wide percentages can hide a weak page, so use the table to compare individual destinations.

Find the page that needs attention

Start with the question you’re trying to answer:

Situation	Compare	Why
Launching a product or collection	Arrival rate, load speed, uptime	Confirm paid traffic can reach the page before adding budget
Running a promotion	Arrival rate and conversion rate	Separate an access problem from an offer problem
Collecting signups	LP views and conversion rate	See whether visitors who arrive complete the signup
Results have dropped	Spend, clicks, visits, conversions, page health	Find which part of the journey to investigate

How to read the patterns:

Many clicks, few page views, slow load: visitors may be dropping before the page loads. Check access, speed and tracking.
High arrival rate, low conversion rate: people reach the page but don’t act. Review the offer, message and form.

Note: HeartBeat points you to pages worth investigating. A warning or correlation doesn’t prove the cause, and missing data isn’t the same as zero results. Registration results don’t show revenue or profit.

Filter by monitoring status

Use the filter to show Active pages (monitoring on) or Inactive pages (monitoring off). Check Inactive when adding new destinations, to make sure they’re covered. Monitoring status only says whether HeartBeat is watching a page, not whether the page is healthy.

Set up alerts

Open Alerts to choose which problems notify your team.

1. Choose the rules

Turn on the problems you want to hear about (see below). Rules marked pending provider need the related provider connected before you rely on them.

2. Set timing

The confirmation window sets how long an issue must last before it counts, balancing brief blips against real problems. The check interval sets how often pages are checked.

3. Pick recipients and channels

Add the people who will investigate. Choose channels; some (such as Email and Slack) may show as pending integration, and won’t deliver until that’s complete.

4. Choose how often to notify

Notify at open and resolve only for a concise history, Repeat while unresolved for reminders, or Escalate after a delay to bring in more people.

Rule	Use it to catch
Page unreachable	An advertised page that can’t be accessed
Load timeout	Pages that don’t finish loading in time
Significant degradation	A material decline in the monitored signal
Click-to-visit leak	A gap between ad clicks and landing-page visits
Conversion vs. speed	Slow loading alongside weak conversion

Regional monitoring settings are labelled planned; don’t rely on them until they’re available.

HeartBeat finds destination problems; fixing them still happens in your website or tracking setup.