Skene
Product
Pricing
Docs
Blog
About
Log InSign up
ProductPricingDocsBlogAbout
Log InSign up
Skene subpage background texture
Resources / Glossary

Analytics call

A statement in your code that records an event. In a Supabase-first setup, a write into a Postgres table, like `supabase.from('events').insert(...)`.

CallsAlso called: analytics event call, tracking call, event call

About this term

This page is part of the Skene analytics instrumentation glossary. Use it as a reference when writing specs, dashboards, or playbooks.

Canonical glossary index: /resources/glossary

Glossary

Glossary

Analytics callEvent namePayload (event properties)Identify callEvent taxonomyInstrumentation surfaceBaseline manifestInstrumentation driftSemantic diffRemoved eventRenamed eventMoved eventAltered payloadConditional firing changeCustomer Data Platform (CDP)Schema registryMCP (Model Context Protocol)Coding agentSide effectFunnelConversion eventActivation eventCohort

Definition

An analytics call is the statement in your application code that records an event somewhere it can be analysed. `supabase.from('events').insert({ name: 'checkout_completed', plan_tier })` is an analytics call. So is an `upsert`, an `rpc(...)` that records an event, or a server-side insert into an event table.

Why it matters

Every dashboard, funnel, and retention chart your team trusts is downstream of these calls. If a call disappears, gets renamed, or fires from a different code path, the dashboard keeps drawing - just from worse data.

Related terms

  • Event name
  • Payload (event properties)
  • Instrumentation surface
Skene

Product

How it worksFeaturesSupabaseArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

AboutOpen sourceContactPrivacyTerms
© 2026 Skene. All rights reserved.
Privacy PolicyTerms of Service
Skene