Singular’s attribution for app installs is generally accurate, but like all mobile measurement partners (MMPs), its precision depends on the attribution model you configure, the platforms you run campaigns on, and how well your SDK integration is set up. For Android campaigns, Singular performs reliably across most scenarios. For iOS, accuracy is more constrained due to Apple’s SKAdNetwork and ATT framework limitations, which affect every MMP on the market. This article walks through how Singular’s attribution works, what affects its accuracy, and whether it’s the right MMP for your app growth setup.
How does Singular’s attribution actually work for app installs?
Singular attributes app installs by matching install events to ad interactions using a combination of device-level signals, probabilistic matching, and SKAdNetwork postbacks on iOS. When a user clicks an ad and then installs your app, Singular’s SDK captures the install event and cross-references it with click and impression data from your connected ad networks to assign credit to the correct source.
On Android, Singular primarily uses Google’s referrer mechanism and device IDs (such as the Google Advertising ID) to perform deterministic attribution. This method is highly reliable because it creates a direct, traceable link between an ad interaction and an install.
On iOS, the process is more complex. Since Apple’s App Tracking Transparency (ATT) framework limits access to device-level identifiers, Singular relies on SKAdNetwork postbacks from Apple for privacy-safe attribution, supplemented by probabilistic matching for users who have not granted tracking consent. Singular also offers its own privacy-preserving attribution solution to help fill measurement gaps left by SKAdNetwork’s limited conversion value windows.
Across both platforms, Singular aggregates data from your ad networks, normalises it, and presents a unified view of your campaign performance. This cross-channel aggregation is one of Singular’s stronger differentiators, particularly for teams running campaigns across many networks simultaneously.
What factors affect the accuracy of Singular’s attribution data?
Several factors directly influence how accurately Singular attributes your app installs. The quality of your SDK integration, your attribution window settings, and the platforms you advertise on all play a significant role in the reliability of your data.
The most important factors include:
- SDK integration quality: A poorly integrated SDK leads to missed events, duplicate installs, or incorrect source attribution. Correct event mapping from the start is non-negotiable.
- Attribution window configuration: If your click-through or view-through windows are too wide, you risk over-attribution to specific channels. If they are too narrow, you miss legitimate conversions.
- User consent rate on iOS: The lower your ATT opt-in rate, the more Singular must rely on probabilistic methods, which are inherently less precise than deterministic matching.
- Ad network data sharing: Singular’s accuracy depends partly on the data ad networks share with it. Networks that delay or limit postbacks reduce attribution precision.
- Fraud filtering: Singular includes fraud prevention tools, but the effectiveness of these depends on how you configure your rules and whether you actively monitor anomalies in your data.
Getting these factors right requires deliberate setup. Teams that invest time in clean SDK implementation and thoughtful attribution window logic consistently get more reliable data out of Singular than those who rely on default configurations.
How does Singular compare to other MMPs like Adjust and AppsFlyer?
Singular, Adjust, and AppsFlyer are all capable MMPs with broadly similar attribution accuracy for standard use cases. The meaningful differences lie in their cost and billing model, data aggregation capabilities, and the depth of their integrations with specific ad networks.
Singular’s standout feature is its cost aggregation layer, which pulls spend data directly from ad networks via API and combines it with attribution data in a single platform. This gives you a more complete picture of your return on ad spend without needing a separate BI tool. Adjust and AppsFlyer offer similar aggregation features, but Singular has historically been stronger in this area out of the box.
AppsFlyer has the broadest network of direct integrations and is widely considered the industry standard for large-scale user acquisition operations. Its raw attribution volume and partner ecosystem are unmatched. Adjust is known for its clean interface, reliable fraud protection, and strong customer support, making it a popular choice for mid-market apps.
From a pure attribution accuracy standpoint, all three MMPs operate within similar constraints on iOS and perform comparably on Android. Your choice between them should come down to your team’s workflow, your ad network mix, your budget, and the level of support you need. We work with all three platforms regularly and help clients evaluate which MMP fits their specific growth stack.
What are the known limitations of Singular’s attribution for iOS apps?
The most significant limitation of Singular’s attribution on iOS is the restricted data available through Apple’s SKAdNetwork framework. SKAdNetwork postbacks are delayed, aggregated, and limited in the granularity of conversion value data they provide, which makes campaign-level optimisation harder compared to Android.
Specific limitations to be aware of include:
- Delayed postbacks: Apple sends SKAdNetwork conversion data with a delay of up to several days, which slows down your ability to react to campaign performance in real time.
- Limited conversion value windows: SKAdNetwork’s conversion value model gives you a narrow window to capture meaningful post-install events, making it difficult to measure deeper funnel actions like purchases or subscriptions reliably.
- No user-level data for non-consenting users: For users who decline ATT tracking, you receive only aggregated, modelled data. This limits your ability to build retargeting audiences or run personalised re-engagement campaigns.
- Probabilistic matching uncertainty: When Singular uses probabilistic methods to fill gaps left by SKAdNetwork, there is an inherent margin of error. This is not unique to Singular, but it is a real constraint you should factor into your iOS reporting expectations.
These limitations apply across all MMPs, not just Singular. The key is to set up your SKAdNetwork conversion schema thoughtfully and align your reporting expectations with what iOS attribution can realistically deliver in 2026.
Should you use Singular as your MMP for app growth campaigns?
Singular is a strong choice for app growth campaigns, particularly if you run paid campaigns across many ad networks and want unified cost and attribution data in one place. It is well-suited for performance-focused teams that need clean ROI reporting without heavy reliance on third-party BI tools. If your primary need is deep network integrations or the most widely recognised MMP brand, AppsFlyer or Adjust may be a better fit.
When evaluating Singular for your app, consider the following:
- Do you need cross-network cost aggregation as a core feature?
- How important is the breadth of direct network integrations to your campaign setup?
- What is your iOS-to-Android traffic split, and how much does iOS attribution precision matter for your optimisation decisions?
- What level of technical support and onboarding does your team need?
No MMP will give you perfect attribution in 2026, especially on iOS. What matters most is choosing a platform your team will configure correctly, maintain consistently, and use to make informed decisions. A well-set-up Singular account will outperform a poorly configured AppsFlyer account every time.
If you are unsure which MMP fits your growth stack, or you want to make sure your attribution setup is actually giving you reliable data, we are here to help. At Wuzzon, we bring 14 years of mobile growth experience to help you build a measurement foundation that works. Explore our app growth stack services to see how we approach attribution and performance marketing, or book a free consultation to talk through your specific setup with one of our specialists.
Frequently Asked Questions
How do I know if my Singular SDK is integrated correctly before launching campaigns?
Before going live, use Singular’s SDK console and event testing tools to verify that install events, session data, and any custom in-app events are firing correctly and mapping to the right sources. Cross-check the data appearing in your Singular dashboard against your internal analytics or Firebase to confirm event counts align. It’s also worth running a small test campaign on a single network to validate end-to-end attribution before scaling spend across multiple channels.
What attribution window settings should I use in Singular for most app campaigns?
A common starting point is a 7-day click-through window and a 1-day view-through window, which balances capturing legitimate conversions without over-attributing to channels that had minimal influence. However, the right settings depend on your app category and typical user decision cycle — subscription apps or games with longer consideration phases may benefit from a wider click window. Review your assisted conversion data regularly and adjust your windows based on actual user behaviour rather than leaving defaults in place indefinitely.
Can Singular help me measure in-app revenue and not just installs?
Yes, Singular supports in-app event tracking beyond installs, including purchases, subscriptions, and custom conversion events that you define based on your funnel. By mapping revenue events through the SDK, you can calculate ROI and ROAS directly within the Singular platform alongside your cost data. This is one of Singular’s core strengths — connecting spend aggregation with downstream revenue events so you can evaluate true campaign profitability without exporting data to a separate tool.
What should I do if my Singular attribution data doesn't match what my ad networks are reporting?
Discrepancies between Singular and ad network dashboards are normal and expected — ad networks count clicks and impressions on their own terms, while Singular attributes based on last-touch or the model you’ve configured, and deduplicates installs across sources. Start by checking your attribution window alignment, then look for signs of overlapping attribution between networks. If discrepancies are large or growing, audit your SDK event triggers for duplicate firing and review whether any networks have delayed or incomplete postback sharing with Singular.
How can I improve iOS attribution accuracy in Singular given ATT limitations?
The single highest-impact action is improving your ATT opt-in rate by presenting the permission prompt at a contextually relevant moment in your app experience, ideally after the user has already seen value. Beyond that, invest time in configuring your SKAdNetwork conversion value schema thoughtfully — prioritise the post-install events most predictive of revenue within the measurement window. Singular’s privacy-preserving attribution features can help model performance for non-consenting users, but a higher consent rate will always give you cleaner, more actionable data.
Is Singular suitable for smaller apps or early-stage growth teams, or is it built for large-scale operations?
Singular works well at multiple scales, but its cost aggregation and cross-network reporting features deliver the most value when you’re running campaigns across several ad networks simultaneously. For very early-stage apps running campaigns on one or two networks with limited budgets, the overhead of a full MMP setup may outweigh the benefits in the short term. That said, building clean attribution infrastructure early prevents costly data gaps later, so if you’re planning to scale paid acquisition within the next 6–12 months, setting up Singular correctly from the start is a worthwhile investment.
What are the most common mistakes teams make when setting up Singular for the first time?
The most frequent mistakes are misconfigured attribution windows that inflate one channel’s contribution, incomplete event mapping that leaves key funnel actions untracked, and failing to set up fraud prevention rules before spend scales. Another common oversight is not connecting all active ad network accounts to Singular’s cost aggregation, which creates blind spots in your ROAS reporting. Taking the time to audit your setup with a checklist — or working with an experienced partner — before your first major campaign launch will save significant data cleanup work down the line.
Related Articles
- 5 signs you need one view of your app's ad performance
- AppsFlyer vs Singular vs Adjust: which is best for app attribution?
- 5 ways to identify your most profitable app ad channel
- Why do users lose their cart after reopening my app?
- 5 reasons switching app tools feels riskier than staying
- What are the most common mistakes when advertising apps?
- How do you advertise an app in the Dutch market?
- How do you track the ROI of app store optimization?
- How do you measure app store optimization success?
- 8 app store review management best practices
EN 
NL 