How does AITENDLY decide what is relevant to a visitor?

AITENDLY estimates relevance by comparing the visitor’s role and company with the content in the event program. When a custom event widget collects additional event-specific answers, AITENDLY can use those answers as well. It then prioritizes the sessions, exhibitors, workshops, speakers, tracks, and other opportunities that appear most relevant.

Which visitor information does AITENDLY use?

By default, AITENDLY uses the visitor’s role and company.

A custom event widget can also ask additional questions relevant to the specific event, audience, or program.

AITENDLY uses only the answers actually collected through the event widget when creating the personalized preview.

Which event information does AITENDLY use?

AITENDLY uses the content available in the organizer’s existing event program.

Depending on the event, this may include titles, descriptions, speakers, tracks, formats, intended audiences, dates, times, locations, exhibitor descriptions, product categories, booth numbers, expo themes, and other structured information.

How are the visitor and event information compared?

AITENDLY looks for contextual connections between the visitor information collected and the information available in the event content.

It then prioritizes program items that appear more relevant to that visitor and uses them to create a focused agenda preview.

This is an estimate of relevance, not a claim that one recommendation is objectively correct for every visitor.

What affects recommendation quality?

Recommendation quality depends on both sides of the comparison.

More specific visitor context can help distinguish between different needs, while clear session descriptions, detailed exhibitor information, useful categories, and accurate program data make the event content easier to interpret.

When the available information is vague, incomplete, or very similar across many program items, the recommendations may be broader or less precise.

Related questions

Published:
Last updated:

← Back to the AITENDLY Knowledge Base