HYROS revenue does not match your CRM or checkout?

1. Write down the comparison rules

Keep a copy of each report and its settings before changing the setup. Include account, date range, time zone, currency, included products, payment status and the definition of revenue. A CRM opportunity value is not proof of a collected payment.

Shopify documents differences between sales reports and order exports, including how returns, refunds and reporting dates are represented. Those differences must be reconciled before treating a lower total elsewhere as missing tracking.

Reference: Shopify: sales reporting discrepancies ↗

2. Build a small transaction sample

Use a handful of paid orders that your team is authorized to inspect. Include an ordinary purchase and any relevant edge cases, such as a deposit, renewal or refund. Keep customer identifiers in the private working record.

For each transaction, record the source order or payment ID, timestamp, amount, currency, event source and corresponding HYROS record. A missing source record, a missing destination record and a missing ad source are three different findings.

1. Confirm the payment succeeded in the source system.
2. Find the corresponding sale in HYROS using the available private identifiers.
3. Compare amount, currency and date before investigating channel credit.
4. Record whether the difference is explained, reproducible or still needs access.

3. Separate capture from attribution

A sale can be present in HYROS while its source is unclear. In that case, investigate the lead journey and identity connection. Reimporting a sale that is already present can make the problem harder to diagnose.

HYROS documents that historical Stripe imports cannot reconstruct an ad source when tracking was not active at the time. Missing historical attribution therefore does not, on its own, prove that today’s integration is broken.

Illustrative example: a customer clicks an ad on August 31 and pays on September 2. A report grouped by interaction date can place that revenue in a different period from one grouped by payment date. Record which date each report uses before comparing August totals. This is a teaching example, not a client result.

Reference: HYROS: Stripe integration and historical imports ↗

4. Turn the finding into a testable next step

If the same sale is missing after the reporting rules are aligned, inspect its delivery path: the configured integration, its connection status, the relevant source event and any available delivery response. Confirm the behavior for that integration before retrying or importing records.

If the sale exists but the amount differs, check the event mapping and the agreed treatment of discounts, taxes and refunds. If the amount matches but the channel differs, compare attribution settings and the observed journey.

Close each finding with the evidence, the next action, an owner and a pass condition. For example: “An authorized paid test appears once in HYROS with the agreed amount and currency.” Keep unexplained differences open until the test resolves them.