What are the current limitations of Vercel Analytics when tracking custom user events across multiple subdomain deployments?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What are the current limitations of Vercel Analytics when tracking custom user events across multiple subdomain deployments?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Vercel Web Analytics custom events limitations cross subdomain deployments domains project analytics events Google ↗
site:vercel.com/docs/analytics custom events track event limitations domains subdomains Google ↗
- Pricing for Web Analytics · vercel.com
- Using Web Analytics · vercel.com
- Tracking custom events · vercel.com
- Vercel Web Analytics · vercel.com
- Privacy and Compliance · vercel.com
- Split Web Analytics data by any dimension · vercel.com
- Filtering Analytics · vercel.com
- Public Web Analytics API now available · vercel.com
- Documentation · posthog.com
- Documentation · amplitude.com
- Cross-domain measurement documentation · support.google.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Vercel Web Analytics custom events limitations cross subdomain deployments domains project analytics events OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
site:vercel.com/docs/analytics custom events track event limitations domains subdomains OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |