---
title: "Personalisation"
canonical: "https://support.passcreator.com/space/KB/22282276/Personalisation"
format: markdown
---
## Using additional properties to personalise your pass

Additional properties are a way to personalise your passes. You define what fields are different for each pass and can then use them anywhere on your pass as placeholders. When creating a pass, Passcreator will ask for the properties you’ve defined and automatically replace the placeholders with the actual values.

You don’t necessarily have to use the placeholders visibly for your users. This also allows you to store metadata you need, e.g. the contact number from your CRM that you can then use to search for.

To create an additional property, edit your pass template, click on the tab "Additional properties" and add a new field. You need to specify a name for the property that can be used as a placeholder elsewhere on your template as well as a field type.

Additional properties are also important if you want to send your passes using SMS or Email since these fields are used to store the email address or phone number of your users.

If you create an additional property with the name “Name”, the placeholder you need to use is {Name}.

![image](media://46f62caf-243e-48ab-ab0e-29b13ebc63f6)

## Placeholder functions

### {urlencode({yourPlaceholder})}

*This will convert the given placeholder(s) into a format that can be used in URLs.*

#### Example

You want to use a URL that should contain your placeholders {firstName} and {lastName} as a conjunct parameter in your QR code: https://yourdomain.de/?name={urlencode({firstName} {lastName})}


### {sign({yourPlaceholder})}

*This will generate a signature of the given placeholder(s). This can be used for tamper protection.*

**🛡️ How tamper protection works**

1. **Data Signing (Sender)**:

- The sender creates a **hash** of the data using a cryptographic hash function.
  - Hashing ensures that even a tiny change in the data produces a different hash.
- The sender **encrypts the hash with their private key**, creating a **digital signature**.
- The **data + signature** is sent to the receiver.

2. **Data Verification (Receiver)**:

- The receiver uses the **sender’s public key** to **decrypt the digital signature**, revealing the original hash.
  - The Public Key can be obtained through the [API](https://passcreator.atlassian.net/wiki/spaces/API/pages/1490026501)
- The receiver independently **hashes the received data** using the same hash function.
- If the **decrypted hash (from signature)** matches the **newly computed hash**, the data is:
  - **Authentic:** Signed by the owner of the private key.
  - **Untampered:** No modifications occurred during transmission.
  - If the hashes **don’t match**, the data has been **tampered with**.