What do I install on a custom site?

One asynchronous snippet in the page head. It auto-detects common events, and you can send custom conversions with a single line where auto-detection cannot see them, for example a WhatsApp click or a form submit.

Does it work without a store platform?

Yes. SetRoasFlow is platform-agnostic. Any website that can paste a snippet in its head can collect first-party events, build customer profiles, and activate them server-side.

Server-side tracking for any website

Most server-side tracking tools assume you run a store on a specific platform. Plenty of businesses do not. If you have a custom site, a headless storefront, a booking flow, a SaaS signup or a lead form, you still lose conversions to ad blockers and iOS, and you still deserve complete first-party data. SetRoasFlow is built for any website, not just Shopify or WooCommerce.

One snippet, collected server-side

You add a single asynchronous snippet to the page head. From there:

Common events are auto-detected, so page views and standard actions are captured without extra work.
A first-party cookie on your own domain keeps visitors recognizable across sessions, even under Safari's ITP.
Events are sent to the edge and delivered server-side to your destinations, where the browser cannot block them.

Where auto-detection cannot see an action, you send it explicitly with one line:

<script>
  SetRoasFlow('track', 'Lead', { value: 0, currency: 'USD' })
</script>

That covers the conversions that live outside a checkout: a WhatsApp click, a form submit, a demo request, a phone tap.

Why this matters on a custom site

A custom site is often where tracking is weakest, because there is no store platform filling gaps for you. Server-side collection changes that:

Ad blockers cannot stop a conversion that is recorded server-side.
iOS and Safari cannot shorten a first-party cookie the way they shorten third-party ones.
Every channel receives the same complete event, deduplicated against your browser pixel by a shared event id.

What you get

First-party customer profiles with identity resolution, built from your own events.
Server-side delivery to Meta, Google, TikTok, GA4 and more, plus sync to your CRM.
Raw event export to your own warehouse (BigQuery, Snowflake, S3 or a webhook), so you own the data.
Consent enforced at the edge, per visitor and region, with sensitive fields hashed before they leave.

The point of a customer data layer is that it is not tied to one platform. Collect once, on any website, and route that data everywhere you sell and market.