top of page

What Guest Data Requirements Should You Confirm Before Booking an Activation?

Nov 11
4 min read

By Dennis Walthers, Founder & CEO, Interactive Dallas


Before booking an activation, I recommend writing down what information the experience needs and what your team expects to receive afterward. A photo archive, a guest's delivery address and a sales record are different deliverables. Naming them early makes the purchasing conversation much more useful.


For our American Airlines 100th Birthday activation, we coordinated eight cities on the same day and gathered the images into one ZIP file for the client. That is a concrete example of an image handoff. It does not, by itself, describe a contact database, a marketing permission record or a CRM connection.


AI-generated illustration of event professionals reviewing a checklist and schedule beside audiovisual equipment.

AI-generated planning illustration; not a photograph of a client event.


Use the checklist below to request written answers for your particular project. It is not a statement of Interactive Dallas's standard retention periods, integrations, security certifications or legal compliance. Those details need to be confirmed for the actual configuration and agreement.


Start with the purpose of each field


Write a separate purpose beside every proposed input. An image may be needed to produce a portrait. A chosen visual style may personalize the result. A delivery destination may be needed to send the requested output. A sales question serves a different purpose.


Then ask whether the experience still works without that field. Optional personalization should not quietly become a requirement simply because a form can collect it. Avoid asking for sensitive or unnecessary details when a simpler choice achieves the creative goal.


Our guide to content guests want to keep is a useful starting point for deciding what the guest actually values. Let that purpose shape the data request.


Map where information goes


Ask the vendor to describe the proposed flow from capture through processing, delivery and any agreed export. Which tools or service providers are involved? Which party can access each category? Does the brand receive images, contact information, participation counts or some combination?


For an AI experience, ask specifically whether images or other inputs are sent to another provider and what use that provider makes of them. Request documentation rather than assuming that every configuration behaves the same way. If the answer is not available, leave the requirement unresolved in the procurement review.


The buyer should involve its privacy, security or legal reviewers where appropriate. A sales description of an experience is not a substitute for their approval of the actual data flow.


Separate four guest decisions


Your review should distinguish participation, output delivery, public image use and later marketing. Each has a different purpose. Ask what guests will see, how choices will be recorded and how the workflow handles someone declining an optional use.


For instance, a guest may want a private photo but not want it used in brand advertising. The event team should know how that preference affects galleries, displays and post-event content selection. Have the responsible reviewers approve the wording and process before staff are trained.


Avoid making a legal promise in booth signage unless the relevant team has verified it. Do not assume that receiving an output authorizes every later use of the image or contact information.


Complete the procurement worksheet


For every line, record the requirement, vendor's written answer, supporting document, internal approver and unresolved issue:


  • Data fields: what is collected, why and whether it is required.

  • Processing: which systems and providers receive which inputs.

  • Guest information: the notices and choices shown before collection.

  • Delivery: available methods, error handling and support ownership.

  • Access: who can view, download, export or share the material.

  • Retention: proposed storage periods and the process for deletion requests.

  • Reuse: permitted purposes for images and contact information.

  • Handoff: file type, field definitions, recipient and transfer method.

  • Exceptions: what happens during lost connectivity or a guest complaint.

  • Approval: who can accept the final configuration and any later change.


This worksheet gives procurement something specific to compare. A blank answer is a follow-up question, not evidence that a requirement is satisfied.


Test the handoff before the event


Request a demonstration or a small sample using approved test material. If the deliverable is an archive, check how the files are organized and how the intended recipient will receive access. If structured records are required, inspect field names, missing values and permission information.


Confirm whether the requested transfer is manual or automated, and who is responsible for any mapping or import. Do not write an integration into your event plan until the relevant parties have confirmed it works for the agreed scope.


Include this test and any required review in the schedule. Our activation brief guide explains why assigning responsibilities early prevents misunderstandings about what a supplier is delivering.


Keep reporting proportionate


You may need aggregate participation figures without needing every guest's contact details. Ask the team to distinguish the evidence required for evaluation from information collected merely because it is available.


Our measurement guide separates production, engagement and business outcomes. That distinction helps you specify a useful report without assuming a photograph is a unique person or a sales lead.


Frequently asked questions


Does every activation need guest contact information?


Do not assume it does. Ask what the selected experience and delivery method require, and whether a suitable alternative can meet your objective with fewer inputs.


Does a ZIP of images include a customer database?


No. An image archive only establishes the agreed image deliverable. Any contact records, field mapping or permission evidence must be specified separately.


Can I assume an activation connects to our CRM?


No. Confirm the exact system, transfer method, fields, permissions and responsible person. A downloadable file and a working automated integration are different arrangements.


What retention period should we expect?


Request the actual proposed periods for each relevant system and data type. Have your organization's reviewers determine whether those terms meet its requirements.


Who approves guest notices?


Assign that responsibility explicitly. The organizer's appropriate privacy or legal reviewer should assess the proposed wording and use, with accurate technical information from the supplier.


What if guests include children?


Raise that before choosing the workflow. Ask the organizer's reviewers to determine the appropriate participation, permission and image-use requirements for the audience and circumstances.


What should be resolved before booking?


At minimum, identify the purpose, required inputs, receiving parties, delivery and handoff expectations, and who approves unresolved issues. Put material requirements into the agreed scope instead of leaving them as assumptions.


To discuss your event, contact Dennis Walthers or call 214.293.5044.

Comments


bottom of page