# Event ticket Whether you are a new client who needs to create the template for the tickets that will be distributed to your attendees, or a master of The Wallet Crew who needs to update an existing template, this article will help you navigate to our template designer. The goal is to configure a ticket template that will reflect your brand identity, clearly display essential event information, and ensure a smooth and secure experience across Apple Wallet and Google Wallet. ## Architecture Apple and Google have their own ticket pass templates as you can see below. {% tabs %} {% tab title="Apple" %}

{% endtab %} {% tab title="Google" %}

{% endtab %} {% endtabs %}

	Cover image
Apple ticket	design-event-ticket-image-2026-02-12t154141-948-removebg-preview.png
Apple ticket	design-event-ticket-image-2026-02-12t154147-926-removebg-preview.png
Apple ticket	design-event-ticket-image-2026-02-12t154144-942-removebg-preview.png
Google ticket	Capture_d_écran_2026-04-09_à_14.43.48-removebg-preview.png
Google ticket	Capture_d_écran_2026-04-09_à_14.42.55-removebg-preview.png
Google ticket	design-event-ticket-capture-d-e-cran-2026-02-12.png

{% hint style="info" %} **If you want to go further, find all the details of the two versions:** {% endhint %} **Apple:** {% embed url="" %} **Google:** {% embed url="" %} ### How to configure it on The Wallet Crew With The Wallet Crew, you have access to a **template designer** that allows you to **personalize the event tickets** you will distribute to your clients. Let’s see in detail how to personalize each section! ## Apple **Let’s take a look at the different sections of the Apple template designer.** ### General section On the general section, you have two mandatory field that you must fill : * **Description** : a brief description of the pass, that will appear on the back on the card * **Organization name** : the name of your company or brand You also have the possibility of putting a text next to your logo, **activate the sharing of the ticket** if you want your customers to be able to share it or not with other people, the “void feature” for the coupons, a relevant and expiration date that are used for event tickets. You can also **define the distance** from a relevant latitude and longitude that the pass is relevant, for **geofencing notifications.**

### Barcode Choose the **type of barcode** that is compatible with your control hardware. The barcode value corresponds to the **identifiers** that will allow you to identify the event ticket with your control terminal at the entrance. Finally, the alternate text can be used to display the barcode data in case the barcode cannot be scanned.

### Colors & Images To change the background color of your ticket, simply **add the color code in the fields** provided for this purpose. To add an image, upload it from your device. ### Header Fields This section is particularly important in the Apple version, as the tickets are **stacked on top of each other**. Only the header of the ticket remains visible. Therefore, it is important that this section catches the eye and encourages clicking on the card, especially by displaying the most important information such as the date, or other relevant information.

### Front fields The front fields are the fields that are used to **display information in the recto of the ticket**, under the strip image. The label you will choose is the same for every user (per language), but you can customize the value to display the name of the event or the customer's seat.

{% hint style="warning" %} **To personalize the front fields please refer to your tech team to find which dynamic value you have to write.** {% endhint %} ### Backfields This section, located on the back of the event ticket, includes several useful pieces of information for the customer: * How to get to the event * Information regarding entrance * Receipts * The ability to add links, such as a link to listen to the artists, access to the terms and conditions, etc.

### Other sections On Apple, you also have four other sections : * **Locations** : Used for geofencing notifications. * **Beacons** : Also used for geofencing notifications. * **Associated store identifier** : You can link your application if it's located on Apple Store * **NFC** : A feature that allows customers to exchange digital content, and connect electronic devices with a touch. {% hint style="warning" %} **Please contact your The Wallet Crew representative to activate these features** {% endhint %} {% hint style="danger" %} **Once you’ve done some modifications, don’t forget to click on “save” on the top of your screen!/** {% endhint %} *** ## Google **The Google template designer is a bit different than the Apple one.** {% hint style="warning" %} **Here are a few things you need to know before configuring your Google template:** {% endhint %} 1. Some fields such as “issue” and “program name” are **mandatory** 2. Google preconfigures the fields based on their intended values, so it’s best not to enter the customer’s name in the Event name for example, even if that’s how you’d like it to appear on the pass 3. Dynamic values (e.g., {{firstName}}) should be **placed in dedicated dynamic fields**. ‘Label’ fields are intended for static text only. **Let’s take a look at the different sections.** ### General section On the general section, you have three **mandatory fields** that you must fill : * **Issuer**: the name of the brand or company that issues the ticket * **Event name**: it appears on the front of the pass, it can be the name of your event * **State**: the state of your ticket (active, expired, completed, inactive)

### Security When you configure a template, you need to decide **whether the customer can share their pass or not**. Regarding Google you have three option: * **Multiple holders**: it means that the customer can share their pass with anyone * **One user all device**: a customer but with several devices (a watch for example) * **One user one device**

### Colors & Images To change the background color of your ticket, simply **add the color code in the fields** provided for this purpose. To add an image, upload it from your device.

### Venue A section to enter the detail of where the event will take place!

### Placement You can define the gate, row, seat and section of your customer's ticket. Each field is optional. {% hint style="warning" %} **To personalize the placement fields please refer to your tech team to find which dynamic value you have to write.** {% endhint %}

### Confirmation On the Google template, you can also define and display a confirmation code if it's required for your event. This is an optional field, if you don't have any confirmation code, you can select "Unspecified".

### Additional links, Smart tap and Valid Time Interval You can decide to add **additional links** to the customer's ticket, for exemple the event website link! Furthermore, you can also configure the **Smart tap feature** that allows your customer to simply **validate their ticket** by taping their device on your compatible hardware terminal. Finally, the Valid time interval section allows you to **define a start and an end date** to your event!

### Messages This section, located on the back of the event ticket, includes several useful pieces of information for the customer: * How to get to the event * Information regarding entrance * Receipts * The ability to add links, such as a link to listen to the artists, access to the terms and conditions, etc.

### Value added opportunities This section allows you to add a **small section at the bottom of the ticket**. This is used to display offers, or news.

Event ticket - Value Added Opportunity Google

### Other sections On Google, you also have four other sections : * **Face Value** : The price of the ticket * **App links** : Used to add a link for an application * **Homepage** : Used to add the link of the event website * **Locations** : Used for geofencing notifications {% hint style="danger" %} **Once you’ve done some modifications, don’t forget to click on “save” on the top of your screen!** {% endhint %} ## FAQ

Do I need to save my configuration and update all the passes at the same time?

Once you've done editing your template, you have **two options:** * Saving your configuration without pushing an update on all passes: this is the best option is you have a lot of passes. You can save your configuration and decide to schedule an update during the night to avoid the impact of mass updating. * Saving your configuration and pushing an update: this is the best option if you are doing some tests or have a few passes in your environment.

How to modify the configuration for another language?

You have the ability to modify the design of the pass for each language. If you click on "general" in the menu, you can add a language. You'll then see it appear on the template designer and will be able to edit it.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.thewalletcrew.io/design/event-ticket.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.