When your numbers look wrong

Whether tracking is healthy: a history rebuild, the pixel, how much spend the figures explain, and what platforms claim beside what the pixel credits.

Analytics, Campaigns, with the amber Rebuilding history chip beside Last 30 days, above the store’s ad spend, reported and attributed revenue

Check these in order: the first is the most common reason for figures that move or look wrong.

The history is being rebuilt

When Omnymous changes how it derives analytics, it rebuilds every session, order and day of your store in the background. While it runs, Rebuilding history stands beside the period on the Analytics screens, and figures can move until it finishes. It can take hours on a large store. There is nothing to do: the screens refresh when it ends.

Your history is being rebuilt: what changed, under Credit, Contribution and Sessions, and Nothing to do on your side

Press the chip to see what changed.

The pixel is not reporting

Under Analytics, then Campaigns, the Attribution view opens on Measurement health. If Pixel Events (24h) reads 0 on a store with visitors, or the Pixel match rate is amber, the pixel is the cause. See Check that the pixel is reporting.

The figures explain only part of your spend

Tables that credit creatives and their pieces say how much of the period’s ad spend their rows explain, as in Creative Leaderboard’s Explains 100% of ad spend. Below 60% the line turns amber: the rows rest on a small part of your spend.

The Creative Leaderboard’s header: Every launched creative ranked by attributed return, and Explains 100% of ad spend

Spend is left out when Omnymous cannot tie an ad to a creative in your Library: ads imported from the platforms, or ads not linked yet.

Tag the ads you run outside Omnymous. See Tag your ads.
Check how far your ads have been read and linked. See Ad census.

The same line can read, for example, 3 days of spend without an FX rate: spend from an ad account in another currency is left out of a day until that day’s exchange rate is available.

The platform claims more than Omnymous credits

The Attribution view’s Performance sets what each channel’s platform reports beside what the Omnymous pixel credits. On a computer, Claim Gap divides the ROAS the platform reports by the ROAS Omnymous attributes. Reported figures come from Meta only.

Attribution’s Performance: Meta Ads with Reported Rev. $53.6K, Reported ROAS 2.53× and Claim Gap 1.23×, and dashes for Google, TikTok and the channels without spend

A gap above 1× is expected. Meta counts every conversion it believes it caused, including after an ad was only seen, and orders it estimates. Omnymous credits each order once, split across the touches in the buyer’s journey, so an order that a TikTok ad also brought is not Meta’s alone. A gap that grows suddenly is worth a look: check that the pixel is reporting and that your ads are tagged.

Still stuck

Write to support@omnymous.com with:

your store’s name, the screen and the period you were looking at;
what you expected to see, and what you see;
a screenshot of the screen.

Check that the pixel is reportingConfirm the Omnymous pixel is sending your store's visits, see how many orders it ties to a visit, and trace one order back to the ads that brought it.
Ad censusEvery ad your connected accounts list, how far Omnymous has read them, and how to have them read again.