The continuous, behavior-informed matchmaking systems that had emerged the prior year matured further in 2025, with platforms incorporating richer data sources — professional social-network connections (where attendees opted to link an account), more granular real-time in-event behavior, and cross-event history for attendees who used the same platform across multiple conferences throughout the year. The result was matchmaking accuracy that improved substantially by most measures organizers tracked, alongside a parallel rise in attendee discomfort with just how much a recommendation revealed about what the system apparently knew.
What Made the Recommendations More Accurate
The core accuracy improvement came from combining data sources that had previously existed in isolation: an attendee’s stated interests from registration, their actual session-attendance behavior at the current event, and in some cases their broader professional network and cross-event history with the same platform vendor. Combining these signals let matchmaking systems make genuinely more specific, contextually relevant suggestions — not just “shares your industry” but “attended three sessions on the same specific sub-topic and has a mutual professional connection with you” — a level of specificity the earlier, more siloed data models couldn’t produce.
For platform vendors operating across many client conferences throughout the year, cross-event data accumulation gave an increasingly rich long-term behavioral profile for repeat platform users, improving recommendation quality at every subsequent event that user attended regardless of whether it was run by the same organizer.
Why Some Attendees Found This Unsettling
The same specificity that made recommendations more useful also made the underlying data collection more visible and, to some attendees, more uncomfortable. A recommendation explicitly citing a mutual professional connection or referencing behavior from a different conference run by an entirely different organizer made clear to attendees just how much cross-context data aggregation was happening behind the scenes — a transparency that, ironically, undermined some attendees’ comfort precisely because it made the system’s data reach visible rather than abstract.
This discomfort reaction illustrated a recurring pattern in personalization technology broadly: recommendation quality and attendee comfort don’t necessarily move together, and a system that becomes more accurate by drawing on more data can simultaneously become more alarming to the people whose data it’s using, even when every individual data source was technically consented to at the time of collection.
Platforms Responded With More Granular Controls
In response to this feedback, several matchmaking platform vendors introduced more granular controls letting attendees limit which data sources fed their own matchmaking profile — opting into session-behavior-based matching while declining cross-event history aggregation, for instance, rather than an all-or-nothing choice between full personalization and none at all. This mirrored the granular consent evolution that had already played out in the sponsor-data-sharing context, applied now to the matchmaking feature specifically.
Organizers Had to Balance Feature Marketing Against Attendee Comfort
Organizers promoting matchmaking features to prospective attendees faced a genuine messaging tension: emphasizing the feature’s sophistication and accuracy to encourage adoption risked the same specificity that made the feature appealing also making prospective users wary of just how much data-driven personalization was involved. Organizers who navigated this well generally emphasized the value delivered — better, more relevant connections — over the specific technical mechanism producing it, avoiding messaging that inadvertently highlighted the data-aggregation depth in ways that triggered discomfort before attendees had experienced the feature’s actual benefit firsthand.
The Cross-Event Data Aggregation Question Organizers Couldn’t Fully Answer
The specific feature driving the most attendee unease — cross-event history compiled by a platform vendor operating across many different organizers’ conferences — raised a question that individual organizers were poorly positioned to answer on their own: once a vendor holds a behavioral profile spanning a given attendee’s participation across a dozen unrelated conferences run by a dozen unrelated organizers, whose data-governance obligations actually apply, and to whom does an attendee direct a request to see, correct, or delete that aggregated profile? This is functionally the same cross-context data aggregation problem regulators and consumer-protection agencies had already been examining in the broader data-broker industry, where the same structural pattern — a single intermediary compiling behavior collected across many unrelated first-party relationships into one composite profile — has drawn sustained scrutiny for the same reason: individual consumers (or, here, attendees) have no direct visibility into how much of their behavior has been stitched together, since no single event they attended captured the full picture; only the platform vendor sitting across all of them did.
Organizers evaluating matchmaking vendors increasingly had to treat this as a genuine procurement question rather than an assumption to wave through: what does the vendor’s cross-event data retention and deletion policy actually say, does an attendee’s opt-out at one conference propagate to the vendor’s broader cross-event profile or only to that single event’s dataset, and does the organizer’s own attendee privacy policy accurately describe a data-sharing relationship that, in practice, extends well beyond the single event the attendee registered for. Organizers who pressed vendors on these specifics during procurement generally found meaningful variation in how seriously different platform vendors had built out cross-event governance controls — variation that wasn’t always visible from the matchmaking feature’s marketing materials alone.
Frequently Asked Questions
What data sources made 2025-era matchmaking recommendations more accurate?
Platforms combined registration profile data, real-time in-event behavioral signals, professional social-network connections, and cross-event history for attendees using the same platform across multiple conferences, producing more specific and contextually relevant suggestions than earlier, more siloed data models.
Why did some attendees find improved matchmaking recommendations uncomfortable?
Greater specificity made the underlying cross-context data aggregation more visible — a recommendation citing behavior from a different conference or a mutual professional connection revealed how much data reach was involved, which some attendees found unsettling even though each data source had been individually consented to.
How did platforms respond to attendee discomfort with data-driven matchmaking?
Several introduced more granular controls letting attendees limit which specific data sources fed their matchmaking profile, rather than an all-or-nothing choice between full personalization and none, mirroring the granular consent model already established for sponsor data sharing.
How did organizers navigate marketing a highly personalized matchmaking feature?
Organizers who managed this well emphasized the value delivered — better, more relevant connections — rather than the specific technical mechanism producing it, avoiding messaging that highlighted data-aggregation depth before attendees experienced the feature’s benefit directly.
For related coverage, see our piece on algorithmic attendee matchmaking. The structural pattern of aggregating behavioral data across many unrelated first-party relationships into a single composite profile — the same dynamic underlying cross-event matchmaking data — is examined in the Federal Trade Commission’s Data Brokers: A Call for Transparency and Accountability report.