All Collections
What is the difference between Dynamic Fields and Static Fields?
What is the difference between Dynamic Fields and Static Fields?

Meta fields and Custom fields

Danny Allen avatar
Written by Danny Allen
Updated over a week ago

When it comes to creating and managing digital passes, such as coupons, loyalty cards, or event tickets, PassKit offers a wide range of customization options to suit your specific needs.

Two key elements that play a pivotal role in pass design are Dynamic Fields and Static Fields.

Understanding the differences between these two types of fields is crucial to creating passes that effectively engage and interact with your customers. In this guide, we will break down the distinctions between Dynamic and Static Fields, helping you make informed decisions when crafting your passes with PassKit.

Advanced Fields:

Advanced fields are predefined fields that are commonly used and these are a mix of dynamic and static fields.

  • Dynamic field keys for Advanced Fields will start with person.

  • Static field keys for Advanced Fields will start with members./SingleUseCoupons./eventTickets

Dynamic Fields:

Dynamic Fields are the dynamic, data-driven components of a pass. These fields allow you to personalize passes with real-time, up-to-date information and unique information pertaining to the pass holder.

For example, if you're creating a loyalty card for a coffee shop, you can use Dynamic Fields to display the customer's current points balance or the next available reward.

The data for Dynamic Fields is typically sourced from data you collected when the pass was issued (for example using the enrolment form), your database, API or Zapier/Make. Passholders always have access to the most relevant and current information. This real-time data syncing makes passes more engaging and useful for your customers, as it keeps them informed and incentivized to interact with your business.

Static Fields:

On the other hand, Static Fields are, as the name suggests, unchanging and predefined elements within a pass. These fields are perfect for displaying fixed information that either doesn't need to be updated frequently or updated with information that is the same for all passholders. You change the text in a static field using the designer, via the API or by using Zapier/Make, but note that the update will be sent to all pass holders within the Tier/Offer/Ticket Type. See how to use a static field to send a message to all Apple passholders here

Static Fields are ideal for holding details like the general terms and conditions, your business address and contact details, things that remain constant throughout a pass's lifecycle.

By using Static Fields, you can maintain a consistent and professional look for your passes while ensuring that critical information remains readily available to passholders. While Static Fields may not change over time, they provide essential context and branding that reinforces your business identity to your customers.

Using Static and Dynamic fields:

If you can't find the field you want to use in the "Advanced Fields" you can add your own custom fields from the "Add Custom Field" section.

New Static Field - This will add a new static field to your design. Static fields have a Field Key that begins with "custom." The field name is used to define the rest of the field key.

Example - custom.newField

New Dynamic Field - This will add a new dynamic (meta) field to your design. Dynamic fields have a Field Key that begins with "meta." The field name is used to define the rest of the field key.

Example - meta.newField

Dynamic Fields In Action

This is my card design using dynamic fields for the Name, Email address and Mobile number.

The value for the dynamic fields can be set when the pass is issued, or updated after the pass has been issued. Below are two examples of passes issued from the design above with different display values.

Did this answer your question?