Overview
How up-to-date is the data in uSlicer?
Most data in u-Slicer is between 2-4 hours behind real-time trading data as it is collated from various systems. Before loading data into u-Slicer, a number of processes happen in the background to ensure data is of sufficient quality, commonly known as the extract, transform, load (ETL) process.
Why do I see inconsistent data between data in the UI and data in uSlicer?
The inconsistent data between the UI and uSlicer is a result of varying data sources, data definitions, and reporting delays. To explain further, the ‘Avails’ metric in the UI is calculating all ‘Supply Avails’ for the demand deal in the Commerce Grid. This makes the assumption that all the bid requests are passed through and not filtered out beforehand. This is to give you a rough estimate of the scale of the deal in order to identify any issues. Once the Deal is active and we are able to refine and reconcile the ’Avails” metric within uSlicer. This now calculates ‘Downstream Supply Avails’ which is the most up-to-date measurement of avails of the Demand Deal in Commerce Grid. In addition, if you don’t have the demand deal associated with any package, you will not have zero avails metrics in uSlicer as we are calculating the full ‘Downstream Supply Avails’.
Why does uSlicer use extract, transform, load (ETL) process?
The benefit of ETL is that it removes noise from the data set, such as duplication, trading anomalies, and unrelated errors. Data sampling is also applied to certain fields to improve one's ability to query a data set without performance issues caused by too much unimportant data. This can used for the following purposes:
Monitoring campaign, deal, or line item performance.
Analyzing trading patterns to identify advantageous combinations of inventory sources, user segments, buying strategies, or supply partners.
Analyzing trading patterns to identify underperformance or system problems like timeouts, deal inactivity, or below-floor bidding.
Setting up custom reports and scheduled reports.
Exporting data to your own system.
Creating custom metrics to apply your own logic to quantifying your trading performance.
Why is my data different when I pull reporting in different timezones?
Data from different time zones will not match, and shifting timezones will compress data. Note: Publisher domain is only exact when broken out by day - if broken out more granularly by hour, data will not be exact
Why do I see data compression when I select certain metrics?
Data compression occurs depending on the combination of metrics you have selected in your reporting view. As a rule of thumb, we recommend trying not to use too many metrics simultaneously to avoid compression.
I see a ±XX% number pop up in the upper left corner of my u-Slicer data table. What does this mean?
This indicates compression of data. The ±XX% number represents the confidence range of the dataset based on the keys you selected, meaning how different the actual data may differ from what is shown. If you continue to add additional compressed dimensions on top of other compressed dimensions, the approximation will multiply or increase.
Why is there a difference between my billing and the Net Media Revenue I see in u-Slicer?
While Net Media Revenue is an exact value in slicer, the final billing can show a different number because of DSP discrepancy adjustment.
Can we get the report broken out by Ad Units for an Amazon TAM connection?
No - we don’t log info about placement, but if you need this data, please refer to reports from the Amazon UI
What should I do if I see the traffic but don’t see any bid offers?
Double-check that you have passed your inventory for approval and that you have requested connections with DSPs
Data Timing and Sampling
Data Accuracy for Today
Using data for today’s date is not accurate, as many of the figures used to calculate the values u-Slicer reports come into the system with different time delays. Figures and calculations will be accurate from yesterday’s date backward.
Data Sampling
The data to which certain values refer is sampled to reduce noise, and when you query such data, it will also have an associated confidence range. This can be seen in the UI e.g. ±.01 and API response confidence_range. Also, if you split data using multiple keys which are sampled, the level of accuracy decreases.
Bidfloor Calculation
The Bidfloor is an average value. It is calculated based on the following figures, which are the average of these.
If the Buyer responds with the Deal ID, the bid floor for that Deal ID is stored.
The impression bid floor is stored if the Buyer responds without the Deal ID.
If the Buyer responds with no-bid, or a timeout, the impression bid floor is stored.