PRACTICAL GUIDE · VIXI TEAM
Six steps to structure a review: what to check, which evidence to keep and which conclusions to avoid. VIXI methodology updated September 8, 2026.
“Did this sale reach HYROS with the correct amount?” is more useful than “Is my tracking working?” An agreed test tells you which evidence to look for and what the result means.
This guide organizes the review; exact installation steps depend on your tools. A public website review cannot confirm internal events or server-side delivery.
See anonymized report examples →Record the accounts, domains, ad sources, CRM and payment provider in scope. Align date ranges, time zone, currency, the definition of a sale and the attribution window.
Evidence to keep: A journey map and the settings used in each report.
Mistake to avoid: Comparing revenue across different dates or models and treating the difference as a fault.
Review installation on the relevant funnel pages and test the URL that actually receives traffic. A verified domain alone does not demonstrate that a lead is captured correctly.
Evidence to keep: The tested page, installation status and test-lead outcome.
Mistake to avoid: Calling the setup complete after seeing a verified domain.
Use an identifiable test lead and follow it through the form, CRM and HYROS. Check the source and the stages that define a qualified lead.
Evidence to keep: The test time and corresponding records in each system.
Mistake to avoid: Assuming a submitted form proves that every destination received the lead.
Trace an authorized test transaction or a record the team can review. Check amount, currency, date and identity in the systems in scope. Define renewals and refunds separately where relevant.
Evidence to keep: Source and destination records, with identifiers kept in a private working record.
Mistake to avoid: Mistaking a checkout visit for a confirmed purchase.
Document which event leaves each source and which platform receives it. Examine retry and duplicate handling where browser, server or integration sources overlap.
Evidence to keep: An event map, applied rules and the outcomes of agreed tests.
Mistake to avoid: Enabling multiple sources without checking whether they represent the same conversion.
Classify each item as verified, access needed or pending test. Assign the next action, its owner and the criteria for completion.
Evidence to keep: A report connecting each finding to evidence, expected impact and a next action.
Mistake to avoid: Presenting a recommendation as if it had already been implemented and verified.
For opt-in capture failures, HYROS documentation includes checks for the account, script and landing page. Follow the instructions for your platform.
HYROS: troubleshooting the tracking event ↗Share screenshots and records only through channels agreed with your team. Remove customer data from any public example.
GUIDES FROM THE VIXI TEAM
A practical reconciliation guide for HYROS, Shopify, Stripe and your CRM: align report definitions, trace transactions and identify what needs fixing.
Read guideInvestigate duplicate HYROS revenue across checkout integrations, Stripe, webhooks and n8n. Map event sources and verify a repair without losing legitimate sales.
Read guideTHE NEXT STEP
Share your funnel and get an initial report by email within 24 hours.
