BlueConic can answer “how often did this person visit, and how long did they stay?” in several ways. The right one depends on the window you care about: the last 30 or 90 days, one path on the site, a single session, or time spent. This article matches each of those questions to a setup, and names the setting that decides whether the number can actually cover that window.
Start with the section that matches what you want to measure.
Rolling count of visits in the last N days
Use the Visit Listener Number of Visits (ranged) property.
Set Number of Days to N. Set Visit Timestamp Property, and set Max. Number of Timestamps to at least N. The ranged count is the number of stored visit dates inside the window, and it cannot exceed that cap. It is recalculated when a new visit starts. It does not fall each day on its own, and it does not include visits from before the listener was turned on. On the next visit it can drop sharply, because dates outside the window are left out of the new count.
Restrict Where to the channel you mean. One listener on all channels mixes every brand into one number.
Visits to one path in the last N days
Use the same Visit Listener, with Where limited to that path. The steps are in Count visits to one path in the last N days.
A Behavior Listener that matches the URL and stores Visit date and time records when that page was seen. One date-time property holds the latest view, not a count of views inside N days. Use it for “seen this path” or “last time they saw this path.” Use the Visit Listener ranged property for “how many visits to this path in N days.”
Session counts and time on site
Total Number of Visits on the Visit Listener is the running total of visits since the listener was on. It is not limited to N days.
Number of Page Views (last session) is only the most recent visit.
Average Visit Time and Total Visit Time are minute totals for visits this listener has seen. For time spent on a specific page, use a Time Span Listener on that page rather than the visit average.
The Global Listener keeps cross-channel visit fields, including a read-only last visited date. Those fields are separate from the properties you chose on the Visit Listener.
When a timeline rollup is the right tool
A timeline event rollup can count events already stored, including history from before you created the rollup, for whatever the event actually contains.
The built-in pageview event stores the referrer and the BlueConic item IDs that ran on the page. It does not store the page path. A rollup on that event cannot count visits to a path.
Use a rollup when you already have an event type with the field you need, such as an order event for purchases in the last 730 days. For a path on the website, store visit dates with the Visit Listener, or send a custom event that includes the URL and roll that event up.
You need | Use |
Visits in the last N days, for a channel | Visit Listener, ranged count, timestamp cap at least N |
Visits to one path in the last N days | Visit Listener with Where limited to that path |
Last time a page was seen | Behavior Listener, visit date and time, on that URL |
All visits since the listener was on | Visit Listener, total number of visits |
Time on the visit, or time on one page | Visit Listener visit-time properties, or a Time Span Listener |
A count over history that is already in timeline events | A rollup on an event type that stores the field you filter on |
Visits to a path from the system pageview event | Not available. That event has no page path |