Frequently Asked Questions
Quick answers to common questions about setting up Metrivo, configuring checkout parameters, and tracking attribution.
Why are some of my transactions marked as 'Unattributed'?
Transactions appear as 'Unattributed' (with 'Unknown' confidence) when Metrivo receives a payment webhook but cannot find any matching visitor session, customer ID, or email hash in the database. To fix this, make sure you are passing `metrivo_session_id` or `metrivo_visitor_id` in your gateway checkout metadata, or sending the customer email so our email hash match can link the payment.
How do I test the tracking script on localhost?
The tracking script works on `localhost` just as it does in production. Ensure that your script tag contains the correct `data-site="<YOUR_WEBSITE_ID>"` attribute. All tracking requests will be routed to your backend API collector at `/api/track`. If you want to view a page without logging test events, append `?metrivo_ignore=true` to your URL query string.
Can I track multiple domains in a single Metrivo workspace?
Yes. In your Metrivo dashboard, you can add multiple websites. Each website will generate its own unique `data-site` tracking script snippet. Ensure that you insert the correct snippet on each corresponding domain.
How does email-based attribution work, and is it secure?
When a customer makes a payment, payment providers include the checkout email. Metrivo takes that email, normalizes it (trims whitespace, converts to lowercase), and hashes it using SHA-256 with a unique salt (`process.env.ENCRYPTION_KEY`). It then looks for a matching email hash captured by the tracking script when the user signed up or submitted a form. Raw, clear-text email addresses are never stored in our database.
What is the difference between 'high', 'medium', and 'low' confidence attribution?
High confidence means a payment was matched directly to a visitor session or visitor ID (using metadata passed to the checkout flow). Medium confidence means the match was made using a normalized email hash. Low confidence means no session or email matched, but the transaction payload itself contained UTM parameters or referrer metadata.
How often does the Revenue Leak Agent run?
The Revenue Leak Agent runs checks automatically in the background on a daily schedule, or you can trigger a manual check anytime from your dashboard.