Set up Revenue tracking
Register your website, install one tracker, connect consent, and verify visits and orders using the right data source.
Open Revenue setupRegister your website
Open Revenue and enter the website or store address you want to measure. Continue to setup to open the installation screen for that site.
Registering the domain does not install tracking. Collection starts only after the script is installed and the required analytics consent is granted.
Setup provides the public site key and script URL for your registered website. Copy these from your own workspace rather than another site or a generic example.
Choose one installation method
Setup provides HTML, Shopify, Tag Manager, and Next.js options. Choose the method appropriate for your website, or use Copy installation prompt to give your coding assistant the site-specific instructions.
| Platform | Where it goes |
|---|---|
| HTML | The shared template used by the pages you want to measure. |
| Next.js | The application layout, using the provided Script component example. |
| Tag Manager | A Custom HTML tag with the appropriate page trigger. |
| Shopify | The storefront theme. Orders need a separate integration. |
Do not install the same tracker both in your application and through Tag Manager. Duplicate installation can create duplicate page views.
Connect analytics consent
The provided installation snippets include data-consent="required". The tracker waits until your consent manager grants analytics consent.
After the tracker has loaded, pass consent changes to the tracker. Handle an existing saved choice as well as new choices and withdrawals. The calls below illustrate the API; your implementation must use the actual consent manager’s state.
// After the tracker is ready and analytics consent is granted:
window.adrise.consent(true);
// When analytics consent is withdrawn:
window.adrise.consent(false);A tracker waiting for required consent is different from a broken installation. Confirm the consent flow before diagnosing missing visits.
Choose how orders are reported
A page-view script cannot infer payment totals or refunds. E-commerce tracking needs an explicit order integration; a site without sales may only need visit tracking.
| Order source | How it works | Verification |
|---|---|---|
| Browser confirmation | Report the completed order from your confirmation page. | Unverified / browser reported |
| Signed server event | Send the confirmed payment from your backend using the signing instructions in Setup. | Server verified |
| Shopify | Configure the supported Order payment webhook and signing secret; add refund handling as described in Setup. | Verified Shopify events |
Report actual completed orders with their real currency and amount. Reuse the same order ID on retries. Keep server signing secrets on the server; they do not belong in browser code.
Verify the installation
Use a separate test site for synthetic purchases so you do not contaminate production reporting.
- Check that the script URL from Setup loads successfully with HTTP 200.
- Grant analytics consent on the website and navigate to another page.
- Check that the collection request is accepted and Setup shows received activity.
- Review Visitors for the selected site and period. If an automated test is missing, check Show crawler traffic.
- For a store, confirm a test order through the chosen integration and inspect Transactions.
- Repeat the same test order ID and confirm it does not add a second order.
- Check the order’s verification label and test any refund integration you installed.
Diagnose missing or different numbers
If visits are missing, check the selected site, actual installed site key, consent, script loading, date range, and crawler filter first.
If visits arrive but sales do not, inspect the order integration. The storefront script alone does not mean that order reporting is configured.
If Meta and Revenue disagree, compare their date ranges and measurement methods. Meta’s attributed conversions and the website ledger are distinct sources; neither should be silently substituted for the other.
The Revenue workspace includes detailed installation documentation and site-specific snippets. Use those for exact server signing and platform configuration steps.