Apple gave every ad claim a clock, and took attribution away from demographics
Two lines in a measurement partner's bulletin, effective on a Tuesday, and a quarter of the way app marketers read their own Apple Ads results changed. One line makes the numbers more honest. The other makes a whole targeting option invisible.
By Katie Delaney · 2026-09-02 · 12 min read
What changed in AdServices on 1 September, in the bulletins' own words#
of App Store searches come from devices with Personalised Ads turned off, the users a demographic refinement already excluded
The fox reads the fine print before it reads the field. AppsFlyer's bulletin, effective 1 September 2026, says two things. First, Apple's AdServices API adds an engagement timestamp to all iOS attribution claims, including those that previously lacked one, and AppsFlyer uses this timestamp to apply your configured lookback window and last-touch attribution rules. Second, for ad groups with age or gender targeting, Apple will return an attribution payload of false, and these engagements cannot be attributed to Apple Ads.
Singular's integration page says the same with a little more edge: since these claims will now be evaluated against your configured lookback window, you may observe a slight decrease in attributions attributed to Apple Ads, and Apple will no longer return attribution claims for any ad group with age or gender settings applied. No action is required, both partners say, which is true of the integration and untrue of the marketer. The integration updates itself. The media plan does not, and the fox that trusts the den to rebuild itself sleeps outside.
Why does a timestamp matter? Because AdServices attribution was, until this week, partly undated. Apple's own developer documentation describes the mechanism: the framework generates a token with a 24-hour TTL, the app or its measurement partner posts it to Apple's server, and the payload returns attribution=true when a matching record exists and attribution=false when it does not. The record carries a clickDate for click-through claims. Claims without a usable engagement time were, in practice, credited without being tested against the advertiser's window. Now every claim carries a clock, and every clock is checked.
The demographic tax: what age and gender refinements now cost in Apple Ads#
Apple's audience settings page is candid about the trade. Modify audience settings explains that Apple Ads optimises your ad groups to reach customers across demographics, but you can refine your settings by age and gender if preferred, that the youngest targetable age in the US and Europe is 18, and that apps rated 15 plus serve only to adults regardless. What it does not say, because it never needed to, is that a refined group already loses everyone with Personalised Ads switched off. Search Engine Land puts that at 78% of App Store search volume.
So the arithmetic of a demographic refinement in Apple Ads now runs like this. You give up most of the search volume to narrow the audience. You keep the installs that arrive from the narrowed audience. And from 1 September you cannot attribute any of them through AdServices, because the payload comes back false. The ad group still runs, still spends and still converts. It just does so in the dark, in the undergrowth where budgets get cut. The fox does not hunt a field it cannot see across.
There is an honest defence of Apple's move. Demographic attribution on a platform that lets the user opt out of personalisation was always a partial signal dressed as a full one, and a partial signal that reports as complete is the kind of number that talks a team into the wrong decision. Returning false is blunt. It is also the first time the platform has told you plainly that a slice of your campaign was unmeasurable.
Why the timestamp is the bigger story for apple search ads attribution#
The demographic change is loud. The timestamp change is quiet, the scent under the thicket, and it touches every campaign. AppsFlyer's own reading is that for most Apple Ads campaigns, attribution accuracy improves because engagements are now evaluated against your advertiser-defined lookback window rather than the previous default windows, including engagements from non-consenting users who previously were claimed without timestamps. Improve is the right word, and so is decrease. A claim that used to count now has to be inside your window to count.
The durations above come from two places. Singular documents a 90-day click-to-install and 61-day view-to-install window for Apple Ads pre-order campaigns, attributed only if there is no other more recent and competing touchpoint from another channel. Apple's attribution overview says AdServices attribution data is retained for up to 21 days to support relevant campaign measurement, and notes that Apple Ads registered with AdAttributionKit on 10 April 2025 while Apple will continue to maintain the AdServices API. Different clocks, one rule from this week: the claim has to fit the window you set.
What that does to reported numbers depends on how long your windows are and how much of your Apple Ads volume came from claims that were never dated. Expect a small step down in attributed installs in the first week of September, and resist the urge to explain it as a performance drop. It is a counting change, exactly like the one the Snap Unified Attribution switch produced this week: the number moved, the market did not.
I want to create a dashboard to manage my campaigns via API. Obviously I need to have an API credentials for this. It seems not possible to generate needed keys from my main admin user and looks like I need to invite another user and specifically assign api permission.
The same day the AdServices payload changed, the busiest question in the Apple Ads subreddit was how to get API access at all. That is the state of the practitioner base: a platform Kochava measured at 36% of iOS attribution volume, and a community still working out which user gets the keys. Nobody in that thread was reacting to the attribution change, because on 1 September almost nobody had noticed it. They will notice it in their October reports.
What can you do with the Apple Ads attribution API, and what should you stop doing#

