# Why Numbers Differ > Why your numbers in Proferex can differ from your traffic source and offer source, and how to line them up. This page explains why your totals in Proferex can differ from what your traffic source or offer source shows, and how to line them up. A small gap is normal. Go through the causes below in order. The timezone is the most common one. --- ## Timezone Each platform starts its day at its own midnight. If Proferex is set to a different timezone, visits, costs, and conversions near midnight land on different days. Set **Timezone** at the top of the report to the one the other platform uses, then compare again. If you have never picked one, Proferex uses New York time. TrafficJunky reports in New York time and TrafficStars in UTC. Your offer source's settings or affiliate manager can tell you which one it uses. --- ## Today isn't finished yet Your visits, clicks, and conversions reach Proferex reports within a minute. Traffic sources and offer sources update their own reports on their own schedules, sometimes hours later. Synced costs for today also keep changing until the next morning. See [How often costs update](/docs/tracker/costs/index.md#how-often-costs-update). Compare whole days that have ended, not today. --- ## Conversions are dated when they arrive Proferex dates a conversion by when the postback arrives, not by when the visitor clicked. A sale that comes in just after midnight counts on the new day, even if the visit was the day before. Some offer sources date conversions by the click instead, so their days split differently. Compare a whole week instead of a single day, and the difference mostly disappears. --- ## Conversions that didn't reach Proferex A conversion only appears in Proferex if your offer source sends the postback. Offer sources can send postbacks late, hold them for review, or not send them at all if the postback is set up wrong. If Proferex shows fewer conversions: 1. Check that your Offer URL sends `{clickid}`, and that your offer source's postback sends it back. See [Postbacks](/docs/tracker/postbacks/index.md). 2. Go to **Tracker → Tracker Settings → Click/Conversion Log** and choose **Conversions** to see every conversion Proferex recorded. --- ## Upsells, rebills, and duplicates **Conversions** counts each sale once. Upsells and rebills sent with `kind=upsell` or `kind=rebill` add their revenue, but are not counted as extra conversions. Your offer source may count them separately. Proferex also records each conversion only once. A second postback for the same click is ignored unless it has a different `tid`. See [Upsells and rebills](/docs/tracker/postbacks/index.md#upsells-and-rebills). If your revenue matches but your conversion count doesn't, this is usually why. --- ## Cost - **Cost sync** shares each day's spend among the visits that carried the traffic source's campaign ID. Visits without the ID don't get synced cost. See [Costs](/docs/tracker/costs/index.md). - **Static costs** are the CPC or CPA you set on the campaign. They are an estimate, so the total won't match your traffic source's bill exactly. - If two of your campaigns use the same campaign ID at the traffic source, they share its spend. --- ## Currency Proferex shows money in your display currency. A payout in another currency is converted at the exchange rate for the day of the conversion. An offer source that reports in its own currency, or converts at a different rate, shows a different total. Compare the number of conversions first, then the revenue. See [Currency](/docs/account/currency/index.md). --- ## Visits and clicks Your traffic source counts its own impressions and clicks. Proferex counts a visit every time the campaign link opens. Some people click an ad and leave before the campaign link loads, so they appear in the traffic source and not in Proferex. Proferex doesn't remove repeat visits from the same person, or filter out bots, so a visitor who opens the link twice counts as two visits. A gap of a few percent between the traffic source's clicks and Proferex's visits is normal. --- ## Next step If the gap is still large after these checks, see [Troubleshooting](/docs/appendix/troubleshooting/index.md).