FAQ
Does Revly require a cookie consent banner?
It depends on which tracking mode you use, and you configure this per site. In the default cookie mode, Revly sets two first-party cookies (_revly_vid and _revly_sid). Depending on your jurisdiction (GDPR, LGPD), a consent banner may be required. In cookieless mode, no cookies are set: visitor IDs are derived from a daily-rotating server-side fingerprint, so analytics can run without a consent banner. You can switch modes at any time in your site's Privacy Settings. See Cookieless Mode for details.
Do I need to configure anything for single page apps?
No. The tracker automatically detects client-side navigation in React, Next.js, Vue, and any framework that uses the History API.
Does the tracker work in incognito/private mode?
Yes. If local storage is unavailable, the tracker falls back to in-memory identifiers. Tracking still works — the visitor just won't be recognized across sessions.
What counts toward my event quota?
Pageviews and custom events count toward your quota. Session ends, heartbeats, and identify calls do not.
Can I proxy events through my own domain?
Yes. Set the data-endpoint attribute to your proxy URL. This can help with ad blockers that block third-party analytics scripts.
Does the tracker affect my site's performance?
Barely. The script is ultra-lightweight, loads with defer, and uses sendBeacon for non-blocking event delivery. It has zero impact on your Core Web Vitals.
My custom events are not showing in the dashboard. What should I check?
Two things to verify. First, check whether the Event Allowlist is enabled under Settings → Allowed Events. If it is, the event name must appear in the list or it will be silently dropped before reaching the database. Second, the Goals section only shows events that have a matching Conversion Goal configured — the individual visitor timeline always shows all collected events regardless of goals.
Do I need to create a goal to track a custom event?
No. Custom events are collected whenever you call window.revly.track(), regardless of whether a goal exists. Goals are only needed to see aggregated conversion metrics — conversion rate, unique converting visitors, and source attribution. Without a goal, events still appear in each visitor's individual timeline.