Questions about what Tally records.

Tally separates qualifying attendance from recorded invitation credit. Check-ins, tickets, clicks, RSVPs and door counts answer different questions. Neither attendance verification nor a credited invitation establishes causal lift.

A fan uses the supported event check-in path with the required permission. The named policy decides whether its evidence qualifies. Additional door, ticket or provider connections require separate qualification.

Check-in evidence and permitted location signals support attendance records. Aggregate program reports and authorized host views have different scopes. Hosts may receive profile or home-city fields subject to fan visibility settings; review the Privacy Policy for those boundaries.

Sponsor proposals scope aggregate campaign reporting, not individual fan access. Agree suppression, purpose and recipient permissions before launch. The Privacy Policy describes other authorized disclosures and applicable choices; aggregation alone is not an anonymity guarantee.

Agree the supported check-in path and fallback with the venue before launch. A QR path can reduce new hardware needs, but policy, accessibility, staffing and additional integrations determine the actual door process.

Availability depends on the supported release, role, event and program. Contact support@tally.vip about a specific city or venue before planning a launch; this page does not establish an active local program.

Pricing depends on how an artist, venue, promoter, or sponsor uses Tally, and sponsored campaign funding is separate from platform use. There is no public price list. Contact the team to discuss which surfaces apply to your situation.

Artists and promoters can open the Tally portal or download the app to set up a first event and distribute attributable invitations. Venues and sponsors usually start with a conversation, because setup depends on existing ticketing and campaign arrangements.