RevenueUIDocs
Login

RevenueUI documentation

Install the tracking script

Add the generated RevenueUI script to your website and verify that it is collecting activity.

Copy the generated embed code

Open the website setup flow and copy the embed code shown for that website. A generated snippet has this shape:

<script
  defer
  src="https://your-tracker-origin.example/tracker.js"
  data-public-key="your-website-public-key"
></script>

Use the exact tracker URL and public key shown in RevenueUI. The values above are illustrative and should not be pasted into a site.

Place it in the head

Add the script inside the document <head> on every page that should be measured. In an application framework, place it in the shared root layout or document template so navigation is covered consistently.

Keep the defer attribute. Do not expose a payment-provider secret or any server credential in this browser snippet; the website public key is the only RevenueUI identifier it needs.

Use consent-required mode

When your consent policy requires cookies to wait, copy the consent-required version:

<script
  defer
  src="https://your-tracker-origin.example/tracker.js"
  data-public-key="your-website-public-key"
  data-require-consent="true"
></script>

See Consent and cookies for the resulting accuracy tradeoffs.

Verify the installation

  1. Deploy the change to the domain registered in RevenueUI.
  2. Open the site in a normal browser and visit more than one page.
  3. Return to the website dashboard and check its latest event status and analytics.

If the script is present but events do not arrive, check browser content blockers, the generated URL, the registered domain, and the consent state.