See who actually showed up, in Slate
When someone checks in at your event, Guidebook marks their Slate registration Attended, with the time they arrived.

Send app engagement back to Slate
For students who opt in, downloads, schedule adds, views, and form responses land on their event registration every hour.

Build the campus event once in Slate
Link a Slate folder to a guide. Every event becomes a session, and registrants are added automatically.

Slate profiles, in the campus app
Match each student's Slate record to their Guidebook account, so college, major, and orientation details stay current on every sync.

Campus apps by department
Admissions, orientation, student life, and more — one campus app that works across departments.

Build unlimited event apps on one license
One partnership for unlimited campus events — orientation, tours, student life, and everything in between.

Compare event app platforms
See how Guidebook stacks up against other event app and registration platforms.

Event apps for nonprofit and community programs
Give members, volunteers, and donors one branded app for conferences, fundraisers, and year-round community.

Campus integrations and an open API
Connect Guidebook with the campus systems, APIs, and tools your team already uses.

Event apps for corporate and enterprise teams
Internal meetings, offsites, and large-scale corporate events — with the branding and control enterprise teams need.

Create a branded event app with no coding
Put schedules, maps, resources, and updates in every attendee's pocket — built for campus events and programs.

Launch a branded, white-label event app
A white-label event app with your branding, your content, and your attendee experience — no coding required.

Everything in the Guidebook platform
Explore the features event teams use to engage attendees before, during, and after the event.

One app for in-person and virtual attendees
The same schedule, networking, and updates whether people are in the room or joining remotely.

Event apps built for associations
Annual meetings, chapter events, and member engagement — without rebuilding a new app every year.

A branded event website that matches the app
Promote the event, collect interest, and keep branding consistent from the first click to check-in.

Plan, run, and measure events on one platform
App, registration, badges, and websites in one workflow — so planning isn't a pile of disconnected tools.

Keep members engaged between events
One branded app for the conference and everything that happens the other 51 weeks of the year.

The conference app attendees actually use
Schedules, maps, networking, and live updates for annual meetings, summits, and multi-day conferences.

Registration that feeds your app and badges
Collect registrations, payments, and attendee data in the same platform as your event app.

Design and print event badges in one place
Custom badges, QR check-in, and on-site printing — without a separate badge vendor.

A Smaller School?
Deliver a polished, branded event experience without a large team or a big budget.

Running Family Programs?
Give families everything they need, from schedules and maps to real-time updates, all in one place.

Coordinating Move-In Day?
Share updates, manage events, and keep students informed from move-in through the academic year.

Offering Campus Tours?
Deliver branded, self-guided tour experiences with interactive maps and rich media, available 24/7.

Organising a Career Fair?
Simplify logistics for students, employers, and Career Services staff with one easy-to-use app.

Managing Alumni Events?
Plan reunions, regional events, and fundraising campaigns with an app built for alumni engagement.

Boost Student Engagement
One hub for schedules, resources, and events that keeps students connected throughout the academic year.

Planning Orientation?
Help new students feel prepared from day one with schedules, campus resources, and real-time updates in one app.

Running Admissions Events?
Manage open houses, tours, and yield events with a branded app that saves time and engages prospective students.

Get a custom Sponsorship Package Template
Stop starting from scratch. Grab free templates that helWe'll build a tailored sponsorship package with suggested pricing, tiers, and benefits..for your specific event.p you build professional sponsorship packages and close deals faster.

Plan Your Next Event Without Missing a Beat.
From venue selection to post-event wrap-up, this free checklist walks you through every step (so nothing falls through the cracks).

Real Results From Real Events
100,000+ organizations trust Guidebook. See exactly how universities, associations, enterprises, and more put it to work.

Flexible pricing for every event size
Find the perfect plan for your needs, from intimate gatherings to large-scale conferences.

Join our event experts
Watch on-demand webinars and join live sessions with industry leaders sharing best practices for event success.

Guidebook in Action
Book a personalized walkthrough and discover how we help event teams create better attendee experiences.

See Who Actually Showed Up, in Slate

See Who Actually Showed Up, in Slate
- When someone checks in at your event or session, their Slate registration for that event is marked Attended, with the time they checked in.
- Every check-in method counts: email entry, badge scan, attendee self check-in, and check-ins from the Guidebook mobile app.
- Checking someone into a session also marks them attended for the overall event, so event-level turnout stays complete.
- You choose which guides send attendance back, and it's only sent for attendees who have agreed to share their data.
Your Slate report tells you how many people registered for Admitted Student Day. It can't tell you how many walked through the door. So someone exports the check-in list, someone else matches it against registrations, and a week later you have a rough answer to a question you needed on Monday.
Attendance Data closes that gap. When someone checks in at your event or session in Guidebook, their Slate registration for that event is marked Attended, along with the time they checked in. Registered is a plan. Attended is a fact. Now your Slate record holds both.

