Show session offers after the session starts

You can now time an offer, freebie or giveaway banner from a session's scheduled start as well as its end. Show it at the opening or a chosen number of minutes into the session.

In Marketing > Offers & Giveaways, edit a perk and open Visibility > Session promotion. Select the sessions, choose After the session starts, and enter the minutes. Enter 0 to reveal the banner at the scheduled start.

Timing follows the scheduled clock, rather than each attendee's video playback. Existing promotions keep their previous end-based timing.

See how to set up session promotions.

Choose whether blog posts show publication dates

You can now choose whether your event blog posts show their publication dates.

Open Blog Settings from Event Settings → Branding and Site Settings, or from the Blog Posts settings sidebar, and turn off Show publication dates when you want to use blog posts for evergreen event content or topic pages.

The setting updates blog cards and individual post pages while keeping your posts, ordering, and RSS feed intact.

Match Stripe payments to event orders

Stripe ticket payments now include details from the HeySummit order, so you can identify the event, attendee and purchased tickets while reviewing payments in Stripe.

Open a payment in your connected Stripe account and look for the HeySummit metadata. It includes order and ticket information, plus any applied coupon. Recurring charges include details of the individual ticket being charged.

No extra setup is needed. The details are added to new payments; older payments are not backfilled automatically.

Collect poll responses during replays

Replay viewers can now answer polls that ran during your broadcast. Results combine live and replay answers, with a Live/Replay breakdown available through Combined.

Open Audience Tools > Polls from your event dashboard and turn on Allow replay responses? when creating or editing a poll. You can change it later in Poll details and results, including after live voting closes.

Replay responses are optional and off by default. Each viewer has one hour from their first replay visit to respond, and one answer per person across live and replay. Only polls activated during the session being replayed are eligible. Closing live voting does not stop replay responses; disable replay acceptance separately.

Live poll response time can now be set up to 24 hours. Scheduled polls remain capped at the time left in the session. See the polling guide.

Restrict each integration to the events and permissions it needs

You can now create a separate API key for each integration and choose exactly which events and actions it can access. Give a reporting tool read access to one event, or let another integration update the records it needs, without sharing the same unrestricted key everywhere.

Open API keys in your account dashboard to create a named key, select its events and permissions, or rotate or revoke access. New MCP OAuth connections also let you choose event access when you authorize an AI assistant. Your existing HeySummit permissions and active paid-plan requirement still apply.

Restricted keys work with API v2 event endpoints and MCP. Keep your existing unrestricted token for legacy API, Zapier and account-wide webhook integrations.

Learn how to manage API keys and integration access.

See ticket prices on session pages

When a session has exactly one eligible ticket available to buy, its page now automatically shows the ticket and its current price. Visitors can see the cost before they click through to checkout, and organisers do not need to select that ticket manually.

If you have already chosen a Registration CTA Ticket for the session, HeySummit continues to use your choice. When several tickets qualify, the session page does not automatically choose one.

The automatic display follows your ticket access rules, sale dates and capacity limits. It does not add a ticket offer to Open Access or Public Access sessions.

Re-order sponsorship packages

You can now choose the order your sponsorship packages appear in HeySummit. Open Revenue → Sponsor Packages and drag packages into the order you want.

That order is reflected on your public sponsor package list and application page. Existing events keep their current price order until you reorder the packages.

Filter and export your event analytics

Choose the dates you want to report on and take your event analytics into a spreadsheet.

In Registration & Attendees > Attendee Insights, use a preset such as Last 7 days or Last 30 days, or select your own start and end dates. The reports update to match your selection.

Select Export CSV to download the report data for that period. The export includes the date range and reporting timezone, so you can share the results with your team or use them in your own reporting.

See which campaigns drive event traffic

Compare traffic from presenter links, affiliates and UTM campaigns in Registration & Attendees > Attendee Insights. Switch each report between Visitors and Page views to see which sources bring browsers to your event website and how much activity they generate.

You can also choose presenter referrals, affiliate referrals or UTM campaigns in Home > Analytics > Traffic insights, then open the detailed reports with View audience insights.

The new reports collect traffic from when tracking became available, so they do not include earlier visits. They measure website traffic and leave attendee attribution and affiliate commission unchanged.

Learn how to interpret the reports: Understand referral and campaign traffic in Attendee Insights.

Automatic IndexNow updates for event page changes

HeySummit now automatically notifies IndexNow when public event content changes, provided you have an IndexNow key configured in Event Settings.

This covers event pages and the public pages for sessions, presenters, topics, sponsors, stages, venues, blog posts, and Page Builder pages. New, updated, unpublished, deleted, and moved URLs are submitted in the background after changes are saved, with retry handling for temporary provider failures.

You can keep managing your key where it is today; no extra automation is needed.