Guide

What to ask in an event registration form in Argentina (and what to leave out)

By SOMOS DER · October 30, 2026 · 6 min read

To check someone in at the door, you need their name, and the email is what gets them their QR code. Every other field has to earn its place with a concrete use: the door, the printed badge or the follow up after the event. If you are organizing from abroad, there are a few extra traps: name order, ID documents that are not Argentine, and a data protection law that asks you to collect as little as possible.

The rule: every field costs you sign ups

Each field you add is friction, paid in people who start registering and never finish. Before adding a field, the question is not whether it would be nice to have, but which concrete decision you will make with it.

In Argentina there is a second reason to keep it short. The personal data law, Law 25,326, says in article 4 that data collected must be "ciertos, adecuados, pertinentes y no excesivos" (accurate, adequate, relevant and not excessive) in relation to the purpose for which they were obtained. An unused field is data you now have to protect.

That is why the PASE registration page is short on purpose: full name (required) and email (optional). With that, the person gets a unique code and is on the event's attendee list.

The fields you do need

Full name. The only truly required field. The operator sees it on screen when scanning, the exceptions desk can search by it if someone arrives without their code, and it is printed on the badge.

Email. Technically optional, but it is what makes the system run on its own: it carries the QR code and the PDF badge, and it is the channel to resend them. If the address looks like a typo, PASE suggests a correction before registering. PASE also stores the delivery status per registrant (sent, failed or no email), so before the event you can see who did not receive anything. Without an email the person can still get in, but someone has to find them by name at the door.

Company and job title, only if there is networking. At congresses and corporate events the badge has a social job: people want to know who they are talking to. If that is your case, these two fields are justified. If not, leave them out.

Names from abroad: one field, written their way

Many forms split first and last name. For an international audience, that split causes more problems than it solves. The W3C internationalization guide on personal names around the world advises: "don't assume that the order they will provide names in will be given followed by family", and suggests asking "whether you really need to have separate fields for given name and family name". It also notes that "Spanish-speaking people will commonly have two family names", typically paternal followed by maternal.

The PASE page uses a single full name field, labeled in Spanish or English depending on the browser language (adding ?lang=en to the link forces English). Each attendee writes the name the way they want it on the badge, in their own order, accents included. The door scans the code, not the surname. If you are hosting guests from several countries, our note on international guests: registration and the door covers names, ID documents and the QR email in more detail.

Fields that are usually extra

• ID or passport number: only if the venue requires visitors to be identified or there is a specific security requirement. The unique code validates entry, not the document. If you need it, do not assume an Argentine DNI: accept passport, national ID card or other, with letters and numbers.
• Phone: rarely used. If the plan is to tell people something, email already does it. Ask for it only if someone will actually call or message.
• "How did you hear about us?": interesting for marketing, but the answers are unreliable and the cost in completion is real. Measure it with parameters in your invitation links instead.
• Postal address: no use on the day of the event.
• Health information: under article 2 of Law 25,326 health data is sensitive data, and article 7 states "Ninguna persona puede ser obligada a proporcionar datos sensibles" (no one can be obliged to provide sensitive data). Dietary or accessibility needs go as optional fields that say what they are used for.
• Attendee category: do not ask it. Assign it, as the next section explains.

The category is assigned by link, not asked

Put a "type of attendee" dropdown on a public form and you will find people declaring themselves press or VIP. The clean way is a different registration link per category: one for general attendees, one for speakers, one per sponsor, one for press.

In PASE each attendee type has its own opaque link that does not reveal the category. Whoever registers through it lands in that type without seeing or choosing it, and that type is what later decides which zones the person can enter, according to the event's permission matrix. At the door, PASE validates the code online and checks pass type and sector.

Fields that depend on the event

• Dietary restrictions: yes for a seated meal, no for a coffee break.
• Arrival time slot: if the venue has limited capacity per hour, PASE can offer time slots with a cap: the attendee picks one, sees how many places are left, and a full slot closes by itself.
• Companion: if capacity allows it, register each companion as a separate person so they count as one more entry.

Consent and the extra data: tell people what you will do

Article 6 of Law 25,326 asks you to inform people, before collecting their data, of "La finalidad para la que serán tratados y quiénes pueden ser sus destinatarios" (the purpose and who may receive the data) and of "El carácter obligatorio o facultativo de las respuestas" (whether each answer is mandatory or optional). In practice: a short notice next to the link or in the invitation, saying what the data is for and who the organizer is, and every optional field marked as optional. Consent, international transfers and attendee rights are covered in our note on attendee data and Argentina's Law 25,326.

If you need fields beyond name and email, you have two routes. Extra fields such as company, job title or phone can be enabled per event for manual entries, and bulk uploads store them the same way. If you run your own registration page, PASE receives it: besides name, email and category, it stores an extra data block with each registration. Those fields are searchable in the attendee list and come out in the export.

If a field is not used at the door, on the badge or in the follow up, all it does is lower the number of people who register.

Frequently asked questions