Qualifying visits
Set eligible locations, time windows, participants, and confidence requirements. Treat freshness and evidence limits as part of the arrival decision.
Arcus brings the verified-outcomes model to restaurants, shops, entertainment venues, and other place-based businesses. Define a qualifying visit, evaluate arrival evidence, connect eligible participation to rewards, and understand the program's verified foot traffic and repeat visits.
Discuss an arrival programA merchant's goal may be a quieter-period visit, a group arrival, repeat participation, or an eligible event check-in. The program policy defines what must happen and what evidence supports it.
Set eligible locations, time windows, participants, and confidence requirements. Treat freshness and evidence limits as part of the arrival decision.
Connect rewards to qualifying arrivals rather than promotional reach. Campaign rules and funded capacity bound the authorized issuance.
Understand which qualifying visits recur, what the program funded, and the cost per outcome through permitted reporting.
Define the qualifying visit, approved location, time window, evidence threshold, reward conditions, and review responsibilities.
Use sources appropriate to the program, such as a partner check-in or permissioned location observation. Add qualifying dwell only when required and supported.
Record whether the evidence meets the policy, is insufficient, or needs review. Preserve reasons and confidence rather than flattening every claim into a count.
If the arrival qualifies for a reward, link issuance to that decision and the campaign's remaining authorized capacity.
| Signal | What it records | How Arcus frames it |
|---|---|---|
| Promotion or RSVP | Interest, reach, or an intention to attend | Context for the program, distinct from arrival |
| Check-in | An observation or assertion of participation | Evidence evaluated under the arrival policy |
| Verified qualifying arrival | A decision supported by the required evidence | An accountable program visit with reasons and confidence |
| Qualifying purchase | A transaction supported by authorized purchase evidence | A separate outcome linked only when the program supports it |
| Estimated total footfall | A modeled or observed estimate of overall traffic | Reported separately from verified program arrivals |
Verified program arrivals describe participation in the defined program. They are not automatically a census of everyone who visited or proof of what each visitor spent.
A venue needs evidence about a qualifying visit and the campaign result. Reporting should remain within that purpose.
Minimum necessary disclosure, coarse location context, aggregate results, and small-group suppression help bound the information a program exposes. Retention, consent, evidence access, and reporting controls are agreed for each deployment.
For a live-event example of consumer participation becoming a graded arrival record, explore Tally. For the underlying decision model, read the verified arrival guide .
A verified arrival establishes that the available authorized evidence satisfied a defined arrival policy. The record should retain the location and time criteria, evidence context, decision reasons, and confidence limits. It can support an eligible visit or reward; it does not by itself establish a purchase, customer spending, or total venue footfall.
A campaign can define eligible locations, arrival windows, participant rules, reward terms, and authorized capacity. The intended mechanism connects issuance to the qualifying arrival decision. A merchant can then review verified program arrivals, repeat participation, issued and denied rewards, remaining capacity, and cost per qualifying outcome.
A check-in is one source of evidence. The policy determines whether it is sufficient on its own or needs corroboration such as an authorized partner record, permissioned location observation, or qualifying dwell. Report qualifying program arrivals separately from estimates of total foot traffic so an estimated number does not become a verified count.
If a program requires a qualifying purchase, it needs separately authorized transaction evidence and an explicit rule linking that purchase to the participant and visit. Arrival verification alone should not be described as verified spending. Evidence permission, data access, and integration scope must be established with the merchant.
Bring your location, participation goal, proposed reward, and evidence sources. Define one arrival program before expanding to additional sites or outcome types.
Arcus is a platform initiative in development. Pilot scope, integrations, controls, and readiness are agreed for each deployment.