> 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/connectors/ticketing/aparte/advanced-customization.md).

# Advanced customization

### Why advanced customization matters

The default setup covers most Aparté projects. It works well when one pass template is enough.

Advanced customization is useful when ticket display or template routing needs more control.

<details>

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

* **Multiple ticket families**: use different pass templates for different ticket types.
* **Custom display rules**: transform source values before showing them on the pass.
* **Specific routing**: apply a different template based on ticket metadata.

</details>

### Start simple first

A first rollout should stay simple. Start with the default pass type, validate the result, then add custom rules only when needed.

When extra data is needed, inspect the raw Aparté payload under `debug.aparte.ticket`. This confirms which fields are available before changing the pass design.

### What can be customized

<figure><img src="/files/3k3IgbB5QLDpMNIyYnTG" alt=""><figcaption></figcaption></figure>

Advanced customization usually covers two areas.

* **Display rules**: adjust how Aparté data appears on the pass.
* **Template routing**: send some tickets to a different pass type.

The connector **Default pass type** remains the fallback when no custom rule selects another template.

### Recommended rollout

Use this order to keep the setup easy to validate:

1. Start with one default pass type.
2. Check the source payload in `debug.aparte.ticket`.
3. Add small display rules if needed.
4. Add template routing only when one pass type is no longer enough.

### Get help with advanced customization

Advanced customization can be reviewed with The Wallet Crew support team. This is useful when the right routing or mapping approach is not yet clear.

Support can help define the simplest rule set before implementation.

### FAQ

<details>

<summary><strong>Should every Aparté project use advanced mapping?</strong></summary>

No. Most projects work well with the default setup and one pass type.

</details>

<details>

<summary><strong>Where can the raw Aparté payload be inspected?</strong></summary>

The full source payload is available under `debug.aparte.ticket`.

</details>

<details>

<summary><strong>When should template routing be added?</strong></summary>

Add routing when one default pass type no longer covers the ticket variants cleanly.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/connectors/ticketing/aparte/advanced-customization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.