DataSpice documentation

Setting up DataSpice is one script tag in your page head, and everything after that is optional. This page is the complete setup guide: installing the web tracker, what it does and does not send, connecting Apple App Store Connect and Stripe, and the limits worth knowing before you rely on it.

Installing the web tracking script

Add one tag to the head of every page you want measured. The site key is issued when you create the site in your workspace, and it identifies the site rather than authenticating anything. It is a public value. The server authorises an event on the request's origin, never on knowledge of the key.

<script defer
        src="https://backend.dataspice.net/tracker/v1.js?site=YOUR_SITE_KEY&domain=yourdomain.com"
        data-site="YOUR_SITE_KEY"></script>

No consent banner goes in front of it. The script sets no cookies for analytics, so there is nothing for a banner to ask permission for, and gating it behind one only loses you the visitors who decline.

What the tracker sends, and what it drops

The tracker sends the path, the referrer reduced to its origin, the screen size, and enough of the user agent to name a browser and a device type. The country comes from the connection at the edge and the IP address itself is hashed and never retained.

What the tracking script sends and what it discards
Field	What is sent
Page path	The path only. Query strings are dropped in the browser before the request leaves.
Referrer	Reduced to its origin. The full referring URL is never sent.
Country	Derived from the connection. No city, no coordinates.
IP address	Hashed, used to resolve a session, and never stored.
Cookies	None are set for analytics purposes.
Cross-site identity	None. There is no profile that follows somebody between sites.

Verifying the script is working

Open your site in a normal browser window, not localhost. The tracker refuses to report from localhost without an explicit opt-in, and the API rejects any origin that is not the registered domain.
Check the live view in your workspace. A pageview should appear within a few seconds.
If nothing appears, confirm the domain on the tag matches the domain registered for the site key exactly, including whether it has a `www`.
Check your content security policy. A site with a strict `script-src` has to allow the tracker host explicitly.

Connecting Apple App Store Connect

Create a read-only App Store Connect API key in your own Apple account and add it in workspace settings. DataSpice uses it to read the sales and downloads reporting Apple publishes; downloads, proceeds and the country breakdown then appear beside your web traffic.

The credential is held only by the backend and never reaches the browser. The integration is Apple only, with no Google Play equivalent, and it is entirely optional.

Connecting Stripe or RevenueCat

Connect one revenue source per project: Stripe for a web SaaS, or RevenueCat if your money comes from mobile subscriptions across stores. It is a read-only authorisation from workspace settings and it is what lets a paying customer be read back to the acquisition source that produced them.

Paddle, Lemon Squeezy, Chargebee and Braintree are not supported.

Embedding the live country globe

The globe is a live country breakdown you can put on your own site as an iframe. Because it is built on the same cookieless data as the rest of the workspace, embedding it adds no tracking to the page it sits on.

The embed URL is shown in the website's settings in your workspace.

Limits worth knowing before you rely on it

No data export and no customer-facing API key. The API authenticates with a session cookie, so it is not something you can call from your own code. If a portable copy of your numbers is a requirement, DataSpice does not meet it today.
Apple only on the store side. There is no Google Play integration.
Stripe or RevenueCat only on revenue.
Hosted only. There is no self-hosted build.
No behavioural analytics. No funnels, cohorts, session replay or feature experiments.
No ad-platform integration. Conversions are not fed back to Google Ads or Meta.

How the trial works

The trial runs fourteen days and takes no payment method to start, so nothing can be charged before then and there is no card on file to bill you by surprise. DataSpice asks for a card on day fifteen.

Everything is available during the trial with your own real data, which is the only way to tell whether the numbers are useful to you.

Start free See the tiers