RevenueUIDocs
Login

RevenueUI documentation

Troubleshooting

Diagnose missing traffic, incomplete attribution, revenue connection errors, and analytics differences.

No traffic appears

Check the following in order:

  1. The generated script is present in the deployed page <head>.
  2. Its src and data-public-key match the website's current embed code.
  3. The page is served from the domain registered for that website.
  4. A content blocker or browser policy is not blocking the tracker request.
  5. If consent is required, test the state after consent is actually granted.

Use browser developer tools to confirm that tracker.js loads and that collection requests are not failing.

Revenue appears but has no visitor

This usually means the payment was imported correctly but did not contain a valid RevenueUI visitor or session identifier. Confirm that your backend reads the first-party cookies and copies the identifiers to Stripe metadata when it creates the payment or subscription object.

Consent-required mode can also limit identifier availability before consent. RevenueUI does not assign an unrelated visitor to fill the gap.

Stripe cannot connect

Create the restricted key from the link in RevenueUI so it receives the required read and webhook permissions. Confirm that the key belongs to the intended test or live account and has not been revoked.

The form verifies the key before it stores the connection. Use the returned field error rather than repeatedly submitting a broader secret key.

A Stripe webhook was deleted

Disconnect the provider while keeping imported revenue, then reconnect. Manual endpoint recreation does not restore signature verification because the signing secret changes.

Numbers differ between reports

Before comparing values, check:

  • The selected website and reporting period.
  • The reporting timezone.
  • The selected currency.
  • Whether you are comparing all imported revenue with attributed paying visitors.
  • Whether a metric is collected revenue or expected trial value.

These scopes are intentionally distinct and should not be combined without preserving their meaning.