Analytics revenue uses a different currency from the order

Start with a traceable purchase rather than two totals

Choose an existing order that can be connected to a real provider payment and available purchase-event evidence. Use the references actually retained by the implementation. If the event cannot be linked reliably, leave that relationship unresolved instead of pairing records only because the amounts look similar.

Record the event's transaction reference, value, currency, and observed time exactly as retained. Separately record the order reference, total, currency, and relevant timestamp, then the matching provider payment's amount, currency, and status. Keep those records inside the authorized workspace and use non-secret reference aliases in a shareable comparison.

Google's ecommerce measurement guide describes purchase events as events the implementation sends. The first question is therefore what the implementation actually emitted. A formatted analytics report may be useful for spotting the discrepancy, but it does not replace the underlying event evidence when locating where the value changed.

Align currency, units, and amount composition

A number cannot be compared meaningfully without its currency. Record the currency code from each source rather than relying on a symbol or the report's visual formatting. Do not add amounts in different currencies to produce an unexplained balancing total.

Also distinguish a displayed payment amount from a raw API amount. Stripe's currencies documentation describes API amounts in currency minor units, with zero-decimal currencies and documented exceptions. Do not apply a universal divide-by-one-hundred rule. If a raw Stripe amount is involved, use the documented representation for that currency and operation, and retain both the original value and the interpretation used for comparison.

Write what each amount represents: the items, discounts, shipping, tax, or other components actually included by the store and event implementation. This worksheet does not prescribe an analytics value formula. Inspect the real calculation before deciding that a difference from the order total is an error. If the event's composition is not known, keep that part of the comparison open.

The provider's charge and its settlement record can describe different currency stages. Keep settlement or payout values in a separate column of your private working records when they are relevant. A settlement figure should not silently replace the charge amount used to check the purchase event.

Locate the earliest disagreement the evidence can show

If the order and provider payment agree but the emitted event contains a different currency, inspect the source of the event currency field. If the currencies agree but the amounts differ, inspect the field mapping, amount composition, and unit handling used to build the event. Those are focused investigation routes, not findings about code that has not been inspected.

If the order and provider payment themselves disagree, establish that operational mismatch first. Correcting an analytics tag cannot establish whether the buyer was charged the intended amount. Keep the analytics discrepancy and the payment discrepancy separately recorded so one is not mistaken for the other.

If the emitted event, order, and payment agree, move the investigation to the report. Record the exact revenue metric, reporting currency, period, filters, and any transformation documented for that report. A different displayed currency is a reason to inspect reporting behavior, not evidence of a particular exchange rate, conversion date, or formula.

When only the report and ledger are available, state that limitation. You can identify the disagreement between those records, but you cannot locate it at event creation without the missing event evidence. Do not recreate an old event from today's settings and describe it as the original.

Correct the identified representation and preserve the money record

Give the responsible implementation or reporting owner the first verified mismatch and the evidence on both sides of it. The requested change should name the faulty field or confirmed report setting. Do not change a genuine order or payment record simply to make the analytics display match.

After an authorized correction, compare available subsequent genuine purchase records using the same amount definitions. Document whether the change applies only going forward or whether a separate historical correction is supported. Do not assume a tag change rewrites earlier analytics records, and do not resend purchases merely to force a total without establishing how that action would be handled.

Once individual references reconcile, compare aggregates only within a stated period and compatible currency and amount definitions. Keep unmatched references visible. An analytics total remains a measurement result; use provider payment records to establish what was collected and separate reconciliation records for settlement and payout questions.

For a Prism checkout-review consultation, describe the website, research-only products, and the first amount or currency mismatch you can substantiate. Any instrumentation or reconciliation assistance needs agreed scope, responsibilities, fees, and terms. Send the question without payment exports, customer records, or credentials; the inquiry receives email follow-up and does not purchase implementation.

Event-to-order amount map

Use this for one genuine purchase whose records you are authorized to inspect. Write exact values with currency and units in the final column; keep sensitive source records in their existing authorized location. Compare the event with the order and charge first, then the report. A missing link or unknown calculation remains unresolved rather than receiving an assumed exchange rate.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.