Authenticate

Why Authenticate matters for B2B marketing leaders

The VP Marketing at a Series B passkey vendor weighed Authenticate against a 1,400-person identity show in Vegas the same week. The 82-person FIDO Alliance gathering at the Park Hyatt Aviara won the budget. Twelve weeks later her team had three closed deals attributable to that decision and a CFO who started asking, by name, when Authenticate was on the calendar again. The reason is simple: Authenticate is the FIDO Alliance’s working group conference. Almost every attendee is a deciding voice on passkey rollouts, FIDO2 deployments, or workforce IAM modernization at their company.

If your ICP is a Director of Identity, a Head of Workforce IAM, a Principal Identity Architect, or a Product Manager owning passkeys at a financial services firm, healthcare network, or large enterprise, this is one of the highest-density practitioner identity rooms on the calendar. Our 82-row publicly-sourceable list reads like the credentials list of every relying party that ships passkeys to production. Vendelux and Bizzabo will list Authenticate as a “small identity event” and recommend something larger. That misreads the room. The smaller the identity room, the higher the practitioner concentration.

Three days at the Aviara, mostly in working-group sessions and small-room demos. The poolside dinners are where the technical roadmap conversations actually happen.

Who attends Authenticate

The 82-row publicly-sourceable list concentrates around identity practitioners and architects:

• Relying party identity architects and practitioners (Apple, Google, Microsoft, Meta, banks, healthcare, government): roughly 30-40% of the room. The highest-use cluster for passkey, FIDO2, and IAM vendors.
• Workforce IAM and customer IAM product leaders at financial services and healthcare: 18-22%. The buyers for IAM platform modernization and passkey rollouts.
• Government identity attendees (DHS, NIST, GSA, state DMV identity programs): 8-12%. Useful to brief, sometimes useful to sequence depending on your federal motion.
• Authenticator and security key vendors (Yubico, Google Titan-related, RSA, Thales): 8-12%. Partnership conversations more than buyer conversations.
• Standards body and FIDO Alliance staff: 6-10%. The infrastructure of the event.
• Browser and platform engineering teams: 4-8%. Technical depth conversations.

For a Series A or Series B IDV, IAM, or passkey vendor, the working list at Authenticate is closer to 40-60 named contacts across 30-50 named accounts. Almost every contact in the working list is either a current buyer or a peer-bank reference in a buying conversation.

The five-stage pipeline applied to Authenticate

Authenticate is practitioner-driven. The conversations that produce pipeline are the ones grounded in real deployment problems: passkey enrollment friction, account recovery gaps, SP-side metadata management, FIDO2 backwards-compatibility with legacy SAML.

Source. Pull the FIDO Alliance member roster and the published Authenticate attendee list five weeks out. Cross-reference against your IAM-and-IDV TAL: the relying parties that actually ship passkeys to production, the financial services firms running enterprise passkey rollouts, the healthcare networks with workforce IAM modernization programs. The 82-row publicly-sourceable list ICP-matched against a typical IAM TAL produces 40-60 working contacts.

Enrich. Score on three axes: relying party status (currently shipping passkeys, or 6-12 months from shipping), seniority (Director and above for buyers; Principal Engineer and above for architects), and active-vendor signal (recent IAM platform job postings, FIDO2 deployment talks at prior conferences). Apollo email coverage on identity practitioner contacts runs around 80-85%, but LinkedIn Sales Navigator coverage is denser for this audience.

Sequence. Two cadences. Architect-and-practitioner: a 4-touch sequence anchored to a specific FIDO working group or a real deployment problem (enrollment friction, account recovery, hybrid SAML/FIDO2). Director-and-VP: a 3-touch sequence anchored to a peer reference or a regulator anchor (NIST 800-63-4, OCC’s authentication guidance for banks, HIPAA’s emerging passkey allowances). Avoid generic “we should meet at Authenticate” openers; this audience filters those out instantly.

Capture. The Aviara has no traditional booth floor. Sponsorships are working-group anchors, demo-room slots, and reserved poolside cabana meeting space. Use a mobile capture flow that maps voice notes from each meeting to your Salesforce or HubSpot Campaign Member the same business day. Authenticate produces 20-35 high-quality scheduled meetings across three days for an active sponsor.

