Works with your stack
Cookie consent for Ticketack
PostHog after a yes
Ticketack sells tickets from your WordPress site. Its plugin starts PostHog on your pages by default, with Ticketack’s own project key, and can also load Plausible from Ticketack’s own server. Cookie Rocks holds both until the visitor accepts statistics.
By Ticketack · ticketack.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
What matters for consent with Ticketack
PostHog by default
The plugin’s head script starts PostHog with Ticketack’s key and eu.i.posthog.com. It records page views, page leaves and page speed, without session recording, and removes query strings from the addresses it sends. A switch in Ticketack’s own back office turns it off; it is on by default. Ticketack skips it on a local test address.
A second copy for you
If you add your own PostHog key in Ticketack, the same events also go to your PostHog project.
It already waits for consent tools
When the WP Consent API or CookieYes is present, Ticketack waits for statistics consent before starting PostHog, and starts it when consent changes. With no consent tool, it starts at once.
A second script: Plausible
When your ticketing engine runs on a ticketack.com address, the plugin also loads Plausible from Ticketack’s own server, analytics.netoxygen.ch, with no consent check. It sets no cookie and stores nothing, but each page view goes to that server. Ticketack measures there for its own account, so it needs the visitor’s consent for statistics like any other analytics.
Stored in the browser
PostHog keeps its state in a cookie and in local storage. Ticketack adds tkt_ph_instance_group in session storage, to remember the Ticketack instance the events belong to.
Who receives the data
Net Oxygen Sàrl, the Swiss company behind Ticketack, receives the PostHog and Plausible data sent with its own keys, as an independent controller. If you add your own PostHog key in Ticketack, you are responsible for that copy.
Cookie Rocks today
In our test, Cookie Rocks held PostHog before the choice and after Reject all: no request to PostHog and no ph_ cookie or key. Since Cookie Rocks 2.11.9 it also holds Ticketack’s Plausible script from analytics.netoxygen.ch: nothing reached that server before the choice or after Reject all. After Accept all, both started without a reload, and the ticketing page kept working. Its scan names Ticketack as the source of tkt_ph_instance_group and proposes statistics.
What our tests found on Ticketack
Before the choice · TicketackCookie Rocks holds Ticketack's Plausible until statistics consent
Plausible from analytics.netoxygen.ch now waits for statistics consent.
Seen in our tests, 18 November 2026, Ticketack 2.115.1.
Full detail
Cookie Rocks 2.11.9 recognises the Plausible script that Ticketack loads from analytics.netoxygen.ch and holds it: nothing reached that server before the choice or after Reject all, and the script loaded and sent its page view after Accept all, without a reload. It is never covered by the exempt audience measurement option, because Net Oxygen measures for its own account. The ticketing page still rendered.
Before the choice · TicketackCookie Rocks holds the PostHog analytics that Ticketack starts by default
by default: on
PostHog waits for statistics consent; Ticketack also reads the WP Consent API.
Seen in our tests, 17 November 2026, Ticketack 2.115.1.
Full detail
Ticketack starts PostHog on public pages by default, with Ticketack's own project key, sending events to eu.i.posthog.com and setting a ph_ cookie for a year. With Cookie Rocks 2.11.8, nothing reached PostHog and no ph_ cookie or key was set before the choice or after Reject all; after Accept all, PostHog started without a reload. Ticketack also waits for statistics consent on its own when the WP Consent API or CookieYes is active.
Bookings, events and courses
Other plugins of the same kind.
Questions
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Ticketack sites
Ticket sales, statistics after a yes.
PostHog after a yes
Every feature of the complete plugin for 30 days, no card. Ticketack keeps working as it does today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support

Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.