Exporting Event Data & Token Usage

Created by Atul Todi, Modified on Thu, 21 Aug, 2025 at 7:31 PM by Atul Todi

WHR lets you export event data when needed — from Trackers, Coordinate, or through Custom Requests. Exports are powered by tokens and organized in data stacks. While export is available, WHR works best when you use the platform directly for research, tracking, and coordination.

How Export Works

Export Sources

Trackers – Export all events in a tracker or only new ones since your last export.
Coordinate – Export shortlisted events with notes, status, and team inputs.
Custom Requests – Request exports with specific fields (always token-based).

Stacks & Tokens

Exports are grouped into mandatory + optional stacks: (see table below for fields)

Basic (mandatory)
Advance Intel
Audience Intel
Event Contact
Organiser Contact

Choosing 1 stack = 1 token per record.
Choosing all 5 stacks = 5 tokens per record.
If a selected stack has no data for a record, tokens for that stack are not charged.

Company / People Data

Company and People data exports are separate. Each has its own token structure (covered in separate articles). They include detail fields for respective entities/

Available	Data Stack	Comment	Availability
Format	basic intel	Event type, such as - tradeshow, conference, meetup	mandatory
Location	basic intel	city, country	mandatory
Status	basic intel	active, cancelled, postponed	mandatory
Category	basic intel	Industry event belongs to	mandatory
Date	basic intel	Event date	mandatory
Event Name	basic intel	Cleaned name of the event	mandatory
Estimated Visitors (range)	audience intel	Event attendance refers to the number of people who are predicted or estimated to attend an event.	mandatory
Maturity - (regularity)	advance intel	Event Maturity refers to the lifecycle stage of an event, based on how often it has occurred (e.g: new, growing, established, flagship)	mandatory
Audience Zone	audience intel	audience tag- local, national, international	mandatory (as available)
Event Description	advance intel	Short 'about' section about the event	mandatory (as available)
Event Point of contact name	Contact	name of active POC	mandatory (as available)
Event Point of Contact (email)	Contact	Email of event active POC	mandatory (as available)
Event Website	Contact	Event website url	mandatory (as available)
Organiser Name	Org Info	Name of the event host	mandatory (as available)
Organiser Website	Org Info	Organiser website url	mandatory (as available)
Venue	basic intel	Name of the venue where the event is happening	mandatory (TBA if not announced)
Venue Location	basic intel	Name, Address and lat-long	mandatory if venue available
Inbound Score	audience intel	Represents the number of attendees traveling to the event from other cities within the same country	where available
International Score	audience intel	Represents the number of attendees traveling to the event from outside the domestic country.	where available
User Rating	audience intel	User rating on 10Times	where available
Estimated Exhibitor count	audience intel	Estimated Exhibitors refers to the projected number of exhibitors that will participate in an event	where available
Forecasted date	advance intel	predicted future date (for events without upcoming yet)	where available
Edition	advance intel	number of editions covered on 10Times	where available
Frequency	advance intel	annual, bi-annual, etc	where available
Event Point of Contact (phone)	Contact	Phone of event active POC	where available

Steps to Export

Go to your Tracker or Coordinate list.
Click Export.
Choose export type:
- Export all data
- Export only new since last download
Select stacks you need.
- Basic is always included
- Add any other stacks as required
Confirm export.
- Token usage is shown before confirmation
- Download link will be available in your export history

Tips & Best Practices

Use Trackers to avoid repeated bulk exports — they refresh automatically.
Export only the stacks you need to minimize token usage.
For large requests (100k+ tokens), contact help@whr.ai.
If you need custom fields not in the standard stacks, request a Custom Export (token-based pricing applies).
Exports include only data available; unavailable fields won’t cost tokens.
Past exports are stored for convenience — you can always re-download.
API access supports incremental pulls (“only new since last call”) and is documented separately.
Note: If you need to export more than 100K entries, talk to us
Refer to T&C to ensure you adhere to platform policy and what you can do/not-do with the data