Attribute. Tag every Campaign Member with the Authenticate campaign and a buyer-type custom field (RP-architect, IAM-buyer, partner, government). Run one Salesforce report 48 hours after the conference closes that segments sourced pipeline by buyer type. Identity deals close on 6-12 month cycles, so plan the attribution review at 60 days and 180 days, not just 30 days.

Booth and meeting strategy for Authenticate

For B2B SaaS vendors selling IDV, IAM, passkeys, or workforce identity:

• Sponsorship tier: There is no traditional booth floor. Sponsorships include working-group anchors, demo-room slots, and lounge or cabana sponsorships. Demo-room slots produce the densest practitioner conversations.
• Location: Pay for placement near the FIDO Alliance working group rooms. The lobby and poolside lounge sponsorships are where the side conversations happen.
• Staffing: A senior engineer or product manager (not just AEs) at every meeting. The buyers here ask architecture-level questions that need engineering-level answers within the first three minutes.
• Side meetings: Authenticate’s evening receptions are where the actual deployment-roadmap conversations happen. Book a 6-8 person dinner Tuesday or Wednesday night with your top relying-party targets. The Aviara’s on-property restaurants or one of the Carlsbad coastal venues.

Recommended exhibitor tier: a working-group anchor plus a demo-room slot plus a sponsor dinner typically runs 25-50K all-in for the three-day program, before staffing and travel.

How Luminik runs the Authenticate motion

Authenticate is an identity practitioner show. The five-stage pipeline (source, enrich, sequence, capture, attribute) runs identically to the IDV motion documented in our Fintech IDV case study where a 175-person Series A IDV vendor produced 2M attributed pipeline and 270+ meetings across 15 events.

We run the same five-stage motion as documented in our case studies. See the Fintech industry playbook for the underlying motion and the for-marketing-leaders page for the budget-defense framing. Run on the Salesforce, Apollo, and HubSpot accounts you already pay for.

FAQ

How many attendees does Authenticate actually have?

Our publicly-sourceable list for the 2025 program at the Park Hyatt Aviara is 82 rows. ICP density for B2B SaaS vendors selling IDV, IAM, or passkey tooling into relying parties runs around 18% of that working list (IDV industry default), but Authenticate’s invitation-led shape skews much more buyer-concentrated than a typical conference floor.

When should I start sourcing for Authenticate?

Five weeks out. The FIDO Alliance member companies plan the trip 4-6 weeks ahead, and the practitioner side fills calendars in the two weeks immediately before the conference.

What is the typical sponsorship cost?

A working-group anchor plus a demo-room slot typically runs 15-30K base. All-in costs including a sponsor dinner and staffing run 25-50K for the three-day program.

How does Authenticate compare to Identiverse or Gartner IAM Summit?

Identiverse is broader (1,400+ attendees) and skews IAM platform vendors and analyst-led sessions. Gartner IAM Summit is analyst-led and skews enterprise IAM buyers. Authenticate is the working-group conference for FIDO Alliance members and the relying parties shipping passkeys. For a passkey or IDV vendor, Authenticate produces denser practitioner conversations per dollar than the larger shows.

Should I run separate sequences for architects vs buyers?

Yes. Practitioners and architects respond to deployment-problem-anchored outreach (enrollment friction, account recovery, hybrid SAML/FIDO2). Directors and VPs respond to peer-reference and regulator-anchored outreach (NIST 800-63-4, OCC authentication guidance). Two sequence templates minimum.

Is government identity a separate motion?

Yes. DHS, NIST, GSA, and state DMV identity programs operate on different procurement cycles (federal SBIR or GWAC) and different evaluation timelines. If your product has a federal motion, treat the government attendees as a separate sub-segment with its own sequence and a longer follow-up window.

How do I write Authenticate attribution back to Salesforce?

Tag every Campaign Member with the Authenticate campaign and a buyer-type custom field. Run reports at 48 hours, 60 days, and 180 days. Identity deals close on 6-12 month cycles, so the attribution model needs to track first-touch through close.