FAQ

Do ad blockers block Virling?

Some block requests to hosts or paths they know as analytics. Serving the script and /api/event from your own domain through a proxy helps, see Reverse proxy. A tested first-party proxy setup per platform is Not available yet. Payments are imported from your provider either way, so blocked visitors still count toward revenue, as Unattributed.

Does it run on an Intel Mac or Windows?

Not from a release build. Releases cover Linux x86_64, Linux arm64 and macOS on Apple silicon, and the Docker image is linux/amd64. Intel macOS and Windows builds are Not available yet. You can try building from source.

Can I track several sites?

Yes. Add each domain as its own site, with add-site or in the app, and use its domain in data-site. Each site has its own settings, payment connections and reports. Subdomains of a site are counted as that site.

Can I invite team members?

Not yet. Each site has one owner account. Team members and roles are Not available yet.

Can I import data from another analytics tool?

Not yet. Migrating from other tools is Not available yet. Payments are backfilled 90 days from your provider, but past visits only exist from when the script was added.

Why is my revenue Unattributed?

See Unattributed revenue. Most often checkout does not carry the virling_vid visitor ID.

Do I need a cookie banner?

That depends on your jurisdiction. Virling sets one first-party cookie, virling_vid. Cookieless mode sets none, at the cost of revenue attribution. See Privacy and consent.

Why does the script not track on my laptop?

It skips localhost, 127.* and [::1]. Add data-dev to the tag to test locally, and add a site for the domain your pages run on.

Is there an API?

Only the event endpoint for sending events. A read API is Not available yet.

How do I report a security problem?

Email security@virling.com. Do not open a public issue.