The standing frustration with heavily automated campaigns — Google PMax included, but Microsoft's version equally — is not the automation itself. It is the opacity. Budget disappears into a black box, aggregate ROAS looks acceptable, and nobody can tell whether strong pages are being underserved or weak pages are absorbing spend that should be going elsewhere.
Microsoft's landing page reporting for PMAX adds a concrete diagnostic layer to that opacity. The data it surfaces is not novel — final URL performance has always been something you could partially infer — but having it surfaced directly without custom scripting changes how actionable the reporting actually is.
Why final-URL visibility matters in automated campaigns
Performance Max campaigns use signal expansion and URL routing to serve ads across the Microsoft Advertising network. When Final URL Expansion is enabled, the algorithm can route traffic to any page on your site that it determines to be relevant to the query. This increases reach but introduces routing risk: the page the algorithm chooses may not be the page best suited to convert that specific query intent.
Without final URL reporting, the only way to detect this is through indirect signals — aggregate conversion rate changes, unusual spend concentration, or a hunch that something is off. With final URL reporting, you can see exactly where traffic is going and whether each destination is earning its spend.
What metrics you can now view
- –Spend by final URL — which pages are receiving the most budget
- –Clicks and impressions by final URL — traffic volume by destination
- –Conversions and conversion rate by final URL — which pages are actually converting
- –Cost per conversion by final URL — the efficiency measure that matters most for budget decisions
- –Revenue or ROAS by final URL where eCommerce conversion tracking is in place
The audit workflow
How to decide whether a page is a routing problem or a page problem
| Signal | Likely routing problem | Likely page problem |
|---|---|---|
| Below-average CVR vs site-wide | If the page is a broad category or homepage | If the page is a specific service or product page |
| High bounce rate on that URL | If traffic is from mixed or unclear intent queries | If bounce rate is high even for clearly relevant traffic |
| Strong CVR for direct or organic sessions | Algorithm routing wrong intent traffic to the page | No — page converts well; routing is fine, test more traffic |
| Generic page absorbing most spend | Very likely routing issue — algorithm defaulting to broad pages | Secondary issue — check the page CTA and trust signals too |
| New page with no conversion history | Algorithm cannot yet assess conversion quality | Allow 2–4 weeks; then evaluate if PMAX continues routing there |
Lead gen example
A dental group with five locations runs Microsoft PMAX targeting all five areas. The final URL report shows 62 percent of PMAX spend is going to the site's generic homepage, which has a conversion rate of 0.8 percent. Location-specific treatment pages — where users can book specific appointment types with local contact details — receive 18 percent of spend combined but convert at 4.2 percent.
The fix is two parts: exclude the homepage from URL expansion in the PMAX campaign, and build a page feed specifically listing the high-converting location and treatment pages. After the change, PMAX routes traffic to the intended destinations, cost per appointment booking drops significantly, and the campaign becomes defensible as a budget line rather than a black-box spend that generates low-quality homepage traffic.
eCommerce example
An outdoor equipment retailer sees Microsoft PMAX delivering below-target ROAS. The final URL report reveals the campaign is routing 45 percent of spend to the site's main shop category page (conversion rate: 1.1%) while product-level pages for the specific items featured in the asset groups convert at 3.8 percent. The category page is not wrong — it is just not the highest-intent destination for someone who saw an ad for a specific product.
Adding the specific product pages to a page feed and disabling Final URL Expansion redirects traffic from the campaign assets to the most relevant product destinations. ROAS improves without any change to bids or budget — purely a routing fix.
What to monitor weekly
- –Top 10 URLs by spend — any new URLs appearing in this list that were not there the prior week
- –Spend concentration ratio: what percentage of total spend goes to the top 3 URLs
- –Conversion rate trend for the top 5 URLs by spend — deterioration often signals routing drift
- –Any URL with spend above 5% of budget and zero conversions in the trailing 14 days — flag for exclusion review
Weekly reporting format
| URL | Spend | CVR | CPL / ROAS | Action |
|---|---|---|---|---|
| /services/dental-implants | £420 | 3.9% | £28 CPL | Scale — strong, add to page feed priority |
| /services | £380 | 0.7% | £142 CPL | Exclude from URL expansion |
| /services/whitening | £210 | 2.8% | £38 CPL | Monitor — acceptable, could improve with page test |
| / | £195 | 0.4% | £243 CPL | Exclude immediately |
| /contact | £85 | 1.1% | £95 CPL | Review — low intent entry point |