Dynamic Data Collection rules are part of TIXNGO V4 Advanced features set. If you’re interested, please reach out to your Customer First point of contact.

In TIXNGO V4, as part of the new Ticket Configuration V4, we’re pleased to introduce Data Collection Rules—a powerful feature that allows organizers to customize the data collection process for Ticket Holders.

Why Dynamic Data Collection rule ?

With Dynamic Data Collection Rules in TIXNGO V4, organizers gain flexible control over how and when spectator data is collected, tailored to the specific context of each ticket.

🎟️ Context-Aware Data Requirements
Organizers can customize data collection based on ticket type, event profile, or distribution channel.
Example: Requesting different fields for VIP tickets vs. General Admission.

🔄 Adaptable to Changing Needs
Rules or rule sets can evolve over time or per event, allowing organizers to collect only needed for specific use cases—streamlining the experience without compromising effectiveness.

📊 Actionable Audience Insights with Compliance
By gathering contextual data at the right moment, organizers gain richer, per-event insights while aligning with GDPR principles like data minimization and relevance.

Data Collection rule management

Default rule

A default Data Collection Rule, named DEFAULT, will be automatically created to replace the current default Assignment setup, which was previously customizable from the Settings > Assignment Configuration screen.

Rule creation

Only organizers with the custom data collection feature (ticket.data.custom) can create rule or create custom fields

By default, the Data Collection rule will collect First name and Last Name.

Using TIXNGO standard Assignment fields

You can extend the rule by selecting standard TIXNGO Assignment fields by clicking “Select a field”.

Birth date

Birth city

Birth country

Gender

Nationality

ID number

Country of residence

Address line 1, line 2, line 3

Address zip code

Address city

Address country

Creating your custom fields

If you need to collect information beyond the standard TIXNGO fields, you can define custom fields to tailor data collection to your specific needs.

To ensure multilingual support by design, you must:

Define a unique key for the field, which will also serve as the Crowdin label identifier.
Select the appropriate data type: text, number, boolean, or date.
Indicate whether the field is mandatory or optional.

Rule update

From the Data Collection tab, click the inline Edit Button

From the Rule Details screen, you can modify the Data Collection Rule by:


Adding new fields from TIXNGO Standard Assignment collection
Adding custom fields (if ticket.data.custom enabled)
Toggling field requirement (required vs. optional)
Removing fields from the rule

TIXNGO Wallet will display fields in the exact order defined in the rule.
Please manually arrange the field order to ensure a logical and user-friendly form experience.

Recommendations

Be Frugal and Strategic with Data Collection

To ensure a smooth spectator experience and reduce operational friction, we strongly recommend that organizers apply a minimalist and stable approach when configuring Data Collection Rules:

Focus on the essential – Only request the information that is strictly necessary for operational or legal purposes
Avoid frequent changes – Each rule update requires propagation time between the back-end and mobile apps. Frequent changes may cause confusion, and spectators might not realize they need to act (e.g., complete missing fields) in order to view their QR code.

Following these principles ensures better compliance, cleaner UX, and a more reliable experience for your audience.

TIXNGO Public Documentation

Introduction to V4 Data Collection rules