Skip to content
TicketCounts.io
Log inStart free

How it works

How TicketCounts.io works

Connect Eventbrite or Universe, pick the show, add recipients and choose a schedule. At each send TicketCounts.io reads the current count from the platform and emails every recipient their own copy.

Last updated

The four steps

  1. Step 1: Connect Eventbrite or Universe

    Choose Connect in your dashboard and sign in on the platform's own page (OAuth). TicketCounts.io stores the access token encrypted and only reads data; it never creates or edits events, orders or ticket types. You can connect more than one account per platform.

  2. Step 2: Pick the show

    Pick the organization (Eventbrite) or host (Universe), then search its events by name. Unlike Eventbrite's own scheduled reports (only events in the next 3 months, as of September 18, 2026), there is no date window: a show on sale for next spring can get a report today. One report covers one event.

    Eventbrite scheduled reports compared

  3. Step 3: Add recipients and a schedule

    Add up to 2 recipients on Free and up to 100 on the largest plan. Recipients do not need an account. Pick daily, one weekday or several weekdays, a time in 15-minute steps and the time zone the report follows.

  4. Step 4: The count goes out

    At the scheduled time TicketCounts.io reads the current count from the platform and emails each recipient their own copy, with your logo on paid plans. Send yourself a test first if you like. If the platform does not answer, no email goes out and the send is retried.

What access does TicketCounts.io get?

You approve access on the platform’s own sign-in page (OAuth), so TicketCounts.io never sees your password. It only reads: the connected account, your events and the tickets sold for them. It never reads attendee or buyer details and never changes your events. What each approval allows differs by platform, as shown below.

Eventbrite

Eventbrite OAuth: you sign in on eventbrite.com and approve TicketCounts.io. TicketCounts.io never sees your Eventbrite password.

OAuth scope

Eventbrite does not offer narrower OAuth scopes, so the approval lets the app call the Eventbrite API as your user. TicketCounts.io only sends read requests (GET) and never creates or edits events, orders or ticket types.

What it reads

  • Your Eventbrite user id and email, to identify the connected account
  • The organizations you belong to, to list their events
  • Live and started events: name, dates, time zone, venue name, URL and status
  • Each event's ticket classes: name, price type (free or paid), category, quantity sold and quantity available
  • The event's capacity tier (total capacity), when set

What it never reads

  • Attendee or buyer names, emails or answers
  • Orders and payment details
  • Payouts and financial reports

Tokens and disconnecting

Eventbrite tokens do not expire. Disconnecting in TicketCounts.io deletes the stored token and pauses that account's reports. Stored tokens are encrypted (AES-256-GCM).

Universe (a Ticketmaster company)

Universe OAuth: you sign in on universe.com and approve TicketCounts.io. TicketCounts.io never sees your Universe password.

OAuth scope

TicketCounts.io requests Universe's public OAuth scope and only runs GraphQL queries (reads); it never runs mutations that change your events.

What it reads

  • Your Universe viewer id, name and email, to identify the connected account
  • The hosts you own or belong to, to list their events
  • Posted events: name, dates, venue and status
  • Each event's rates (ticket types): price, sold count, capacity and type

What it never reads

  • Attendee or buyer names, emails or answers
  • Orders and payment details

Tokens and disconnecting

Universe access tokens expire; TicketCounts.io refreshes them automatically before they do. Disconnecting revokes the token with Universe and pauses that account's reports. Stored tokens are encrypted (AES-256-GCM).

Security and data access

When can reports go out?

Daily, on one weekday, or on the weekdays you pick, at a time in 15-minute steps, in the time zone you choose. A 9:00 AM report stays at 9:00 AM local time when the clocks change. Each report keeps its own schedule and time zone.

Schedule options
ScheduleWhat it does
DailyEvery day at the time you set.
WeeklyOne weekday, for example every Monday.
Custom daysAny set of weekdays, for example Monday, Wednesday and Friday.
Send time
Any time of day in 15-minute steps, from 12:00 AM to 11:45 PM.
Time zone
Each report follows its own time zone, so a report for a show in another city can go out on that city’s morning.
Clock changes
When clocks spring forward past your send time, the report goes out after the jump (2:30 AM becomes 3:30 AM). When an hour repeats, it goes out the first time.
Pausing and resuming
Pause a report any time. When you resume it, the next send is the next scheduled time; missed sends are not caught up.

What happens at each send?

At the scheduled time the count is read fresh from the platform and one email goes to each recipient. If something fails, the send is retried after 5, 20 and 60 minutes; after 3 failed sends in a row the report pauses and you get a notification.

  • The count is read fresh

    At the scheduled time the current count is read from the platform. A report never reuses an older count or fills in a number.

  • One copy per recipient

    Each recipient gets their own email with an unsubscribe link. Addresses that unsubscribed, hard-bounced or marked a report as spam are skipped.

  • Retries when something fails

    If the platform or the email service does not answer, the send is retried after 5, 20 and 60 minutes. A report that fails 3 sends in a row pauses and you get a notification.

  • Late sends are skipped

    If a send is more than 6 hours late, for example after an outage, it is skipped instead of arriving hours after the time you set. The next one goes out on schedule.

  • Ended shows pause themselves

    When the platform marks the event as ended or canceled, its report pauses and you get a notification. Paused reports do not count toward your plan.

  • Reconnect prompts

    If a platform stops accepting the connection, that account’s reports pause and you are told to reconnect. Reconnecting the same account resumes them.

Can I see a report before it goes to anyone?

Yes. Once an account is connected, send a test from the report form to your own verified address or to the report’s saved recipients. It uses the live count, and its subject starts with [TEST], so nobody mistakes it for a scheduled report.

See a sample report

Questions

How often can reports be sent?

Daily, on one weekday, or on the weekdays you pick, at the time you choose in 15-minute steps and in your own time zone. Reports for an event that has ended or been canceled pause on their own.

Can I connect more than one Eventbrite or Universe account?

Yes. You can connect several accounts on each platform and choose which account and event each report uses.

Do recipients need an account?

No. Recipients just get the email. Each one receives their own copy, so nobody sees the other addresses. Every email has an unsubscribe link, and mail apps that support it show a one-click unsubscribe button. Free allows up to 2, Starter allows up to 10, Pro allows up to 25 and Venue allows up to 100 recipients per report.

What access does TicketCounts.io get to my ticketing account?

You connect with the platform's own sign-in (OAuth), so TicketCounts.io never sees your password. It reads only what reports need: which account you connected, your events and the ticket types sold for them. It does not read attendee or buyer details and never edits your events. Stored access tokens are encrypted, and you can disconnect at any time.

Security and data access

Set the schedule once. The count goes out on its own.

Free for 1 active event report. New accounts get 14 days of Pro, no card needed.

Start freeSee pricing