You can inject your own CSS into the Eventify ticket page and use it to hide anything buyers don't need to see, such as the "Sale ends on Jan 31, 2027" label, the "12 left" stock badge or the footer links. Every part of the page carries a fixed class name, so one short CSS rule is enough to hide it.
The CSS runs inside the ticket page itself, so the change shows wherever the page appears: on its own link and inside the iframe embed on your website.
Where to find this: Event Dashboard > Registration > Registration Settings > Tracking Code
Registration > Registration Settings > Tracking Code. The same boxes are also under Tickets > Ticket Dashboard > Add Tracking Code. CSS here loads on every page of your event's ticket and registration portal: the ticket list, checkout, registration forms and the thank-you page.
Good for: hiding an item on every ticket and every page. This is the place to start.
Tickets > Manage Tickets > pencil icon on the ticket > step 5, Settings > Custom Code. CSS here loads only when a buyer opens that ticket's direct link, not on the full ticket list. See "How to inject CSS from a ticket" below.
Good for: changes that should only apply when you share one ticket's own link.
Registration > Registration Forms > open the form's settings > Custom Code. CSS here loads only on that registration form.
Good for: hiding fields or text on a single registration form.
<style>
.TICKET_END_DATE { display: none !important; }
</style>
.png)
Note: Always wrap CSS in <style> tags. A <link rel="stylesheet"> tag is skipped, so it has no effect. To load a CSS file from your own website, see "How to inject an external CSS file" below.
Each class name also exists with the ticket's code added to the end after an underscore. Add these rules to Tracking Code. To hide the sale end date only on the ticket whose code is 3F9A1C:
<style>
.TICKET_END_DATE_3F9A1C { display: none !important; }
</style>
To find a ticket's code, go to Tickets > Manage Tickets and open the ticket. The Ticket Code is shown on the ticket form. It is also the last part of the ticket's direct link, after /tickets/.
You can list several rules in one block. This hides the sale end date on every ticket and the tags on one ticket:
<style>
.TICKET_END_DATE { display: none !important; }
.TICKET_TAG_3F9A1C { display: none !important; }
</style>
Every ticket has its own Custom Code box. CSS you add there loads only when a buyer opens that ticket's direct link, the link that ends in /tickets/ followed by the ticket code. It does not load on the full ticket list, so other tickets and the list itself stay as they are.
<style>
.TICKET_END_DATE { display: none !important; }
</style>
Only one ticket shows on its own link, so plain class names are enough here. You don't need to add the ticket code to them.
Note: Ticket Custom Code loads only on that ticket's direct link. To hide something for one ticket on the full ticket list, add the rule to Tracking Code with the ticket code at the end of the class name, as shown in "Hide it for one ticket on the full ticket list".
If you'd rather keep your rules in a CSS file on your own website, inject the file instead of pasting the rules. You can then change the file at any time without opening Eventify.
eventify-tickets.css (on your website):
.TICKET_END_DATE { display: none !important; }
.TICKET_STOCK { display: none !important; }
Code to paste in Tracking Code:
<style>@import url("https://www.yourwebsite.com/eventify-tickets.css");</style>
Use @import inside a style tag exactly as shown. Browsers can keep an older copy of the file for a while, so if an edit doesn't show, add a version number to the address, for example eventify-tickets.css?v=2, and save again.
These names are added to the page so that you can style or hide parts of it. A name that starts with a dot is a class; one that starts with # is a single element. To target one ticket, add an underscore and the ticket code to any ticket-level class.
These apply when a ticket lets buyers pick sessions.
Note: Hiding is visual only. The hidden text is still in the page for anyone who views its source. Never hide something buyers must see or fill in, such as a required checkout field, the terms checkbox, or price details your local consumer rules require.
I added the CSS to my own website, where the ticket page is embedded, but nothing changed. Why?
The embed is an iframe, which loads the ticket page from Eventify's address. Browsers keep the styles of your website away from a page loaded from another address, so the CSS has to be injected through Eventify's Tracking Code box instead.
Which pages does my CSS affect?
CSS in Tracking Code loads on every page of your event's ticket and registration portal. Use the class names in this article so that each rule only touches what you mean to hide. For a narrower scope, use a ticket's or a form's own Custom Code box.
I saved my CSS but the live page hasn't changed. Why?
Buyers see a published copy of your event's pages. Saving marks that copy as out of date, and Eventify refreshes it in the background, but that can take a while. Click Publish at the top of the dashboard, then Publish Changes, to update it straight away.
I added CSS to a ticket's Custom Code, but the full ticket list still shows the item. Why?
Ticket Custom Code loads only on that ticket's direct link. To hide something for one ticket on the full list, add the rule to Tracking Code with the ticket code at the end of the class name, for example .TICKET_END_DATE_3F9A1C.
The item shows for a moment and then disappears. Is that normal?
Yes, on embedded pages. When the ticket page sits inside an iframe, Eventify waits up to two seconds for your website's cookie-consent answer before it loads Tracking Code.
Some visitors still see the item I hid. Why?
If your website passes its cookie-consent choice to the embedded ticket page and a visitor declines both analytics and advertising cookies, Tracking Code does not load for that visitor, and neither does any CSS inside it.
Does hiding the sale end date change when sales close?
No. It only changes what buyers see. The ticket still stops selling on its sales end date.
Can I hide a whole ticket with CSS?
Don't. A ticket hidden with CSS is still on sale and can still be opened by its direct link.
Will my CSS keep working after Eventify updates?
The capitalised names (TICKET_, SESSION_, BUYER_, HEADER_, FOOTER_) are there for customisation, so target those. Lowercase styling names such as text-xs or rounded-full change between releases.
Does Eventify check my CSS?
No. Eventify saves the code exactly as you paste it. Try it on a test event first, and only inject files from sources you trust, because code in these boxes also runs on your checkout page.
Need more help? Contact Eventify support from the admin panel.
