A conference, webinar, meetup, or other event, whether hosted or attended.
An event, in marketing, is an organised gathering a company runs or joins to reach an audience: a conference, a webinarWebinarCustomer EducationA live or recorded webinarView reference →, a product launch, a field dinner, a trade-show booth. It is one of the few channels where a prospect gives a brand real time and attention in one block. The standing tension is that events are expensive and hard to measure, yet teams keep coming back to them because the attention they buy is the kind digital channels struggle to match.
This is the marketing sense of "event," a deliberate gathering aimed at demand, distinct from the analytics sense of an event as a logged user action. The two share a word and nothing else, and conflating them in a data modelData ModelData & AnalyticsA data model or schemaView reference → is a classic mistake.
Events as a demand channel matured under the banner of field marketing, the practice of meeting prospects in person within a region or segment, then expanded into what is now called event-led growth: treating events as a primary engine for pipeline. Practitioner accounts describe field marketing as a strategic, pipeline-accountable function, with its own targets and attribution. The shift was from "we should have a booth" to "events are a channel with targets, attribution, and a cost per lead like any other."
The format mix moved hard during and after the pandemic and then settled into a blend. Industry surveys put the current split at roughly 60% in-person, 35% virtual, and a small slice hybrid, with in-person attendance recovering and small regional field events growing fast. Virtual events trade depth of engagement for reach and lower cost, in-person events trade scale for the conversion power of a face-to-face conversation, and most programmes now run both deliberately, matching format to the stage of the funnelFunnelGrowthA conversion funnel tracking user progressionView reference → they are meant to move.
A B2B software company runs a regional field event: a half-day workshop in three cities for forty invited target accounts each. The economics are unforgiving on paper, with venue, catering, and staff time running to tens of thousands per city. The justification is the quality of the room. These are named accounts the sales team already wants, gathered for three hours of hands-on time with the product and a peer-led talk.
Each city produces a clean line from gathering to pipeline. Of 120 attendees across the three cities, the events generate sixty-two qualified leads, because attendance plus an in-session demo request is a far stronger buying signal than a whitepaper download. The recordings and a written recap then become content piecesContent PieceContent & KnowledgeA piece of content (article, video, etc.)View reference → that extend the event's reach to the accounts that could not travel. One event feeds two channels: the room itself, and the content it leaves behind.
In the Unified Product Graph, EventMarketingA marketing event sits in the marketing domain as a demand-generation activity, kept firmly separate from any telemetry notion of an event. It is hosted from two directions: eventMarketing StrategyhostsEventhierarchy ties it to the plan that called for it, and marketing_strategy_hosts_eventProducthostsEventhierarchy records the product behind it. Its payoff is captured by product_hosts_eventEventgeneratesLeadcross-domain, the edge that makes an event accountable for the pipeline it produces, beyond a turnout figure. Modelling the event as a node with a typed edge to the leads it produces, and recognising the webinar as a narrower neighbour, lets a team compare formats on the same footing and answer the question every events budget faces: which gatherings actually generated qualified demand.event_generates_lead
Type-specific fields on BaseNode
event_typestringFormat of the event
event_datestringDate of the event (ISO format)
locationstringVenue or virtual platform
attendee_countnumberNumber of attendees
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
5 phases — initial: planning · template: OPERATIONAL
3 edge types connected to this entity.
product_hosts_eventmarketing_strategy_hosts_eventevent_generates_lead