Apple Maps ads became visible to users on August 25, 2026. Three days earlier, the most detailed trade write-up of the launch stated that Apple had published no cost per tap, no cost per action, no floor and no auction mechanics. Apple’s agencies page had already published three of those four.
This is not a gotcha piece about a trade publication. PPC Land’s coverage of Maps ads has been the most thorough anywhere, its economic read on the rebate structure is sharper than Apple’s own description, and the fourth item on that list — a floor price — genuinely is not published. What happened here is more interesting than an error, and more useful to anyone buying Apple inventory: Apple shipped a complete auction, bidding and measurement specification into a part of its site that nobody covering Apple reads, and every launch story worked from the consumer app and the Newsroom post instead.
That pattern is worth internalising, because it is how Apple documents advertising generally. We found the same shape when we worked through Apple’s delivery documentation: the answers exist, undated and unannounced, several clicks from anywhere a marketer would think to look.
01The claim and the page
Set the two texts side by side. PPC Land, August 22, 2026, writing three days before consumer delivery began:
“Absent from all of it is a price. Apple has published no cost per tap, no cost per action, no floor and no auction mechanics for the Maps format.” And: “Whether Maps campaigns inherit that bidding architecture has not been documented.”
Apple, on its Maps agencies page, under the FAQ heading What is the pricing model for ads on Maps?:
“If you choose the Maximize Engagements bid strategy, you’ll use the cost-per-tap (CPT) pricing model. If you choose the Manage Bids strategy, you’ll have the option of CPT or cost-per-thousand-impressions (CPM) pricing models.” And: “the price you pay is based on our dynamic auction-based pricing mechanism, which takes into account various factors such as relevance, bids, and more.”
Cost per tap: published. Auction mechanics: published, with two named inputs. Bidding architecture: published, and it does inherit — the two strategy names are the same ones the App Store side uses, which means Maximize Engagements is the Maps sibling of the Maximize Conversions strategy that went generally available on the App Store in February 2026.
The auction was not even an August disclosure. Apple confirmed auction-based pricing publicly on March 24, 2026, in the coverage of the original announcement: the ads would use an auction-based pricing system, as is standard in the industry, and advertisers would pay only on a desired outcome such as a view or a tap. That was five months before the launch write-ups described the mechanics as undisclosed.
02What Apple actually published
The full documented surface, assembled from Apple’s agencies page and the Maps help tree, is considerably richer than a pricing line.
| Control | What Apple documents |
|---|
| Bid strategies | Maximize Engagements (CPT only) and Manage Bids (CPT or CPM) |
| Auction | Dynamic auction-based pricing; named inputs are relevance and bids, followed by “and more” |
| Keywords | Advertisers specify terms and categories the search-results ad may display on, and can add negative terms |
| Matching signals | The device’s approximate location, the on-screen map view, and business-provided data such as hours, street address and category |
| Geo targeting | Device location by ZIP code, city or state, plus distance from the business location |
| Structure | Location groups, to promote multiple locations together — the franchise case |
| Placements | Top of search results, and the top of a new Suggested Places experience shown before the user searches |
| Formats | One-image, three-image or text only, depending on the query; images or a logo, never both; promotional text optional, no special characters or emoji |
| Budget | Advertiser-set, campaigns can start or stop at any time, billing only on the intended action |
| Eligibility | United States (excluding American Samoa and the Northern Mariana Islands) and Canada; advertiser must have a business in those countries |
One caveat on placements that we want stated precisely rather than smoothed. Apple’s wording is that agencies using Apple Ads will have the option of choosing an individual ad placement — search home or search results — or both. We found no confirmation that self-serve Apple Business advertisers can split placements the same way. Do not assume they can.
03The metric dictionary
The strongest single artifact is not the agencies page at all. It is a reporting definitions page inside the Maps help tree, and it is a complete metric dictionary of exactly the kind Apple publishes for App Store campaigns.
| Metric | Apple’s definition |
|---|
| Impressions | The number of times your ad appeared within the reporting period |
| Taps | The number of ad taps within the reporting period |
| Actions | The sum of actions — “currently includes Directions, Calls, Website, Photos, Share, Get the App” — from your ad |
| First Actions | The number of times an ad tap resulted in one or more Actions |
| Average CPT / CPM | Average cost per tap; average cost per thousand impressions |
| TTR | Total Taps divided by total Impressions |
| Action Rate | Total Actions divided by total Taps |
| Avg. Cost per First Action | Spend divided by total First Actions |
Three observations. First, this is a two-stage funnel with a named unit at each stage — impression, tap, action — and a cost metric at the bottom. That is a more complete measurement grammar than Apple shipped for App Store search advertising in its first years. Second, reports download grouped by location and campaign, and the same Campaigns dashboard, Charts dashboard and Insights surfaces carry over. Third, read the word currently in Apple’s definition of Actions. Apple is signalling that the action list will expand, and the composition of that list is the whole of what a Maps ad can be optimised toward.
04The tap action nobody has noticed
Sixth in Apple’s list of reported actions, after Directions, Calls, Website, Photos and Share, is Get the App.
It appears on two independent Apple pages — the agencies FAQ and the Maps reporting definitions — and it is separately reported, rolling into the Actions total while also being visible as its own line. Which means, stated at the narrowest defensible width: a Maps ad reports app-acquisition taps as a first-class metric. We have found no trade coverage anywhere that mentions it. MacRumors, 9to5Mac, AppleInsider, TechCrunch and PPC Land all covered the launch; none of them lists the tap actions at all.
→ WHAT WE COULD NOT VERIFY
Do not let anyone tell you this opens an App Store product page
Apple never says so. We checked: there is no app or App Store field in Apple Business location setup, no app-download type in the Maps action-link taxonomy, and no Apple documentation describing where the action routes or how it is populated. The most plausible mechanism is that Maps surfaces an already-linked app on the brand’s place card rather than the advertiser configuring it — but that is inference, and we are labelling it as inference.
Why it matters anyway: the run of commentary treating Maps ads as categorically irrelevant to app marketing rests on the premise that there is no app surface in the product. There is at least a reported one. That is not a channel yet, and we are not going to pretend it is. It is a thread to pull in six months.
05Where the criticism is right
Fairness requires this section be specific rather than gestural. Apple publishes the mechanism and withholds the price level, and the second gap is real.
There is no floor price. No rate card. No published benchmark CPT or CPM for any category, geography or placement. No share-of-voice or impression-share reporting we could find for Maps. The observation that agencies cannot forecast a Maps line item stands — not because the auction is undocumented, but because a documented auction with no clearing prices still gives a planner nothing to put in a cell. The first meaningful cost data will come from advertisers, exactly as predicted.
This is the same condition we described for App Store search after the multi-slot rollout: a mechanism everyone can read and an outcome nobody can price, because every published benchmark describes an auction that no longer exists. Maps starts life in that state by construction — it has no historical dataset at all.
→ FREE 10-POINT AUDIT
Know what you’re actually buying before you bid
We open your Apple Ads account, map spend against the placements and bid strategies Apple actually documents, and show you where the reporting will and will not answer your questions. One hour. Senior strategist. No pitch.
Book my free audit →
06One ad per result, against the App Store’s two
Apple confirmed in March 2026 that only one ad shows per set of Maps search results, and the launch coverage confirms it held. Set that against the App Store, where multi-slot search results completed their global rollout at the end of March 2026 and up to two ads now serve per query.
Apple is running two different density policies on two surfaces at the same moment, and the divergence is deliberate. On the App Store, Apple doubled ad load into an inventory where advertisers already had keyword control, placement history and years of benchmark data. On Maps, it capped ad load at one on a surface with no advertiser history at all. The read we take from that: Apple is optimising the App Store for auction depth and Maps for surface quality, and the constraint on Maps is a product decision rather than a technical limit.
The practical consequence for a Maps advertiser is that there is no second position to fall to. On the App Store, losing the top slot means serving in slot two, and Apple publishes no slot-level impression share with which to diagnose the difference. On Maps, losing means not serving. That is a harsher auction, and it is also a cleaner one — impression share on Maps, whenever Apple publishes it, will mean something unambiguous.
07One API for two properties
The Apple Ads Platform API documentation opens with a single sentence that is easy to skim past: it programmatically manages App Store and Apple Maps advertising campaigns through a single RESTful API.
The topic index carries two parallel workflow guides — advertising your app on the App Store, and advertising your business on Apple Maps — and a set of Maps-specific groups: an Ads on Apple Maps endpoint family for brands, business categories and creative rejection reasons; Managing Location Groups, which Apple describes as organising business locations into named groups defining which locations an ad group’s targeting applies to; Understanding Locations; Brands data objects and data types; and Geo Targeting. The Brands report endpoints retrieve performance data for Maps campaigns, ad groups, ads, keywords and search terms.
That last one is worth stopping on: search-term reports for Maps campaigns. The same query-mining loop that makes App Store search advertising tractable is specified for Maps.
The calendar consequence is direct. Campaign Management API v5 sunsets on January 26, 2027, and the Platform API is the replacement — which means any team still planning a v5-to-v1 port is planning against a surface that now spans two ad properties, not one. We argued in our migration analysis that this is a rebuild rather than a port, and the Maps topic groups are the clearest evidence for that reading: they are new territory, not renamed endpoints. Apple maintains client libraries; we confirmed the official Swift package directly and could not confirm the others, so verify the library list yourself rather than taking a blog’s word for it.
08What changes for an app marketer
Honestly: your buying plan does not change. Maps advertising remains restricted to advertisers with a physical business location in the US or Canada. If you run a pure app business with no storefront, there is nothing here to buy, and our original read on Maps ads — read the policy once, then do nothing — still holds on the buying question. We are correcting one line of it: the pricing model and reporting metrics we described as unpublished are published, and we should have looked at the agencies page.
What does change is the read on Apple’s direction. Apple now sells declared intent on two surfaces, through one auction vocabulary, one API and one reporting grammar. Someone typing a category term into App Store search and someone typing a business name into Maps are the same kind of user from an auction design standpoint: high intent, contextually targeted, no cross-app tracking, billed on a tap. That is the same structural reason Apple Ads reaches the highest-ARPU iOS users — the audience is Apple’s own, and the placement intercepts a decision rather than interrupting attention.
The privacy architecture is identical across both, and it is the constraint that shapes everything else. Maps matching uses contextual information only — search terms, approximate location, the visible map area. Apple states it does not use precise location or interaction history, does not use age or gender, keeps personal data on device, and ties ad view and tap information to a random identifier that rotates multiple times per hour. The Personalized Ads setting is not even supported on Maps. Contextual-only targeting is why the auction leans on relevance, and relevance is the first input Apple names.
09What we could and could not date
We could not establish when the agencies page went live. Web archive access failed from our environment, so nobody should claim these pages predate the coverage on the strength of this article. If you need that claim, run the archive check yourself.
What we can date, indirectly and firmly: Apple Business release notes dated August 14, 2026 record nine new help topics added for the use and management of ads on Maps, explicitly including “Reporting options and metric definitions,” “Create ads” and “Set and adjust budgets.” That places the self-serve Maps help tree eight days before the August 22 coverage. Add Apple’s March 24, 2026 auction confirmation, and the defensible statement is: the mechanics were confirmable in March and the metric dictionary was published no later than August 14.
None of Apple’s Maps advertising pages carries a publication date or a changelog, which is the same problem that runs through Apple Ads Help generally. Cite them by access date. Ours is August 28, 2026.
10Known gaps
No floor price, rate card or benchmark clearing price for Maps ads exists, so any published Maps CPC you encounter is fabricated or derived from a single advertiser’s account. No impression-share or share-of-voice reporting is documented for Maps. Whether self-serve advertisers can select placements individually, as agencies can, is unconfirmed. How the Get the App action is populated, where it routes and whether it is configurable is entirely undocumented. The full list of auction inputs is unpublished — Apple names relevance and bids, then says “and more.” The live dates of the agencies and Maps marketing pages could not be established. And the Platform API client library list beyond the Swift package is unverified.
One structural gap worth naming last. Apple’s 15 percent statement-credit promotion, capped at $1,000 per month for up to twelve months for brands launching a Maps campaign on or before October 11, 2026, plus a one-time $150 credit for new Maps advertisers, arrives as credit against later spend rather than cash — so an advertiser who stops running campaigns forfeits the balance. Derived, and flagged as derived: the cap binds at roughly $6,667 of monthly spend, above which the percentage stops mattering, and the theoretical maximum is $12,000 over the year. That is an acquisition subsidy with a retention hook, and it will distort the first cohort of published Maps cost data. When benchmarks eventually appear, ask whether they were measured net or gross of the credit.