A report data point (or data point) is a named counter you can attach to a lead. Campaign rules can add to it, subtract from it, or clear it, and other rules- or your reports - can read its running total back. Data points give rules a memory: a way to remember how many times something has happened to a lead, beyond just its current status.

What a Data Point Is (and Isn't)

Think of a data point as a labelled tally kept per lead. For example, a data point called "Brochure Sent" could count how many times an agent has emailed a brochure to a lead, so a rule can stop after the second one.

A data point has only two properties: a Name and a Description. There is no "type", no aggregation setting, and no default value - it is simply a named counter, and its value is always worked out from the changes rules have made to it.

Under the hood, every change is stored as a small event:

• an increase records +1,
• a decrease records −1,
• the data point's total is the sum of those events (increases minus decreases).

Where You Set Up Data Points

Data points are created once per account and then reused across campaigns.

1. In the main menu, open Settings > Advanced Lead Settings >Data Points Management.
2. The page lists your existing data points (ID, Name, Description). Click Create New Data Point.
3. Fill in:
   • Name: required, and must be unique (for example, Voicemails Left).
   • Description: required; explain what the data point is for so colleagues understand it later.
4. Click to save. The data point is now available to pick inside campaign rules and reports.

Using Data Points in Rules

Data points connect to rules in two places — an action that changes the value, and a condition that reads it.

The Action — Change a Data Point

Add this as a rule action (the THEN side):

The Condition — Test a Data Point

Add this as a rule condition (the IF side):

Datapoint "" was (more than / less than / equal / not equal) N times

You can optionally scope it to a recent window - "for the last N hours" or "for the last N days" - so only recent changes count. Without a window, the whole history is summed.

There is also a per-agent variant, "Datapoint … was … times for user", which sums only the changes tied to the lead's assigned agent.

Worked Example — Capping Voicemails

Horizon does not want to leave endless voicemails for the same lead. A data point called "Voicemails Left" lets the rules count them and change tactics after the third.

First, an admin creates the data point in Data points setup (Name: Voicemails Left).

Then two rules use it together:

So David - who keeps going to voicemail - has his Voicemails Left total climb 1 → 2 → 3. On the third, the second rule fires and parks him for a month instead of leaving yet another message. If David later answers and has a real conversation, a third rule can clear Voicemails Left so the count starts fresh next time.

Related Guides

• Campaign Rules
• Campaigns Management.

Getting Help

Submit a support ticket or contact your account manager to set up data points or the rules that use them.