Numbers you can act on and defend.
First-party collector
Map opens, place views, searches, route requests, favourites, banner clicks and scans. Collected by the platform and stored for you, not rented back.
Attribution built in
QR codes and UTM links are generated inside Indavro, so every scan and click is tied to a campaign from the start.
Content demand
What people searched for and did not find is your content to-do list for next year.
Engagement by place
Which zones, stages and vendors drew attention, and when during the day.
Sponsor and vendor recaps
Exportable reports with impressions, profile views, offers and route-to-booth requests, per sponsor and per vendor.
Privacy by design
Consent-aware. No passive precise location tracking. Aggregated by default, with controls per event.
GA4 and Meta forwarding
Forward events to your own tags when you want to. Indavro stays the source of truth either way.
Year over year
The data stays with the event. Compare this edition to the last one and see what changed.
Which campaign brought them here?
Generate a QR code for the poster, a link for the Instagram story and another for the ticket-holder email. Each one carries its campaign through to the map, so you can see which channel brought people in and what they did once they arrived.
- QR generator and UTM builder inside the console
- Per-link attribution on the map
- Campaign reports for the marketing team
A recap your sponsor's marketing lead will accept.
Placement impressions, profile views, taps, route-to-booth requests and offer redemptions, per sponsor. Export it the week after the event. It is the document that starts the renewal conversation.
- Per-sponsor and per-vendor
- Exportable
- Built from first-party data
Why we don't headline attendance.
Attendance estimates are a sensitive number for public events. A single figure can change permit requirements, policing costs and insurance for the producer, and estimates from phones are rough at best.
Indavro leads with engagement and attribution instead: what people looked for, where they went, what they saved, which campaign brought them. Those are numbers you can act on, and numbers you can defend in a council meeting or a sponsor review.
What we collect, and what we don't.
What is collected
Interactions with the guide: map opens, taps on places, searches, route requests, favourites, banner views and clicks, QR scans and campaign parameters.
What is not collected
Continuous or precise location. The guide does not track where a phone is in the background. Route requests record an origin and destination the attendee chose.
Who owns it
The organizer. Data is isolated per organization at the database level and stays available after the event.
Consent and controls
Consent-aware collection, aggregation by default, and per-event switches for third-party forwarding.