Learn how to download and understand raw user-level data through the Export Logs page (Attribution > Export Logs).
For a description of the fields in each log, see Export Logs: Supported Fields.
This article is aimed at Singular customers. If you are a Singular partner, read Using the Partner Portal first.
Troubleshooting the Logs
If you download Conversions or Events logs (in the Export Logs page), and the counts don't match what you see in Singular's reporting (the Reports page or API reporting), check the following:
Your report may be displaying events by cohort, meaning that for every day in the date range, the report counts the events that were created by users who installed the app on that day (see What are cohort metrics and cohort periods?). In contrast, events in exported logs are always associated with the actual date and time in which they occurred.
Check the report settings to make sure your cohort period is set to actual so that it shows the events that occurred on the actual date.
The Singular database has two distinct time values associated with each event:
- The Server Timestamp reflects the time in which the event was received by the Singular servers. This may be significantly different from the original time in which the event occurred if there was a technical delay in sending the event data.
- The Adjusted Timestamp reflects the original time in which the event occurred.
The date range in the Export Logs page is based on the server timestamp.
The date ranges in the Reports page and other Singular reporting tools (e.g. the Singular API) are based on the adjusted timestamp.
This may cause discrepancies in event counts if, for example, an event that occurred on June 1 was delayed such that it arrived at the Singular servers on June 2.
There may be several reasons for these values appearing in your downloaded logs.
1. Real Organic Conversions
If a conversion is judged not to have a paid source, it is marked as organic, and this is how it appears in the user-level logs:
- Network: "Organic"
- Campaign: "Unattributed"
2. Facebook View-Through Campaigns
As of April 22, 2020, Facebook requires MMPs to mask user-level data for view-through campaigns due to user privacy concerns. Therefore, if a conversion is attributed to a Facebook view-through (impression-based) campaign, it is displayed as follows both in your postbacks and in the logs:
- Network: "Unattributed"
- Campaign: "Unattributed"
3. TikTok View-Through Campaigns
As of August 31, 2021, TikTok requires MMPs to mask user-level data for view-through campaigns due to user privacy concerns. Therefore, if a conversion is attributed to a TikTok view-through (impression-based) campaign, it is displayed as follows both in your postbacks and in the logs:
- Network: "Unattributed"
- Campaign: "Unattributed"
4. The Data Retention Period Has Passed
Some partners require Singular to mask user-level data after a certain period of time has passed due to user privacy concerns.
If an install or re-engagement is attributed to one of the following, and an in-app event is triggered after the data retention period has passed, you will see the following details in the user-level event logs:
- Network: "Organic"
- Campaign: "Suppressed"
|Partner||Maximum Data Retention Period|
|Google Ads||6 months|
Tip: If you are receiving postbacks to your internal BI platform that include conversions and events, you can look into the details internally to understand the original acquisition source for the specific device ID.
If the logs you download do not include user data from Facebook, make sure you agreed to Facebook's Terms of Service (TOS) for all of your tracker apps. Without this confirmation, Singular is not allowed to display Facebook's user-level data.
Note that following recent updates to Facebook's TOS, view-through attributions (attributions to impression-based campaigns) cannot be included in user-level data.
User-level data is a detailed list of user activities and attribution-related records, including clicks, conversions, re-engagements, in-app user events, postbacks, fraud decisions, and more.
This is the raw data that is logged by Singular's attribution mechanism and fraud protection engine. Singular uses it to calculate the aggregated data you see in reports.
As a customer of Singular's attribution service, you can access the raw user-level data and use it in various ways - for example, to cross-check the data in aggregated reports if you suspect there is a problem.
Example: Log showing user-level event data
There are three ways to access user-level data:
|The Export Logs Page (Attribution > Export Logs)||
The Export Logs page in the Singular web app lets you manually download user-level data for clicks, installs, re-engagements, in-app events, postbacks, and fraud-related data. The page generates a CSV file.
|Data Destinations||Singular's data destinations (ETL) push data from Singular directly to your internal BI platform, data warehouse, or storage service. One of the types of data you can export this way is user-level conversions and events. For more information, see the Singular Data Destinations FAQ.|
|Configuring Internal BI Postbacks||If you configure Singular to send postbacks to your internal BI platform, you can receive real-time data about installs, re-engagements, in-app events, and fraud decisions.|
To export a log:
- Go to Attribution > Export Logs.
- Choose the relevant date range. You can see up to 90 days of data. We recommend keeping the date range as narrow as possible to avoid going over the record limit per download.
- Select the app, the app site, and the type of log you want to export (clicks, installs, events, or postbacks).
Select the fields you want to include by dragging them into the Selected Fields box.
Make sure you select the device ID field while exporting any logs to get accurate user-level data.
- Optionally, you can filter the log by Attributed Partners, Countries, Device ID, and Device Type. For event logs you can also filter by specific events, and for conversion logs you can filter by conversion type. We recommend filtering the log as much as possible to avoid going over the record limit.
- Select Export Log.
- The date range is limited to up to 90 days back for Singular customers. For options available to Singular partners, see Using the Partner Portal: Export Logs.
- The export is limited to 5M records per request.
- The logs will provide data up to the last 60 minutes of the current day. Select the real-time data checkbox for the past 60 minutes' data.
- The Singular database has two distinct time values associated with each record in the logs: the Server Timestamp (reflecting the time in which the event was received by the Singular servers) and the Adjusted Timestamp (reflecting the original time in which the event occurred). This may cause discrepancies between the user-level data and aggregated reports (learn more).
- Facebook updated the Advanced Mobile Measurement agreement (AMM) on Apr 22, 2020. Based on the new AMM, Singular (and other MMPs) can continue to attribute Facebook attributions and report them at an aggregate level. However, view-through attributions can no longer be reported on the device level. This means you will not see Facebook-attributed installs/events if they were attributed to a Facebook impression (they will be reported as if they were organic) in device-level data. Click-through attributions from Facebook are not impacted. If you do not see Facebook logs at all, approach email@example.com.
- The timezone field tells you the timezone set for your Singular account.
- The timestamped fields (e.g., touchpoint__timestamp) are exported in your configured timezone. Timestamps based on Unix time (e.g., touchpoint__unix_timestamp) are in the UTC timezone.
- If you would like to change the list of fields exported by default, or add a request for a new field to be exported, contact your Customer Success Manager.
- If a network requests user-level fraud data and is not enabled to receive fraud postbacks through Partner Configuration, you can download and share the fraud logs with the network. Singular won’t share this data with any network over a support ticket without consent.
Includes all clicks that were examined to determine the attribution of an install or re-engagement.
Includes information about installs and re-engagement events, who they were attributed to, and other details about the attribution (e.g., was it identifier-based or probabilistic).
Note: The location provided for the conversion event is based on the IP from where it was triggered - not on any location detected internally in your app or any user-provided information. If you have another source of location data for the event, you can check it by reading the passthrough parameter sent by your app to Singular.
Includes data about in-app events, including sessions, registrations, purchases, and any other events that have been defined in the app when integrating the Singular SDK/S2S.
When comparing event logs data against event counts in Reports, make sure to use ACTUAL in Reports instead of a cohort period of 1d,7d,14d, etc. Note that Reports don’t show data against Unique events for the ACTUAL period.
Includes data about any postbacks sent by Singular (not just postbacks about attribution decisions). The log includes postbacks to your internal BI (if you've configured them) and to third-party analytics tools.
Tip: When downloading postback logs, make sure you select the Response HTTP Code and Response HTTP Body fields. Response HTTP Code tells you if the postback was delivered successfully. A 200 code means success; other values mean there was an error. When there's an error in sending, Singular retries the postback 5 more times, in intervals of 1, 5, 15, 30, and 60 minutes. The Response HTTP Body may include additional details about the error.
SKAN (SKAdNetwork) Postbacks
Logs of the SKAdNetwork postbacks that Singular received from your ad network partners. These postbacks are only available for iOS apps that use SKAdNetwork tracking and for partners who have a SKAdNetwork integration with Singular that involves forwarding postbacks. Learn more about Singular's SKAdNetwork solution.
The raw output of the Singular Fraud Prevention System.
Note that this log includes a row for every touchpoint (click, impression, etc.) associated with an install event, including a row for the "organic install" option, which is also examined as an attribution option for every install (see The Fraud Detection Process for more information). Therefore, you may see multiple touchpoints rejected for fraud for one single install.
- Run a report in the Reports page (or the Reporting API) showing installs by source and campaign.
- In the Export Logs page, choose the Conversions log type and pull the following fields for the same date range:
In compliance with integrated partners as well as global standards for user privacy, Singular does not retain user-level data for more than three months.
Accordingly, if you are a Singular customer, you can export user-level logs for up to 90 days back.
Singular partners have more limited access to user-level logs, and among other limitations, partners can only export logs for up to 7 days back.