Skip to content

Know which event created the conversation, while the memory is still useful.

Set up the event and who is working it. Every lead a rostered rep captures during the event’s hours is credited to it automatically, and a wrong one can be moved later, on the record.

What is event lead attribution?

Event lead attribution is how RareMachine records which trade show, conference or field event produced each lead. An admin creates the event with its dates, its time zone and a roster of the sales reps who will work it. From then on, every card scan, badge photo, voice note or typed entry that a rostered rep captures during the event’s hours is attributed to that event automatically, with no extra step for the rep. A capture made outside the window, or by someone who isn’t on the roster, stays unattributed instead of being guessed.

When two events overlap, the one that ends first wins, so the same capture always lands on the same event. The result is a lead count per event, a per-rep leaderboard and a capture list you can export, all calculated from RareMachine’s own records, without a single CRM query. Attribution is one step of the wider job; the guide to event lead capture covers the rest, from the booth to the CRM.

How does event attribution work?

Four steps, and only the first one is extra work.

  1. Create the event. Name it, set its start and end in the event’s own time zone, and add the sales reps working the stand to its roster. An admin can also let reps add themselves.
  2. Publish it. A scheduled event goes live at its start time on its own. Nobody has to remember to press Start on the morning of the show.
  3. Capture as usual. Reps scan cards and badges, send voice notes or type a lead on WhatsApp. Each capture inside the window is attributed to the event and picks up its shared tag, if it has one.
  4. Correct and follow up. A rep can move their own lead to the right event afterwards, and an admin can move anyone’s. Every move is audited. If you switch it on, each attributed lead also gets one WhatsApp invitation.

Built for the floor, not a CRM browser

Lead counts and the per-rep leaderboard come from RareMachine’s own capture records, so they keep working while your CRM connection is down.

An admin can let reps add themselves to the roster
Start, end and archive events without deleting history
Export the event’s captures as a CSV for follow-up

Every write is on the record

If the event has a shared tag, each lead picks it up the moment it is attributed. It reaches your CRM when someone syncs it, or automatically once an admin turns on auto-sync, and an automatic write is logged as auto-sync, never as a person’s approval.

Event hours run in the event’s own time zone; overlaps resolve the same way every time
Moving a lead to another event marks its earlier CRM tag as out of date
Tag edits made in your CRM never rewrite RareMachine’s event history

Questions about event attribution

Does a rep have to pick the event when they capture a lead?

No. If the rep is on the event’s roster and captures the lead during the event’s hours, RareMachine attributes it automatically. Nothing changes in how they capture.

What happens to a lead captured after the event ends?

It stays unattributed rather than being guessed. If the conversation really belongs to the event, the rep who captured it, or an admin, can attribute it afterwards, and the change is recorded in the audit log.

Which time zone does attribution use?

The event’s own. An event in Dubai keeps Dubai hours, even when a rep’s phone or the admin’s laptop is set to India time.

Do event results need a working CRM connection?

No. Lead counts, the per-rep leaderboard and the CSV export come from RareMachine’s own capture records, so they work while the CRM connection is down. A lead reaches the CRM when someone syncs it, or automatically once an admin turns on auto-sync.

Set up the event before the show. The attribution happens on the floor.