This article outlines how to resolve discrepancies between Yield and the SSP's UI, focusing on common issues like incorrect currency, time zone settings, and data mapping, with actionable steps for troubleshooting revenue and impression mismatches.
Sometimes the data between Yield and the SSP's UI doesn't match. Usually, there is a very logical reason for this. This article outlines the steps to take in order to track down the cause of the discrepancy.
While this article provides troubleshooting guidance, you can always reach out to your Technical Account Manager or the Relevant support team for further assistance.
Typically, the discrepancy is caused by a mismatch somewhere along the setup of the integration. To determine the cause, you should obtain the most granular data possible from both systems and compare them. Displaying the site, placement, SSP, and source data on Yield often helps to locate the issue. In addition to revenue, you might also want to report on impressions and some other metrics to see if they align. If they do match and only revenue shows a discrepancy, it is likely due to an incorrect currency setting.
1. Incorrect Reporting Currency
The default currency in Yield is EUR. If the currency reported by the API (which also applies to mail import SSPs) isn't EUR, you need to enable "Use default report currency" under the SSP settings (Configuration → Integration) and select the appropriate currency. 
Save the settings, then reopen the integration and run a manual import by selecting the dates to which this change should apply, and click the "Import Data" button.
Wait until the import indicates that it has been successful. If you need to apply the currency change for several months back, we recommend running the imports in patches of one month or two weeks, as running a manual import for several dates could cause the import to fail.
2. Incorrect Timezone
Some SSPs allow you to select the reporting timezone. For example, on Magnite, you can report in the PTD timezone. Depending on which timezones you are comparing the Yield numbers to in the SSP's UI, you might observe slight discrepancies.
You can change the timezone under the SSP's settings (Configuration → Integrations). Depending on the SSP, there will either be a dropdown menu or a box to tick, as is the case with Magnite.
Similar to the incorrect currency change, you'll need to run a manual import to apply the changes to the historical data. Please refer to the steps mentioned in the previous section.
3. Data Doesn't Match on a Publisher/Site Level
If there is any missing revenue, it is most likely displayed under the Missing SSP Traffic report, which you can find by navigating to Admin → Missing SSP Traffic. All data that hasn't been mapped (meaning it also won't appear in reports on Yield) will be shown in this report. Identify the SSP with the largest discrepancies and check whether it simply hasn't been mapped. The guide for mapping can be found here: Mapping Adserver and SSP placement IDs to Relevant Yield Placements
4. Historical Data Doesn't Match the UI
Sometimes SSPs make changes to their revenue days after Yield has imported the API data. Yield typically reimports data for the past seven days; in some cases, it may be less or more. If the SSP makes changes after this period, those changes won't be automatically reflected in Yield reports. If you notice discrepancies on a monthly level, this might be the case. Running a manual import for the months with discrepancies will correct the data. If it continues to happen, please contact your Technical Account Manager or the support team at Relevant for assistance.