What is the Guidebook and Slate attendance data connection?
It's the part of the Guidebook and Slate integration that sends check-ins from Guidebook back to Slate. When a registrant checks in at an event or session, Guidebook marks their Slate registration as Attended and records the time. Turnout then lives on the student record, next to everything else your team already tracks. It's free to use.
The loop, finally closed
The integration moves information both ways. Events and sessions brings your Slate events and registrations into Guidebook, so every registrant lands in the right guide with the right sessions. Attendance Data sends the other half back. Attendance is written to the same registrations that came from Slate, so there's no matching step and no spreadsheet in between. The registration Slate created is the registration Guidebook updates.

Every way people check in, counted
Your team checks people in differently depending on the event, and all of it reaches Slate:
- An attendance manager adds the attendee by email in Builder
- An attendance manager scans the attendee's QR badge in Builder
- The attendee scans the event's QR code and enters their email to check themselves in
- An attendance manager checks people in from the Guidebook mobile app, by scanning a badge, entering an email, or picking them from the list
Campus events don't happen at a desk, so someone with a phone at the door of a residence hall counts the same as a badge scan in the main hall. Checking someone into a session also marks them attended for the overall event, so a student who skips the welcome table and turns up at a major-specific breakout still counts.

What this changes on Monday
With attendance in Slate, you can see turnout for each event and each session, and follow up with the registrants who didn't show. The no-show list is the useful one. A student who registered for a yield event and never arrived is a different outreach problem than one who never registered at all, and until now those two looked similar in your data. Attendance behaves like any other part of the student record, so it works in queries, communications, and reporting.
What you control
You choose which guides send attendance back, and attendance is only sent for attendees who have agreed to share their data. Because attendance is written onto Slate registrations, it only works for guides connected to events and sessions synced from Slate. The person records connection and the events and sessions connection both need to be in place first, on the same instance. One expectation to set: this isn't a live counter. For real-time numbers during an event, use the Attendance tab in Builder.
You already know how to capture attendance in Guidebook, whether that's session verification or self check-in. Attendance Data is what happens after the doors close, when the question stops being how many came and starts being who to call next.
[faq]
Q: Do we need the other Slate connections first?
A: Yes. Attendance is written onto the Slate registrations that came into Guidebook through the events and sessions connection, so that connection and the person data connection both need to be set up first, on the same Slate instance. Without them there's no registration to mark as attended. If you're setting the integration up from scratch, the order is person records, then events and sessions, then attendance data.
Q: What exactly gets sent to Slate?
A: The registration for that event is marked Attended, along with the time the person checked in. It lands on the registration that Slate already created, so there's no separate record to reconcile and no matching step on your side. From there it behaves like any other field on the student record, which means you can use it in queries, communications, and reporting the same way you use everything else.
Q: Does it matter how someone checks in?
A: No. An attendance manager can add someone by email in Builder, scan their QR badge in Builder, or check people in from the Guidebook mobile app by scanning a badge, entering an email, or picking them from a list. Attendees can also scan the event's QR code and enter their email to check themselves in. Every one of those methods is sent back to Slate.
Q: If someone only checks in to one session, do they count as attending the event?
A: Yes. Checking someone into a session marks them as attended for the overall event too, so your event-level turnout stays complete even when a student only gets scanned once. This matters on campus days where people arrive late or skip the welcome table and go straight to a breakout that's relevant to their major.
Q: Is attendance sent to Slate in real time?
A: No. Guidebook pushes attendance to your Slate web service regularly rather than instantly, so treat it as data for follow-up rather than a live counter. If you need real-time numbers while an event is running, for example to see whether a session is filling up, use the Attendance tab in Builder. The Slate data is there for the outreach and reporting you do afterward.
Q: Can we choose which guides send attendance back?
A: Yes. As the administrator, you select which guides export attendance data, so you can switch it on for your admissions and yield events and leave it off elsewhere. Attendance is also only sent for attendees who have agreed to share their data, so a student who hasn't consented is never included regardless of which guides you've enabled.
[/faq]
Get the Mobile App Playbook
A short guide to running the whole student journey in one app. No fluff, just what works.
%20(1).avif)




.avif)
