GrainQL

• It collects page views, clicks, scroll depth, heatmaps, DOM snapshots, sessions, and attention without tracking code.
• It records the custom events that your code sends, with properties, and it identifies users.
• It stores user properties and serves remote configuration values to your code.
• It shows trackers, tracks, heatmaps, and goals in the dashboard.
• It answers questions about your data with Neo, from any page of the dashboard.
• It returns your events over the Query API.
• It answers questions from an AI assistant over the MCP server.

​

Surfaces

​

Two paths

​

A first event

<script src="https://tag.grainql.com/v4/your-tenant-id.js"></script>
<script>
  GrainTag.track('signup_clicked', { location: 'hero' });
</script>

​

The documentation

​

What GrainQL does not do

• GrainQL Tag has no remote configuration and no React hooks. Both are in Analytics Web.
• Analytics Web takes no DOM snapshots and runs no dashboard trackers. It collects page views and heatmap clicks by default (enableAutoPageView, enableHeatmapTracking).
• GrainQL Tag has no authentication strategy. It sends events with the tenant alias only.
• GrainQL sets no cookies and stores no persistent ID until your code calls consent.grant().
• The Query API is not available without a paid plan. Read Plans and limits.
• The MCP server is read-only. An assistant cannot send events or change a configuration.

​

What wins on conflict

​

Start here