--- title: "Case Study: What Happened When We Connected a Luma Event" description: "What changes when a Luma event is connected to MeetWho? This case study follows the workflow from event access and participant context to smarter networking, showing where the integration adds value, what organizers should watch for, and how the experience can move beyond registration toward meaningful introductions." canonical: "https://meetwho.app/blog/luma-integration-case-study" language: "en" published: "2026-08-18T00:59:32.183+00:00" updated: "2026-08-18T00:59:32.515813+00:00" reading_time_minutes: "18" source: "MeetWho — the networking layer for events and communities" license: "Quote with attribution and a link to the canonical URL." --- # Case Study: What Happened When We Connected a Luma Event ## TL;DR - Event registration solves an essential operational problem: it establishes who plans to attend and gives organizers a way to manage participation. - Registration information is primarily about participating in an event. - One way to support event networking is to show participants a large directory and let them search through it themselves. - At the workflow level, the starting point was simple: there was already an event, and the question was what an additional networking experience could contribute. - Participants still need a clear event experience, while organizers need reliable ways to manage attendance and communication. ## Key questions **Why Connect a Luma Event to a Networking Layer?** Event registration solves an essential operational problem: it establishes who plans to attend and gives organizers a way to manage participation. Networking presents a different problem. **Why a Public Attendee Directory Wasn't the Goal?** One way to support event networking is to show participants a large directory and let them search through it themselves. That can be useful in some settings, but it also transfers most of the work to the attendee: browse profiles, interpret limited information, guess who is relevant, and decide how to approach them. **How the Luma Event Connection Worked?** At the workflow level, the starting point was simple: there was already an event, and the question was what an additional networking experience could contribute. Connecting the event did not change the fundamental distinction between managing participation and helping people build meaningful professional relationships. **What Changed for the Participant Experience?** The most noticeable shift was in the question participants were being asked to answer. In a traditional event flow, the experience can stop at registration and attendance. **What Changed for the Organizer?** For organizers, the main change was conceptual as much as operational. Networking could be treated as something intentionally designed into the event rather than something expected to happen simply because the right people happened to be in the same room or online session. **Luma Registration vs. MeetWho Networking Intelligence** Connecting an event to a networking layer does not mean every part of the event experience moves into the same system or serves the same purpose. Registration and networking answer different questions, and treating them as interchangeable can create the wrong expectations for both organizers and attendees. ## Full article Title: **Luma Integration Case Study: What Happened | MeetWho** Description: **See what happened when we connected a Luma event to MeetWho, from participant context and privacy to smarter event networking and meaningful introductions.** # Case Study: What Happened When We Connected a Luma Event **Luma integration case study:** connecting an event to MeetWho gave us a useful way to examine what happens when registration is no longer the end of the attendee journey. Instead of treating a list of registered participants as the networking experience itself, we looked at what could happen when people were given context about **who might be relevant to meet, why the connection could matter, and how to start the conversation**. The purpose was not to replace an existing event workflow or turn every attendee into a publicly browsable profile. The more interesting question was whether an event could preserve its registration experience while adding a networking layer built around participant intent, relevance, and permission. That distinction shaped what we learned from connecting the event to MeetWho. ## Why Connect a Luma Event to a Networking Layer? Event registration solves an essential operational problem: it establishes who plans to attend and gives organizers a way to manage participation. Networking presents a different problem. Knowing that two people registered for the same event does not automatically explain whether they should meet, what they have in common, or whether a conversation would be mutually useful. That gap becomes especially visible at professional events. A founder may be looking for someone with enterprise sales experience. An operator may want to meet teams working on a particular problem. A community member may have expertise another participant needs but would never discover through a name, company, or job title alone. The challenge is therefore not simply increasing access to attendees. It is creating enough relevant context to help people make better networking decisions. ### Registration Data and Networking Context Solve Different Problems Registration information is primarily about participating in an event. **Networking context** is about understanding what a participant hopes to accomplish once they are there. For MeetWho, that context can come from a professional profile in which participants describe what they are working on, what they are looking for, who they would like to meet, and where they may be able to help someone else. Those signals are more useful for networking when they are considered together rather than in isolation. A job title might suggest what somebody does professionally, but it may say very little about their objective for this particular event. Participant goals, current projects, areas of interest, and complementary needs can provide a clearer basis for deciding whether an introduction is worth exploring. This is also why the **Luma event integration** should not be understood as an attempt to turn registration data into automatic assumptions about people. The networking experience depends on the context participants choose to provide and the permissions that apply to their participation. ### Why a Public Attendee Directory Wasn't the Goal One way to support event networking is to show participants a large directory and let them search through it themselves. That can be useful in some settings, but it also transfers most of the work to the attendee: browse profiles, interpret limited information, guess who is relevant, and decide how to approach them. MeetWho takes a different approach. Rather than making maximum profile visibility the objective, it is designed to recommend relevant people among users who are permitted to participate in networking. Organizer settings and participant consent remain important boundaries, and paid membership does not provide a way around hidden profiles or private contact information. The idea behind **Event Networking Intelligence** is therefore not “see more people.” It is closer to MeetWho’s central principle: **Know who to meet.** A smaller set of relevant, explained recommendations can be more actionable than a long list of names with little indication of why a conversation might matter. ## How the Luma Event Connection Worked At the workflow level, the starting point was simple: there was already an event, and the question was what an additional networking experience could contribute. Connecting the event did not change the fundamental distinction between managing participation and helping people build meaningful professional relationships. It is important not to overstate the technical implementation. Specific claims about APIs, real-time synchronization, automatic imports, or two-way data transfer should only be made when they match the verified integration in use. What matters for this case study is the participant journey that followed: event context could lead into a networking experience where people supplied richer professional intent and received more relevant guidance about whom to meet. ### Step 1 — Start With the Existing Event The event itself remains the anchor. Participants still need a clear event experience, while organizers need reliable ways to manage attendance and communication. Adding MeetWho is useful only when networking is genuinely part of the event objective rather than an extra feature added without purpose. That means the first question is not “How many profiles can we display?” It is “What kinds of useful connections should this event make possible?” Once that objective is clear, the networking layer can be designed around the people attending rather than around directory size. ### Step 2 — Give Participants a Networking Context Participants can build a professional profile that communicates more than identity. They can describe what they are currently working on, what they need, the kinds of people they hope to meet, and the subjects where they can offer useful knowledge or support. This creates the foundation for the next stage: moving from a collection of attendees to **relevant attendee recommendations** that can be ranked and explained rather than discovered by chance. ## What Changed for the Participant Experience? The most noticeable shift was in the question participants were being asked to answer. In a traditional event flow, the experience can stop at registration and attendance. Participants know where to go and when to join, but they may still have little guidance about **who among the other attendees is worth meeting**. With a networking layer in place, the journey can become more intentional. Instead of browsing broadly and guessing, participants can provide context about their goals and receive suggestions based on relevance. The value is not simply that another attendee appears on screen; it is that the recommendation can explain why the person may be useful to meet and what the conversation could be about. ### The Question Shifted From “Who’s Here?” to “Who Should I Meet?” That distinction changes the networking experience significantly. A directory answers a visibility question. A recommendation system tries to answer a relevance question. A simplified before-and-after flow looks like this: Before With networking intelligence Join the event Join the event Browse attendees or meet people by chance Add professional and networking context Guess who may be relevant Receive ranked, relevant suggestions Interpret limited profile information See why a person may be worth meeting Decide how to approach them Use contextual conversation starters Hope the connection continues Connect, message after a mutual connection, and follow up This does not mean every recommendation will lead to a conversation, or that every conversation will create a business outcome. It means the participant receives more useful information before deciding where to spend limited networking time. ### Participants Received Context Before Starting a Conversation Relevance alone is not always enough. If a platform simply says that two participants are a “match,” the user still has to determine what that means. MeetWho is designed to make recommendations more understandable by showing why two people may benefit from meeting and how their interests, needs, or experience could complement one another. For example, one participant might be building a product for enterprise teams while another has experience helping startups navigate enterprise procurement. The important signal is not just that both work in technology. It is the more specific relationship between what one person needs and what the other may be able to contribute. That explanation can also make the first interaction easier. Personalized conversation starters can help a participant move from “This person looks relevant” to a practical opening that reflects the context of the recommendation. The goal is not to automate human relationships, but to reduce the friction that often prevents useful conversations from starting. ### The Connection Could Continue After the Event Networking value does not necessarily end when an event closes. Participants may meet someone relevant and still need to remember why the connection mattered, what they discussed, or when to follow up. MeetWho supports that longer-term workflow through features such as private notes, follow-up reminders, connection history, and messaging after a mutual connection. Depending on the user’s plan, additional networking tools can also support more active recommendations, richer match explanations, personalized conversation starters, AI-assisted introduction or follow-up messaging, and calendar integrations. The important distinction is that these tools support follow-through rather than guarantee it. A useful recommendation can create an opportunity for a better conversation, but the relationship still depends on the people involved. ## What Changed for the Organizer? For organizers, the main change was conceptual as much as operational. Networking could be treated as something intentionally designed into the event rather than something expected to happen simply because the right people happened to be in the same room or online session. That matters because an event can have strong attendance and still produce weak networking. Bringing relevant people together creates potential. Helping those people recognize one another creates a different kind of value. ### Networking Became an Intentional Part of the Event Design Once networking goals are made explicit, organizers can think beyond headcount. They can consider what kinds of participant-to-participant interactions would make the event more useful: founders meeting experienced operators, community members finding collaborators, or professionals discovering people with complementary expertise. MeetWho does not replace good programming, facilitation, or community design. Instead, **event networking intelligence** can support those efforts by helping eligible participants prioritize people who appear relevant to their stated goals and professional context. This makes networking less dependent on luck. Participants can still meet people spontaneously, but they also have a structured way to identify conversations that may deserve attention before, during, or after the event. ### Privacy Settings Remained Part of the Workflow Adding more networking intelligence should not require exposing more personal information than necessary. MeetWho’s model prioritizes organizer settings and participant permission, which means networking availability and profile visibility remain subject to the rules established for the event and the choices participants make. Paid membership does not unlock hidden profiles or private contact information, and MeetWho does not sell attendee lists. This matters because the purpose of personalized networking is not to create unrestricted access to everyone at an event. It is to make permitted connections more relevant. In practical terms, that means privacy is part of the product logic rather than an obstacle added after recommendations are generated. For organizers building professional communities, that distinction can be as important as the matching itself. ## Luma Registration vs. MeetWho Networking Intelligence Connecting an event to a networking layer does not mean every part of the event experience moves into the same system or serves the same purpose. Registration and networking answer different questions, and treating them as interchangeable can create the wrong expectations for both organizers and attendees. The clearest way to understand the relationship is to separate event participation from networking intelligence. A registration workflow helps someone join an event. MeetWho focuses on what can happen once networking becomes a deliberate part of that experience: participants can express what they are looking for, receive relevant recommendations, understand why someone may be worth meeting, and manage connections over time. Participant need Registration/event workflow MeetWho networking-intelligence workflow Why it matters Join the event Manages participation and access Builds on the event context Establishes who is taking part Express networking intent Not assumed by registration alone Participants can describe goals, needs, and expertise Adds context beyond identity Discover useful people Depends on the event setup Relevant participants can be ranked Reduces manual searching Understand relevance Not inherently part of registration Recommendations can explain potential fit Makes suggestions more actionable Start a conversation Usually participant-led Personalized conversation starters may help Reduces initiation friction Protect visibility Depends on platform and configuration Organizer settings and participant permission remain central Supports privacy-aware networking Continue after meeting Varies by workflow Mutual messaging, notes, reminders, and connection history Extends value beyond the event *Product capabilities and integrations can change over time. Luma-specific functionality should be checked against Luma’s current official documentation before publication. This comparison distinguishes workflow roles rather than claiming that a particular capability is absent from Luma.* ## Where the Integration Was Most Useful The value of a **Luma integration case study** is not simply proving that two products can be connected. The more useful question is where an additional networking layer makes a meaningful difference. The strongest use cases are events where participants arrive with goals that depend partly on meeting other participants. That includes events where the quality of a small number of conversations may matter more than the number of people someone can see. In these situations, context about needs, expertise, interests, and objectives can help move networking from chance encounters toward more deliberate discovery. ### Founder and Startup Events Startup events often bring together people with very different but potentially complementary objectives. One founder may want to meet someone who understands enterprise sales, while an experienced operator may be interested in helping early-stage teams. An investor, product specialist, or potential collaborator may have another reason for attending entirely. A generic attendee list can reveal that these people are present without explaining how their objectives intersect. MeetWho can use the professional context participants choose to provide to make those relationships easier to identify. The recommendation becomes useful when it explains not only *who* someone is, but why the introduction may make sense for both sides. ### Communities and Professional Meetups Professional communities frequently include participants who share a broad field but do not yet know one another personally. In a room full of marketers, engineers, founders, operators, or creators, job titles alone may not be enough to identify the most relevant conversations. A networking layer can help surface more specific connections. Someone looking for a collaborator on a new project may be matched with a participant offering precisely that expertise, while another attendee may discover someone facing a problem they have already solved. This creates a more purposeful starting point without requiring everyone to expose themselves through an unrestricted public directory. ### Workshops and Conferences At workshops and conferences, networking competes with sessions, presentations, breaks, and limited attendee attention. Participants may have only a few opportunities to start conversations, which makes prioritization especially important. **Relevant attendee recommendations** can help participants use that limited time more intentionally. Instead of choosing conversations only through proximity or chance, they can identify people whose goals or expertise appear aligned before deciding whether to connect. The networking layer complements the event program rather than replacing it. ### Online Events and Programs Online events remove many of the physical cues that make spontaneous networking possible. There is no crowded coffee line, shared table, or hallway conversation to create an accidental introduction. Unless networking is deliberately designed, participants can attend the content and leave without interacting meaningfully with one another. That makes contextual discovery particularly useful for online communities, entrepreneurship programs, virtual workshops, and similar formats. When participants can see why another person is relevant and receive help starting the conversation, networking becomes a defined part of the experience rather than an expectation left to chance. ## What We Learned From Connecting a Luma Event The most important lesson was not that more technology automatically produces better networking. The useful change came from introducing better context between attendance and conversation. Registration establishes that people share an event; networking intelligence tries to establish whether they may also share a reason to talk. This distinction is central to MeetWho’s positioning. The objective is not to maximize the number of profiles someone can browse. It is to improve the likelihood that participants can identify **who to meet and why**. ### More Attendees Does Not Automatically Mean Better Networking A larger attendee pool creates more possible connections, but it also creates more decisions. Without a way to prioritize those possibilities, the burden shifts to participants to search, interpret, and guess. For professional networking, relevance can therefore matter more than volume. A handful of well-explained suggestions may be more useful than hundreds of profiles with little context about mutual value. ### Matching Without an Explanation Is Less Useful A recommendation becomes more valuable when participants can understand the reasoning behind it. Simply labeling two people as a match can create another decision problem: the participant still needs to work out what they have in common, whether the connection is relevant, and what they could discuss. MeetWho addresses that gap by adding context to recommendations. When appropriate, participants can see why someone may be worth meeting, how their goals or experience could complement one another, and what might make a useful starting point for a conversation. That explanatory layer turns matching from a ranking exercise into something participants can evaluate for themselves. ### Intent Improves the Networking Context Professional titles and company names provide useful information, but they rarely describe what someone wants from a particular event. A participant may be hiring, exploring partnerships, looking for domain expertise, seeking feedback, or hoping to help others with a problem they already understand. Capturing that intent gives networking recommendations a stronger foundation. Instead of assuming relevance from identity alone, MeetWho can consider what participants choose to say about their current work, needs, interests, and potential contribution to others. ### Privacy Cannot Be an Afterthought Relevant networking should not come at the expense of participant control. Organizer settings and participant permission determine how networking is made available, while paid membership does not provide access to hidden profiles or private contact information. That boundary is important to the model. MeetWho is designed to improve **permission-aware networking**, not to turn an event registration list into a database that can be freely searched, exported, or monetized. MeetWho does not sell attendee lists. ## What This Luma Integration Case Study Does Not Prove This case study should not be interpreted as evidence that every event will produce the same networking outcomes. A relevant recommendation does not guarantee that two participants will connect, reply, schedule a meeting, or create a business relationship. It also does not establish a specific improvement in engagement, introductions, or networking success without measured data. The useful conclusion is narrower: connecting an event workflow with richer participant intent creates a practical way to move from knowing **who is attending** toward understanding **who may be worth meeting**. The experience also does not replace event programming, community management, facilitation, or thoughtful organizer involvement. Networking intelligence can support those activities, but successful professional relationships still depend on the participants themselves. ## Should You Connect Your Event to MeetWho? MeetWho is most relevant when participant-to-participant discovery is an important part of the event experience. It may be a strong fit when attendees arrive with complementary needs, expertise, or professional goals and would benefit from a clearer way to find one another. It may be less important for events where communication is intentionally one-directional or where participants have little reason to discover and connect with one another. The question is not whether every event needs networking technology, but whether better introductions would make *your* event more useful. - Attendees participate partly to meet relevant people. - Participants have complementary expertise, needs, or goals. - You want networking to go beyond browsing an attendee directory. - Participant consent and privacy matter to your community. - You want people to understand **why** an introduction may be relevant. - You want useful connections to remain manageable after the event. ## How to Try the Same Approach With Your Next Event Organizers can create an event on MeetWho for free and use its core event-management capabilities, including event pages, registrations, application approvals, waitlists, announcements and reminders, registered-participant-only online event links, QR check-in, and networking privacy settings. These capabilities should not be confused with the technical mechanics of a specific Luma connection. If you are using Luma, verify the current integration workflow before making assumptions about imports, synchronization, or data transfer. The broader principle remains the same: start with the event objective, decide what networking context participants genuinely need to provide, and let relevance guide discovery. ### Start With the Networking Objective Define what a useful connection looks like for your event before asking participants for more information. A founder meetup, professional community, workshop, and online program may each require different networking signals. The goal should be to collect enough context to make introductions useful without turning profile completion into unnecessary friction. ### Let Relevance Guide Discovery MeetWho positions this approach as **Event Networking Intelligence**: helping participants identify meaningful potential connections rather than maximizing the number of profiles they can access. > **Create your event for free** and help participants move from simply attending to knowing who to meet. ## Frequently Asked Questions About Luma Event Integrations ### What is a Luma integration? A Luma integration connects a Luma-based event workflow with another product or service. The exact technical method can vary, so API behavior, synchronization, imports, and data-transfer details should always be verified against the current implementation and official Luma documentation. ### Can I connect a Luma event to MeetWho? A Luma event can be used as part of a workflow that extends into MeetWho networking, but the exact connection method should be confirmed against MeetWho’s current implementation before publication or setup. This case study deliberately avoids claiming unverified real-time sync, two-way synchronization, or API behavior. ### What does MeetWho use to recommend people to meet? MeetWho can use participant-provided professional context, networking goals, interests, and relevant event context to identify useful potential connections. Recommendations can also explain why two people may benefit from meeting and help them start a conversation. ### Does MeetWho show everyone a public attendee list? No. MeetWho prioritizes organizer settings and participant permission rather than indiscriminately exposing every attendee. Its networking model focuses on relevant recommendations among users who are eligible to participate. ### Does MeetWho give paid users access to hidden profiles or private contact details? No. Paid membership does not bypass participant privacy, unlock hidden profiles, or provide access to private contact information. ### Can organizers use MeetWho for free? Yes. Organizers can create events and use MeetWho’s core event-management functionality for free. Participants can also join events on the free plan and receive a limited number of personalized introductions. ### What does MeetWho Plus add? MeetWho Plus expands personal networking tools with more active recommendations, richer match reasoning, personalized conversation starters, AI-assisted introduction and follow-up messages, unlimited notes and reminders, calendar integrations, and other advanced networking capabilities. Connecting the event mattered less because it created “another integration” and more because it created a bridge between **attending an event** and **knowing who is worth meeting there**. That is the central lesson of this **Luma integration case study**: better networking does not require exposing more people—it requires giving participants better context, preserving meaningful privacy boundaries, and helping the right conversations become easier to recognize and start. **Know who to meet.** --- Canonical HTML version: https://meetwho.app/blog/luma-integration-case-study Machine-readable site index: https://meetwho.app/llms.txt