> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-design/design/event-ticket.md).

# Event ticket

What is specific to an event ticket template: access control, date in the header, Apple poster ticket and event guide, Google venue and anti-sharing options.

Use an event ticket when the main workflow is controlled access with fast scanning at the entrance. Typical content is the event name, venue, date and time, seat, section, gate and a barcode. Updates are useful for schedule changes, seat moves and operational messages.

This page covers only what is specific to this type. Every setting is described in the [pass template editor](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration.md), which also explains how to save and push changes.

<details>

<summary><strong>Real-world examples</strong></summary>

* A stadium issues poster tickets with both team abbreviations, the doors-open time and links to parking and the bag policy.
* A concert organizer fills the venue, gate, section, row and seat of each ticket, so that Google Wallet shows them in its standard ticket layout.
* A festival uses a rotating barcode and limits each ticket to one device, to reduce ticket sharing.

</details>

## Layout of the two wallets

{% tabs %}
{% tab title="Apple" %}

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2F3aWK9TVEPV1lnaR7SNyv%2Fdesign-event-ticket-architecture-apple.png?alt=media&amp;token=bba89ace-738b-4f19-bb19-2a8e968fe357" alt="Apple event ticket layout with the event name, date, seat and barcode"><figcaption><p>Check where the event name, date, seat and barcode sit in the Apple ticket layout.</p></figcaption></figure>
{% endtab %}

{% tab title="Google" %}

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2F5iTi06OTC18NVGwCgtld%2Fdesign-event-ticket-architecture-google.png?alt=media&amp;token=ce8c3e2a-f045-46c2-96db-f70b63a7998f" alt="Google event ticket layout with venue, placement and confirmation areas"><figcaption><p>Check how Google splits the same ticket into venue, placement and confirmation areas.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td align="center">Apple ticket</td><td data-object-fit="contain"><a href="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2FvOwOsS3vlAbkzfsg1Df4%2Fdesign-event-ticket-image-2026-02-12t154141-948-removebg-preview.png?alt=media&amp;token=aa8c218c-91a2-4bbf-84ea-74ff622571dc">design-event-ticket-image-2026-02-12t154141-948-removebg-preview.png</a></td></tr><tr><td align="center">Apple ticket</td><td data-object-fit="contain"><a href="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2F8Ldj7Rqe5MIk4UFNtWnn%2Fdesign-event-ticket-image-2026-02-12t154147-926-removebg-preview.png?alt=media&amp;token=7d355771-7672-4995-b669-7b82dfcdd61f">design-event-ticket-image-2026-02-12t154147-926-removebg-preview.png</a></td></tr><tr><td align="center">Apple ticket</td><td data-object-fit="contain"><a href="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2FqglkDu6q5R2EKj5dDnx8%2Fdesign-event-ticket-image-2026-02-12t154144-942-removebg-preview.png?alt=media&amp;token=545e5aca-3170-46ee-bc24-8ef261a325e1">design-event-ticket-image-2026-02-12t154144-942-removebg-preview.png</a></td></tr><tr><td align="center">Google ticket</td><td data-object-fit="contain"><a href="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2FgJ4MQ9KwFtYc7KTFWpUY%2Fdesign-event-ticket-capture-d-e-cran-2026-02-12.png?alt=media&amp;token=fde87ebf-3106-46c1-898b-61fddd1abbbf">design-event-ticket-capture-d-e-cran-2026-02-12.png</a></td></tr></tbody></table>

Reference documentation: [Apple Wallet passes](https://developer.apple.com/documentation/walletpasses) and the [Google Wallet event ticket template](https://developers.google.com/wallet/tickets/events/resources/template).

## What is specific to an event ticket

### On Apple Wallet

* **Date in the header.** Put the event date in the header fields, the only ones visible when tickets are stacked. Set the **Relevant date** in the General section of the Apple tab to the start time of the event.
* **Poster ticket and event guide.** On iOS 27, an event ticket can use the poster layout, with an artwork, an event name and semantic tags, and can show an event guide with action links such as parking, directions or the bag policy. The conditions, the semantic tags and the preview checks are in [Action links (event guide)](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/apple-tab.md#action-links-event-guide).
* **Barcode.** Choose a barcode type that the access-control scanners read on a phone screen.
* **Back fields.** Use them for how to get to the event, information regarding entrance, receipts and links, such as a link to listen to the artists or the terms and conditions.

### On Google Wallet

* **General.** Issuer, Event name and State. Do not put the customer's name in the event name.
* **Venue.** Where the event takes place.
* **Placements.** Gate, section, row and seat, each optional.
* **Confirmation code.** Optional. Choose the label (Confirmation code, Confirmation number, Order number, Reservation number or Unspecified) and leave the code empty when the event has none.
* **Doors open, face value and homepage.** Doors open takes a label (Doors open, Gates open or a custom label). The homepage is the event website.

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-6fa0675a51b6679f4bf265842e20bbd3f917b95a%2Fevent-ticket-venue-section-native.png?alt=media" alt="Venue section of the Google tab for an event ticket template, with the venue name and address"><figcaption><p>Check that the venue name and address match the event listing.</p></figcaption></figure>

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-cbb6d77d9d669f918b5d5535a03a202811bb0bd6%2Fevent-ticket-placements-gate-single-frame.png?alt=media" alt="Placements section of the Google tab with the Gate settings open"><figcaption><p>Gate, section, row and seat each have their own settings.</p></figcaption></figure>

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-7076b88e7d96b3a284864235fec94f3e5765743e%2Fevent-ticket-confirmation-section-single-frame.png?alt=media" alt="Confirmation section of the Google tab with the Confirmation code label"><figcaption><p>Check that the confirmation code label matches the code the event uses, or leave the code empty.</p></figcaption></figure>

## Access control

These options matter when the ticket opens a door:

* **One user one device** (Google tab, Security): the ticket can only be added from the Google Wallet app on an Android phone, by one holder on one device. Combine it with the **Security animation** and a **Rotating barcode**, so that a screenshot goes stale. A rotating barcode needs a one-time set-up for the tenant in **Settings → Wallet → Google → Rotating barcode**.
* **Smart Tap** (Google tab): lets NFC readers validate the ticket on a tap. It needs Smart Tap to be set up for the tenant.
* **Persist scannable data** (General tab → **Advanced configuration** → **Scannable data**): required for Pass Scanner to find the ticket from the scanned barcode value. See [Scannable data](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/general-tab.md#scannable-data).

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-7a80bcf395a19c053c9e48d1da41d7dfdba8f743%2Fevent-ticket-security-device-options-single-frame.png?alt=media" alt="Security section of the Google tab with the Multiple devices and holders list open, showing the One user one device option"><figcaption><p>Check that the sharing option selected matches the ticketing policy for the event.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/guides-design/design/event-ticket.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
