Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

The marketer view on mobile

The mobile app has a second experience alongside the standard rep view — the marketer view — pitched at whoever owns the event's outcomes rather than whoever is at the booth capturing leads. It's a monitoring surface: how the event is tracking against its goal, which reps are producing, what qualifier answers are landing, and what tasks are open.

The marketer view is in beta. Available on select orgs today as part of the Attribution feature set, and the cards + drill-downs are still evolving based on customer feedback. If you don't see the marketer view when you sign in, contact your CSM about enabling it — and if a metric feels off or you want a specific view added, that feedback loops through your CSM directly into the roadmap.

Who sees it

The marketer view is a persona, not a role — the app decides which experience to show based on who you are:

  • Org admins default into the marketer view when the feature is on for your org.

  • Super admins (Mobly staff looking at another org) land in the rep app and switch deliberately.

  • Client users never see the marketer view.

If you're an admin on a marketer-enabled org, the app opens straight into the marketer tabs on sign-in — no toggle to hunt for. A first-run walkthrough introduces the view the first time you land, so even if you've only used the rep app before, you'll get oriented.

What's on Home

Home is a four-card dashboard. Each card is a live read on the event you're currently working in — pulled from the same data the Hub's Post-Event tab uses, just paced for a marketer checking the app between meetings.

Goal progress

How the event is tracking against its goal — specifically, unique leads captured at the event via mobile device. That's the on-floor number: each unique person a rep captured with the mobile app counts once, regardless of how many times they were scanned. CSV uploads, registration imports, and API uploads are intentionally excluded — this card is a read on booth performance, not total lead volume from every source.

Two more reads sit alongside the count:

  • Enrichment standing — how many of those on-floor captures Mobly has enriched

  • CRM standing — how many have synced cleanly to your CRM

Three lenses on the same funnel — captured, enriched, synced — so you can see where things are stuck without opening the Hub.

Top three reps

The three highest-producing reps at this event by capture count. Tap a rep to open their rep detail, which includes:

  • An hourly chart of their captures across the event

  • Their recent leads (with drill-in to lead detail)

  • Their enrichment and CRM numbers — same funnel view scoped to that rep's captures

Useful for spotting who to check on mid-event (a normally-strong rep with a slow morning) and for the post-event debrief.

Event qualifiers

A rollup of how leads answered the event's qualifiers — the same distribution view you'd see in the Hub's Post-Event Qualifiers panel, sized for phone.

Open tasks

The event's open tasks, with a preview of the top few. Task completion is reversible from here — tap to complete, tap again to un-complete. Completed tasks stay visible in the preview so the tap has visible effect rather than tasks disappearing on you.

Shared with the rep app

Leads, Tasks, and Team screens are shared between the two views — they behave the same regardless of which persona you're on. That means if you're an admin who also wants to scan a lead in person, you can switch to the rep app and back without learning a second set of interactions.

Note

The Team card falls back to a device-local reading if the server can't be reached (offline, spotty conference WiFi), showing a live count from what's already on the phone. Cached remote readings carry an "as of" timestamp; local-only counts don't, since there's no fetch time to report.

Related articles

PreviousSharing your business card (My Card)
NextEngaging with leads

Last updated

Was this helpful?