What can you do with the apple ads attribution api? Apple's AdServices framework page puts it in one sentence: the Apple Ads Attribution API is a solution that combines the AdServices framework and a RESTful API for server-side communication with Apple's attribution server, retrieving attribution data you can measure against specific Apple Ads campaign metadata. In practice, an app requests a token, posts it within 24 hours, and gets back a record with the campaign, ad group and keyword identifiers that produced the install. That is the whole instrument, and it is a good one for what it measures.
What you should stop doing is treating AdServices as the same thing as your MMP dashboard. The Apple Ads help centre keeps attribution as its own section for a reason: the framework reports what Apple can vouch for, the partner blends that with everything else, and the blend is where windows, deduplication and last-touch rules live. Kochava's 2026 survey found only 21% of respondents describe their understanding of iOS attribution as comprehensive and 33% had not implemented SKAN at all. A change to one input, on a stack most teams do not fully understand, is how a quiet counting shift becomes a loud budget argument.
Apple Ads share of iOS attribution
Of iOS attribution volume, by Kochava's measurement.
ATT prompt acceptance
Of iOS users shown a prompt accept it; only 2% of installs are prompted.
Comprehensive understanding
Of respondents rate their grasp of iOS attribution as comprehensive.
Two footnotes for anyone who runs app store search ads at scale. First, Apple Ads has not become less effective this week; Search Engine Land still cites Apple's own figure of conversion rates of more than 60% for search results ads, and the change touches the counting, not the auction. Second, the brands most exposed are the ones Kochava describes as the vast majority of Apple Ads spend, brands bidding on their own brand terms, because branded installs are exactly the ones a lookback window is most likely to reject as organic. Your brand campaign is about to look smaller. It was always this size.
The September checklist for apple ads, before the October report lands#
None of this needs a new tool. It needs a baseline, a list, a calendar and a vulpine patience with reports that move before markets do. Write down last week's attributed installs by ad group, tag every group carrying an age or gender refinement, set the lookback windows you actually believe in rather than the defaults you inherited, and diarise the first full-week comparison for 8 September. The fox marks the trail before the snow, not after.
Export attributed installs, spend and cost per install by ad group for the four weeks to 31 August. This is the only clean comparison you will ever have.
List each ad group with an age or gender setting. From 1 September its AdServices payload returns false, so its installs will vanish from attribution, not from reality.
Every claim is now tested against your lookback window. Choose one per campaign type that matches how people actually install after an ad, and document it.
Keep a refined group only if its reach loss was ever justified; otherwise remove the refinement and watch measured installs return.
Tell finance in September that attributed Apple Ads installs will step down for counting reasons, with the baseline attached, before the chart does it for you.
One search note, since app marketers publish too. Google's AI optimisation guide still asks for pages made for your audience, not just for generative AI search, and a plain, dated explainer of what AdServices now returns will outrank every reworded bulletin by October. If you would rather have the baseline built, the windows set and the October narrative written for you, that is what folkfox does inside app marketing and paid search for fintech and healthcare apps, and the first conversation is free.
Frequently asked questions#
What is AdServices?
AdServices is Apple's framework for attributing app downloads that originate from Apple Ads on the App Store. An app requests a token, the token is posted to Apple's attribution server within 24 hours, and the server returns a record with the campaign, ad group and keyword identifiers behind the install, or attribution equals false when there is no matching record.
What changed in Apple Ads attribution on 1 September 2026?
Two things, according to AppsFlyer and Singular. Every AdServices attribution claim now carries an engagement timestamp that is evaluated against the advertiser's configured lookback window, and ad groups with age or gender targeting return an attribution payload of false, so their installs cannot be attributed to Apple Ads at all.
What can you do with the apple ads attribution api?
You can retrieve the Apple Ads campaign, ad group and keyword that led to an install, using the AdServices framework to generate a token and Apple's REST endpoint to exchange it for an attribution record. Most teams do this through a measurement partner, which applies lookback windows and last-touch rules on top of what Apple returns.
Should I remove age and gender targeting from my Apple Ads campaigns?
Decide per ad group. A demographic refinement already excluded users with Personalised Ads off, which Search Engine Land puts at 78% of App Store search volume, and from 1 September it also returns no attribution. Keep a refined group only if its narrowing ever justified the reach loss; otherwise remove it and watch measured installs return.
Will apple search ads attribution numbers go down after the change?
Probably a little, and for counting reasons rather than performance. Singular says advertisers may observe a slight decrease in attributions because claims are now evaluated against the configured lookback window, and any ad group with demographic settings will report zero AdServices attributions. Freeze a pre-change baseline so the step is explainable.
How do app store search ads compare with other iOS channels on attribution now?
Apple Ads is the largest single source: Kochava measured it at 36% of iOS attribution volume in mid-2026, against 11% for SKAdNetwork. The 1 September AdServices change makes its numbers stricter rather than smaller in truth, which is more than can be said for channels where only 2% of installs even see an ATT prompt.
Read more on this topic#
Snap changed the count, not the campaign
The other attribution switch of the week, and why a number that moves is not a market that moved.
Read the pieceApple moved the price. It did not move yours
September's storefront pricing changes and what they do to your unit economics.
Read the pieceApple's app tracking transparency prompt finally plays it straight
The EU consent overhaul that changed what an ATT prompt can say.
Read the pieceGoogle built a box for forums. Reddit owns nine tenths of it
Where the app marketers asking about API keys actually gather, and how to be useful there.
Read the pieceWant the baseline built before October explains it for you?
An attribution change is only a crisis if nobody wrote the baseline, and folkfox sets up app attribution that survives a platform change: the windows, the ad group audit and the report your finance team will read without a meeting.