Find answers to all your questions about using the Reports page in the Singular platform.
To get your data via API instead, see Introduction to the Singular Reporting API.
Building the Report Query
Metrics are the measurements you want to see in your report - for example, Clicks, Installs, or Cost.
Dimensions are ways to divide your data - for example, you can see measurements per App, Country, or Campaign Name.
The normal dimensions in Singular reporting, such as Campaign Name, may be pulled either from the ad network or the attribution tracker. They represent the result of some processing that Singular performs behind the scenes in order to make sure you get both network stats (such as cost) and tracker stats (such as installs and revenue) for the same campaign.
Source dimensions, such as Network Campaign Name or Tracker Campaign Name, are the raw dimensions as they are pulled either from the ad network or from the attribution tracker. These are mostly used for troubleshooting. For example, if you are getting unexpected results in your report, and you suspect the problem may be caused by the campaign names being slightly different in the tracker than they are in the ad network, you can run a report showing the Network Campaign Name and the Tracker Campaign Name.
The Video Views metric reflects the video view count as reported by each ad network. Many networks have adopted the Media Rating Council (MRC) standard, which defines a video ad view as follows: the video was viewed for at least 2 seconds and at least 50% of it was visible on the screen.
Campaign properties are various settings, statuses, and metadata related to an advertising campaign, such as the bid type, bid amount, and whether the campaign is live or not. These are typically settings you can view and edit in your ad network’s dashboard, but the network doesn’t provide a historical view of what settings you had at different times in your campaign.
To fill this gap, Singular is taking a snapshot of the campaign properties every day, and saving it with the day’s date.
“Source metrics” are metrics that are pulled specifically from the ad network OR from the attribution tracker. For example, select Network Clicks to see clicks as reported by the ad network, and/or select Tracker Clicks to see the number of clicks reported by the tracker.
This is in contrast with ordinary metrics such as Clicks, which are taken sometimes from the ad network and sometimes from the tracker, with the choice made automatically by Singular (see Which metrics are taken from the ad network and which from the tracker?).
You can use source metrics to find and troubleshoot discrepancies between network and tracker data. For your convenience, Singular also provides metrics such as Clicks Discrepancy, which contains the difference between Network Clicks and Tracker Clicks.
A cohort in Singular is a group of end-users with a shared conversion date. An example of a cohort is all the users who installed an app on Dec 1, 2019. You can analyze user behavior by cohort.
Cohort metrics are metrics that can be used for cohort analysis, such as Revenue and ROI.
Cohort periods are the number of days for which the cohort metrics are calculated. If you select a cohort metric, you have to select at least one cohort period. You can select multiple periods.
For more information, see the Cohorts FAQ.
Sometimes you may want to see stats from the Cohort Metrics section, such as Revenue or ROI, without having them analyzed by cohort. Instead, you want to see the stats for the actual day in which the events occurred. In that case, you can select the metric(s) and select the "cohort period" Actual.
Events give you stats for user interactions with your product, such as in-app purchases, tutorial views, registrations, or level-ups in a game. Unlike the default metrics (such as clicks and impressions), events are customizable and you can configure Singular to track a variety of user actions based on your needs and KPIs.
Unmapped data is any data that is not associated with an app and platform. For example, if Singular pulls data about a campaign from an ad network, but the network does not say which app the campaign was for, this data is considered unmapped by Singular.
By default, unmapped data is not included in your report. You can check the Show unmapped data checkbox to include it in the report.
Working with the Report Table
Some campaign metrics are provided both by your ad network and your attribution tracker. By default, the metrics displayed in your Singular report are based on the source that is determined by Singular to be more reliable in the specific case, as follows:
- Impressions are pulled from the ad network.
- Clicks are pulled from the network if it’s a SAN (self-attributed network, such as Facebook or Twitter). Otherwise, they are pulled from the tracker.
- Installs are pulled from the tracker.
Hover for the Source of Metrics
After you run a report in the Reports page, you can hover over any row to see indications of where each number comes from.
There are four possible indications:
- Network: The data was pulled from the ad network’s report.
- Tracker: The data was pulled from the tracker’s (attribution provider’s) report.
- Mixed: This data is based on a combination of network and tracker data.
- Custom: This data is based on a custom calculation that you configured yourself or had Singular configure for you - e.g. when the cost is pulled from the network data but has a fee applied to it.
Click the source label to open the Metric Drilldown popup, which shows you the other possible values for this metric.
In this example, the table shows Impressions as taken from the Network data. If you click on the “Network” tag, the Metric Drilldown popup shows you that the tracker (in this case, Singular’s attribution solution) reports 558,580 impressions, while the ad network (in this case, Applifier) reports 572,394 installs.
While for other metrics, the source of the data is the network or the tracker (or mixed), for Ad Revenue the source depends on the method(s) you chose to get ad revenue ROI data. Hover over the cell to see a tag that sums up the source, and click on the tag to get the details.
- "Rev Source": There is a single source for the ad revenue data in this row. Click on the tag to see the source.
"Mixed": Ad revenue is being pulled from multiple sources for this row. Click on the tag to see the revenue breakdown by source.
- "Calculation": The data is interpolated (see details).
You have several options for manipulating the report table after you have run a report:
Hover over the table headers to reveal the Sort button and a menu that contains options for pinning and freezing columns.
Start typing letters under a field header to filter by those letters.
Click the Columns button on the right to open the column-editing menu, which allows you to hide or reveal columns from the table.
- For even more options, use the Pivot page instead of the Reports page (see Using the Pivot Table).
If you want to see more details about a specific row in the table, hover over the row and click on the drill-down icon that appears next to the last dimension (you can tell where the dimension columns end and the metric columns begin by the different column header color).
The drill-down menu pops up and you can pick which additional dimension you want to see. The detailed report will open in a new browser tab.
In order to help you optimize your campaigns, we always try to provide the data broken down by country.
- When ad networks and other sources provide country granularity, Singular shows it.
- When ad networks do not provide country information, Singular tries to provide this granularity anyway by looking at the targeting settings in the network and/or the tracker data for the same campaign (if we have it):
- If the campaign, sub-campaign, or creative is targeted at one country, we'll show that country in the report.
- If there are multiple countries targeted, and we also have tracker data for the same campaign, we'll try to estimate the cost per country by dividing the overall cost between the countries in the same proportions as the installs (see example below).
Bookmarking, Sharing, and Exporting Reports
You can save your report query by bookmarking. First run a report, then go to the toolbar on the top right and select Bookmark.
In the Bookmark menu, you can select the report time period in two ways:
- Rolling: your bookmarked report will be based on a relative time range. Options available are last 7 days, last 30 days, this month, last month, or custom. Custom allows you to define a specific number of days back.
- Static: your bookmarked report will be based on a fixed time frame. With this option, bookmarked reports will always return the same time range you have chosen.
Also, you can select the Share with Team checkbox to allow other Singular users from your organization to view the same bookmarked report. For information about inviting people in your organization to use Singular, see Team Management.
Open the Bookmarks dropdown at the top of the page to see your personal bookmarked reports as well as any reports that have been shared with you.
Select a report to run it.
- Click Bookmarks at the top of the page to display the bookmarked reports.
- Select the report to run it.
- Click Bookmark in the top right toolbar.
- Select Remove.
You can download your report as a comma-seperated values (CSV) file by clicking the Export to CSV button in the top right corner.
Data is pulled every day at midnight in the customer’s local time. After Singular finishes pulling the data and processing it, it becomes available to the customer by 8:00 AM.
By default, we pull data for 7 days back every time, since the data for previous days can change retroactively. For some ad networks, we may pull up to 31 days back.
You can check the Data Connectors page to see whether data for yesterday is already available for each ad network. You will also be able to see when the next pull is.
Note: If the ad network is not in the same time zone as the customer, Singular may perform a second pull at midnight in the ad network’s timezone.
For example, if a customer is in London (UTC) and their ad network is in Los Angeles (PST), when Singular performs the daily pull at midnight UTC, it’s only 4 P.M. PST, so the numbers reported by the network for the day reflect only part of the day. In this case, Singular may schedule an additional pull at midnight PST to get the full day’s data.
Singular updates exchange rates daily based on the rates in http://openexchangerates.org. These rates are applied to all the data of the day. For most data sources, Singular pulls data seven days back to account for data that comes in from the longer lookback windows. During these seven days, Singular only uses updated exchange rates for sums of money that have changed.
If you want to use exchange rates different from the defaults:
- You can include the fields Original Currency and Original Cost in your reports. These give you the original spend data that Singular pulled from your ad networks, and you can apply your own calculations.
- The Singular support team can set up a custom exchange rate table for you (for example, if your organization applies specific exchange rates for a specific time range).
Data for each day is supposed to be available for you in Singular the next day at 8:00 AM, your local time (this is the default time; if you have asked for a different hour, expect your data at that hour).
If you see a notification that certain networks “are not yet updated for the chosen report dates”, it means one of the following:
- The date range in your report query includes today.
- The date range in your query includes yesterday, and you have run the report before 8:00 AM.
- If it’s past 8:00 AM and you run a report for yesterday, and you still get the “data not yet updated” message, there is probably a technical problem delaying the data pull from the specific ad network.
Data delays can be caused by connection problems, bugs, system downtimes on the ad network’s side, etc. The Singular team is alerted about data delays automatically and immediately begins working on the problem.
In the meantime, go to the Data Connectors page to make sure there isn’t a problem with the connection to the ad network.
There are several possible reasons why the data you see in Singular reports may not match the data you see in your ad network dashboard.
One reason your data may change over time is that Singular shows data as it is reported by your networks and tracker(s). Some of these partners may report estimated data before they have the final data. For example, Twitter states that "Twitter reporting is finalized within 24-48 hours of when impressions are served. Before that time, we estimate data to provide real-time feedback, but the data is subject to change" (source).
Sometimes, instead of getting all the metrics for a campaign in a single row, you will get the ad network metrics (such as Cost) in one row, and the attribution tracker metrics (such as Installs) in a second row.
There are several possible reasons for this:
You requested a dimension that is provided by the ad network and not provided by the attribution tracker, or vice versa.
For example, you may get results like the following:
In this case, you can see that the ad network provided the data broken down by Publisher while the attribution tracker didn’t provide this dimension (at least for this campaign). Because the Publisher dimension doesn’t match, Singular can’t provide a combined row of metrics.
To get a combined row of data with cost and installs for the campaign, remove the problematic dimension from the query.
- Another possibility is that you have a dimension provided by both the ad network and the attribution tracker but they give it a little differently and Singular was not able to match the rows. For example, the tracker may give the campaign name as “my_campaign” while the ad network gives it as “MyCampaign”.
Breaking down your report by publisher (the app in which the ad was served) creates a very high volume of data. Therefore, if you select the dimension(s) Publisher ID, Publisher Site ID, and/or Publisher Site Name, Singular needs you to filter the report to one app and one source.
Custom dimensions that are based on the Country or the Creative Name fields are a newer feature, and can only be applied to data starting on November 1, 2019.
If you use them on a date range that includes older data, Singular cannot calculate the custom dimension values for the older data, and instead displays "N/A Custom Dimensions Range".
For example, say you define a custom dimension called Region based on the Country field, with two possible values: "North America" and "EMEA", and you and run a report to see the cost per region for two of your apps. If the date range includes dates before November 2019, you will get results like the following:
Events marked as unique are only tracked by cohort (see What are cohort metrics and cohort periods?). That is, they can show how many distinct users performed a certain action within a certain number of days from the date of install. To view stats for unique events, select a cohort period in days.
Non-unique events do have metrics for "Actual" dates.
Some of the installs in your report may be attributed to impressions (views) rather than clicks. To check, run the report again with the Conversion Type dimension. This will show how many installs were view-through vs. how many (if any) were click-through.
You can also add the Impressions metric to see how many impressions were recorded as well as how many clicks. The total number should be higher than the number of installs.