Scenario

Campaigns and event check-ins

Count people who actually came — then credit the campaign on that number.

A poster QR or a guest-list export cannot tell a real attendee from a forwarded code. Brands still pay and report as if those scans were visits.

How this runs

From the door to a result you can use

Step 1

Set the event

Venue, window, and a live check-in at the door — not a static code on the poster.

Step 2

Confirm on site

The guest scans a short-lived challenge and confirms. Email is enough.

Step 3

See who passed

Partner ops get verified visits instead of an inflated scan count.

Step 4

Credit the campaign

That list is what you report, settle, or send to the next system.

The campaign is credited on verified visits, not on scans that left the room.

The unit of measurement is a visit

If finance asks what the number means, the answer is “people who confirmed at the source,” not “codes that were scanned somewhere.”

The next system can use the same fact

A partner app can ask whether this person checked in before it issues a reward or a second ticket.

You do not need their raw location trail

The useful output is the verification result. You do not have to ingest GPS tracks to make the campaign honest.

What the business gets

You get a list of verified visits you can report, invoice against, or send to a reward or access product. A screenshot from the group chat does not count.