Sample data requirements for testing and demonstration.

Before the event goes live, you need realistic sample data to verify that every feature works correctly and to capture meaningful screenshots. This guide lists the minimum data needed for each area of the app.

User Data

You need a representative set of users across all roles to test role-based features and populate lists.

  • Attendees: At least 10 registered attendees with complete profiles (name, email, company, job title, bio, profile photo)
  • Speakers: At least 3 speakers with assigned sessions
  • Exhibitors: At least 3 exhibitor team members associated with exhibitor records
  • Admin: At least 1 admin account with full access
  • All test users should have profile photos uploaded for realistic screenshots

Agenda Sessions

A populated agenda is critical for testing personalized filtering, RSVP, and check-in.

  • At least 10 sessions across multiple days and time blocks
  • Sessions should have assigned speakers, locations, tracks, and descriptions
  • At least 2 sessions should be marked as optional with group-based access
  • At least 1 session should have check-in enabled
  • Session capacity should be set on at least 2 sessions for RSVP testing

Exhibitors

Exhibitor data drives the directory, bingo, and networking features.

  • At least 5 exhibitor records with company details, booth locations, and team members
  • At least 3 exhibitors should have bingo participation enabled
  • Each exhibitor should have a designated chat contact
  • At least 1 exhibitor should have exhibitor admin rights assigned

Meetings

Meeting data tests the booking, availability, and notification systems.

  • At least 3 meeting time slots configured across event days
  • At least 2 booked meetings with different statuses (pending, accepted)
  • At least 1 meeting booking between an attendee and an exhibitor

Gamification

Award and scavenger hunt data must exist before those features show meaningful content.

  • At least 4 award definitions with icons, colors, and trigger configurations
  • At least 2 users with gamification progress (scores, achievements)
  • At least 4 scavenger hunt questions with answers and item numbers
  • At least 2 scavenger hunt progress records for the test user

Bingo

Exhibitor bingo needs progress data to show the tracking and leaderboard features.

  • Bingo qualification threshold set (e.g., scan 3 of 5 exhibitors)
  • At least 3 attendees with bingo scan progress
  • At least 1 prize draw winner recorded

Social and Engagement

Social features need content to look populated and functional.

  • At least 5 social wall posts with images and captions
  • At least 2 discussion threads with replies
  • At least 3 poll submissions across different questions

Notes

Notes data tests the cross-entity association and export features.

  • At least 3 notes associated with different entity types (person, session, exhibitor)
  • At least 1 lead capture note for exhibitor team testing

Feedback

Feedback data is needed for admin results screens.

  • At least 5 event feedback submissions
  • At least 3 session survey submissions for different sessions

Communications

Communication history shows the admin dashboard.

  • At least 2 sent communications in the history

Content

Static content screens need current information.

  • At least 2 event information pages with descriptions and images
  • At least 3 documents uploaded to the document library
  • At least 5 news feed articles
  • Floor plan image with at least 3 room markers and 2 exhibitor booth markers

Search Embeddings

Universal search requires pre-computed embeddings to return results.

  • Embeddings must be generated (or regenerated) after all content data is populated
  • Use the admin-only Regenerate Embeddings button on the Universal Search screen
Was this article helpful?
YesNo