Skip to main content

Understand cookies used by HeySummit

Learn which cookies HeySummit uses for security, registration, preferences, attribution, and event analytics.

Written by Benjamin Dell

HeySummit uses first-party cookies to keep sessions secure, remember choices, complete registration and checkout, and understand how visitors reached an event. The exact cookies present can vary by page, sign-in state, and the features or integrations an event organiser enables.


​

Essential and functional cookies

  • sessionid keeps a signed-in HeySummit session active.

  • csrftoken helps protect forms and other requests from being submitted by another site.

  • heysummit_cookie_consent remembers whether the visitor accepted or rejected optional cookies. The choice lasts up to 60 days unless you clear the cookie earlier.

  • checkout_attendee, heysummit_attendee, and heysummit_coupon support registration, attendee access, and coupon handling where those features are used.


​

Attribution and analytics cookies

  • heysummit_utm_source, heysummit_utm_medium, heysummit_utm_campaign, and related referrer cookies record how a visitor reached HeySummit or an event when that information is available.

  • heysummit_ac and related campaign, speaker, sponsor, or referral values support attribution when a visitor follows a tracked link.

  • hs_visitor_id and piqo_visitor support visitor and signup attribution used by HeySummit analytics.


​

Cookies from event organisers and third parties

An event organiser can connect analytics, advertising pixels, chat, payment providers, video providers, and other third-party tools. Those services may set their own cookies, so the complete browser list can differ between events. Their cookies are governed by the provider's policy and the event organiser's configuration.


​

Control cookies in your browser

Where a HeySummit cookie banner is shown, accepting allows the configured analytics and helpdesk tracking scripts to load. Rejecting leaves essential site functions available, but does not delete cookies already stored. Some registration, referral and visitor-attribution cookies are set separately. Embedded services and organiser-added code can have their own cookie and consent controls. Use your browser settings to inspect, block or delete cookies. Blocking all cookies in the browser can prevent sign-in, registration, checkout, or attendee access from working correctly. For more detail about how HeySummit handles personal data, read the HeySummit Privacy Statement.

Did this answer your question?