A project participant documents the Averta choice
Clint Cebulak’s original Ticketmaster account describes building an internal creative team and developing a new identity across products and platforms. He identifies Averta as the chosen family and dates the launch to late 2018. This is a firsthand account of that project, rather than a font name inferred from a screenshot or a claim about every earlier Ticketmaster design.
The official brand page defines a communication scope
Ticketmaster Belgium’s own brand-assets page names Averta for marketing and communications, with Calibri as a fallback where Averta is unsupported. Cebulak separately describes deconstructing the legacy logo into a condensed T for a flexible visual device. Keep that logo work distinct from the text family. A font named in marketing guidance does not automatically identify the contents of every SDK, app version or event poster.
Build an independent event-listing sample
For an original event directory, prepare a long performer name, venue, date, start time and a concise description. Let the event title wrap without separating the time from its label. Keep the action clear and avoid making every supporting detail compete with the headline. A directory should still work when two neighboring events have very different title lengths.
Compare realistic text rather than logo resemblance
Inter, Manrope and Source Sans 3 are independent specimens, not Averta files or official alternatives named here. Compare an entire event card and a compact ticket-information block. Keep booking references and dates distinct through consistent placement. If your production requires Averta, retain the exact family and style names and obtain the applicable files through an authorized source.
Your questions, answered.
Which font does Ticketmaster’s brand page identify?
The cited official page identifies Averta for marketing and communications and Calibri as a fallback when needed.
Does the late-2018 project account identify every Ticketmaster app font?
No. It documents an identity project. Particular apps, SDK versions and historical materials require their own implementation context.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.