Algolia Events Insights

Use this skill whenever user behavior needs to power analytics, personalization, Recommend, dynamic re-ranking, or measurable search quality.

Customer-Facing Standard

• Start with one validated result-click event and one validated primary conversion before expanding.
• State which owner controls each event: frontend, backend, analytics/tag manager, or data pipeline.
• Use public academy.algolia.com for learning alignment and public algolia.com/doc for current implementation guidance when source-backed context is needed.
• When an Academy metadata reference pack is available, use only its title, url, course, module, learning_objectives, and updated_at fields for structure. If it is stale or no match exists, fall back to live Academy/docs lookup. Do not treat cached metadata as course content or implementation authority.
• Do not require custom Academy/docs access; use customer-provided sources only as optional context.
• When live Algolia data, analytics, index inspection, settings changes, or account actions are needed, use Algolia MCP, the Algolia CLI, or official Algolia skills for the live operation, then apply this skill to interpret results and validate the customer-ready implementation path.
• Produce an event taxonomy, payload checklist, duplicate-event rule, and validation plan.
• Distinguish between events that are merely ingestible and events that are usable by analytics, Dynamic Re-Ranking, NeuralSearch, Recommend, personalization, or revenue reporting.
• Choose the implementation path deliberately: InstantSearch/search-insights first when possible, GTM for constrained marketing-managed frontends, Segment/CDP for centralized pipelines, and backend ownership for final server-side conversions.

Official Companion Skills