The Food & Wine Classic in Aspen opened today. Five thousand people who paid $2,950 per ticket are gathering in downtown Aspen for cooking demonstrations, grand tastings, and alpine escapes. People calculated the math: each attendee generates 469 times the revenue of an average digital visitor.
Here's the technology question no one is asking: where does the attendee data go?
Three Identity Surfaces
People Inc now has three distinct surfaces where customers appear — and each one runs on different infrastructure with different owners.
The pattern is backwards. The highest-value customers have the least visibility. A person who spends $2,950 to attend the F&W Classic — who has proven, with cash, that they care about food content — is invisible to the system that sells audience segments to advertisers.
What Amex Knows
American Express and Resy are presenting sponsors through 2028. This isn't a logo on a banner. Resy's ResyOS handles ticketing, experience registration, and payment processing. Amex gates presale access by cardholder tier — Platinum and Centurion members get first access and exclusive experiences.
What the Amex/Resy stack captures per attendee:
- Full identity (name, email, payment credentials)
- Cardholder tier (spending power signal)
- Experience preferences (cooking demos vs. tastings vs. alpine escapes)
- Dining history across Resy's restaurant network
- Merchant category affinity from card data
- Dietary and lifestyle signals from reservation patterns
New this year: "Alpine Escapes" — pre-event registration for small group activities (yoga, hiking, meditation). Resy is building experience ecosystem orchestration, not just ticketing. Each new feature generates another data surface that Amex owns and People Inc doesn't.
This is a phenomenal first-party data asset. It just doesn't belong to People Inc.
The Pipeline That Doesn't Exist
D/Cipher is built to understand content and match it to audience segments. It reads pages, classifies them taxonomically, and sells contextual targeting to advertisers. This works on the web surface because People Inc owns the content, the pages, and the behavioral data.
Events break this model. There's no page to classify. There's no cookie to track. There's a person standing in a tent in Aspen holding a glass of Burgundy and a $2,950 receipt, and D/Cipher doesn't know they exist.
What would need to exist to close this gap:
Required Data Pipeline: Events → D/Cipher
- People Inc–owned registration layer — either replace Resy or contractually guarantee data passback (email, preferences, attendance). Resy has open APIs and webhooks, but the data rights question is commercial, not technical.
- Identity resolution — match event attendee emails to web/app profiles. Does this F&W Classic attendee also browse Allrecipes.com? Does their Resy dining history correlate with their content consumption?
- CDP ingestion — event attendance as a first-party data signal flowing into the customer data platform, with privacy-compliant consent captured at registration.
- D/Cipher segment activation — "F&W Classic 2026 attendees" as a targetable audience segment. Advertisers pay premium CPMs for verified high-intent food enthusiasts.
- Measurement loop — attribution showing revenue lift when event attendee segments are activated in programmatic campaigns.
None of this exists. The data pipeline from People Inc's highest-ARPU surface to its ad technology platform is a gap, not a system.
The Timing Problem
This gap is widening in both directions simultaneously.
On the events side, the portfolio is growing. People acquired Hot Luck in Austin (June 16). The F&W Classic runs in both Aspen and Charleston. Best New Chefs events are expanding. More events means more high-value attendees flowing into Amex's data lake instead of People Inc's.
On the infrastructure side, the industry is solving this problem without them. Databricks launched CustomerLake on June 16 — an "agentic CDP" that unifies customer data across surfaces, resolves identity, and activates audiences, all with AI agents operating continuously. It's in private preview, aimed exactly at the multi-surface identity problem People Inc faces. The concept of a platform that automatically connects a physical event attendee to their digital footprint and activates that connection for advertising — that's what CustomerLake is designed to do.
Meanwhile, the ad tech stack going agentic at Cannes next week (PubMatic Decision Fabric, Hearst AURA IQ, DV Neura with MCP) can only target audiences that exist in the system. Agentic buying agents will be able to construct and activate audience segments autonomously — but only from data sources they can access. If event attendees aren't in D/Cipher, they aren't in the auction.
The Recommendation
People Inc doesn't need to fire Amex. The sponsorship revenue and operational expertise are real. But the data relationship needs to change from extraction to partnership.
Step one: Negotiate data passback rights in the Resy/Amex contract before the 2028 renewal. Hashed emails, attendance data, and experience preferences flowing back to People Inc's CDP. Resy's API architecture supports webhooks and downstream integrations — the technical capability exists. The question is whether the commercial terms allow it.
Step two: Build an owned registration layer that wraps around Resy. A Food & Wine account that's required for event access, collects consent, and creates a persistent identity linking events to web to app. This gives People Inc the data without breaking the Resy operational dependency.
Step three: Connect that identity to Graphene-Selene. An F&W Classic attendee who also reads recipe content on Allrecipes creates a cross-surface signal that D/Cipher can monetize. The knowledge graph already maps content relationships — extending it to map customer relationships across surfaces is the same architecture at a different layer.
The guest list exists. Five thousand names, verified with credit cards, rich with preferences. It's the most valuable first-party data asset People Inc generates. It just lives in someone else's system.