You need to complete seven steps to use Singular and get accurate insights from your data:

1. Add your app to Singular
2. Integrate the Singular SDK
3. Test your SDK integration
4. Define your events - these are post-install events you want to track such as in-app purchases, level up, or add to cart.
5. Set up partner configuration - this allows Singular to communicate with your ad network partners and send them tracker data from Singular.
6. Set up data connectors - this allows Singular to pull network data from your ad network partners.
7. Set up a conversion model - this defines how you Singular interprets SKAdNetwork conversion values for your business.

Based on other functionality you want to use, such as ad monetization tracking, creating audience segments, or exporting your data to your own BI tools, you may have other optional steps.

Events need to be defined within your Singular SDK integration by your development team. The “Tracking Events and Revenue” guides for each supported platform in our SDK documentation provide step-by-step instructions on how to set those up.

After Singular starts receiving data from your app, each fired event will show up in Attribution > Export Logs.

The export logs contain user-level data. You will need to tell Singular which events to aggregate and show in reports. To do this:

1. Go to Settings > Events and stay on the Cohort Events tab.
2. Select whether your event is Global (applies to all your apps) or App-Specific.
3. Click on the New Event button and name your event, e.g. “Sign-ups”
4. Toggle whether your event is unique or not, i.e. whether or not you want the event to be counted only once per user.
5. From the list of partners below, find the relevant partner, e.g. “Singular” and choose the events that partner sends that you want to aggregate, e.g. all versions of “SignUp Count” across your apps.
6. Configure any other settings and save your event.

Singular always sends postbacks about installs. You may want to set up other conversion events such as re-engagement and view-through attribution, as well as in-app events such as ad revenue and in-app purchases.

See How to Configure Partner Settings and Postbacks.

Installs are attribution events, which are updated in near-real-time (every 15 minutes) in Attribution > Export Logs.

New data is aggregated for reports every hour, in a process that can take up to an hour. So attribution data in dashboards and reports are up to 2 hours old.

See Data Freshness Rates and Update Times.

User-level data can be seen and downloaded from Attribution > Export Logs in the Singular app.

If you plan to export your data to your own BI tools, you may also be interested in our user-level schemas.

Network data is cost data received directly from your ad network partners. To pull these, you set up a data connector for your partner in Settings > Data Connectors.

Tracker data is data containing metrics such as impressions, clicks, and installs tracked by the Singular SDK. When you integrate the SDK, you set up your trackers.

To make sure your tracker data aligns with your networks, it is important to configure your ad partners in Attribution > Partner Configuration.

If you've toggled Show connectors without data in the last 30 days off, you may see the following error message:

This means that Singular was able to successfully query data, but the network has no cost data to report. If the network reports no data for 30 days, its data connector will be filtered out by the toggle.

To get more information on your dimensions, click the Dimensions Availability button in the top-right corner. The Dimensions Availability window gives you full transparency into your reporting data by showing you which networks provide which dimensions to Singular.

 See the Dimensions Availability FAQ.

To get more information about your metrics, you can use the Transparency feature. After you run a report, hover on a metric in a row. It'll show you whether the metric is pulled from the network or from the tracker. You can also click on them to drill down and get more granular data, if available.

Note: Certain metrics are always pulled from the tracker, such as installs, while other metrics are always pulled from the network, such as impressions and clicks. These defaults can be overridden if necessary.

If Singular pulls the metric from both, we'll merge them (if they're the same) or show them on different rows (if they're different). If you want to use dimensions and metrics from a specific source, use source metrics and source dimensions instead.

Singular only reports revenue for attributed users. There is no historical data for users prior to adding Singular as an MMP.