AdSense Ad Units Report or URL Channels: Which First?

Ad units report names a placement; URL channels segment by path. Pick the AdSense report that matches your question—this page routes, not a second setup clone.

AdSense Ad Units Report or URL Channels: Which First?

After AdSense approval, Reports offers more breakdowns than most small blogs need in week one. Two tools confuse beginners because both feel like “see which part of my site pays”: the Ad units report (performance tied to a named placement) and URL channels (performance tied to paths you configure). They are not interchangeable filters.

This page is a report router. It is not Ad units report basics. It is not URL channels basics. It is not the Ad units versus Coverage metric router—that neighbor splits placement versus request match, not placement versus path.

Early owners:

Which ad block name misbehaves → ad units report. Which folder or URL path deserves more work → URL channels owner. Unit grouping you designed → custom channels owner.

Official Help: View your existing ad units · Track page performance with URL channels · Track ad unit performance with custom channels · Overview of AdSense Reports.

Disclosure: Educational AdSense routing. No earnings guarantees or invented RPM benchmarks.

Table of contents

  1. Placement names versus URL paths
  2. Open the Ad units report when
  3. Open URL channels when
  4. Custom channels and Coverage neighbors
  5. A calm first-month reporting sequence
  6. Scenario: sidebar earns, article body does not
  7. Mistakes that duplicate two tutorials
  8. FAQ
  9. Choose the dimension, then go deep

Placement names versus URL paths

An ad unit is the named block you paste into the theme—sidebar, in-article, sticky footer. The Ad units report answers: how did this specific unit behave on impressions, clicks, earnings, and optional coverage-style columns at unit scope.

A URL channel is a path rule you register so Reports can slice rows by /blog/ versus /tools/ versus one landing page. Help documents limits (for example, caps on how many URL channels you can create) and supported URL shapes. The work is segmentation by address, not by placement name.

Why beginners merge them: both appear under Reports after you serve ads. Someone creates a channel for /blog/, sees earnings move, and assumes the channel is the sidebar unit. The channel is every ad on every URL matching that path unless you add finer rules elsewhere.

One mistake I see often is creating ten URL channels before ads reliably serve on two pages. Start with account-level reading, then add one channel for the path that already has traffic, and use the ad units report when a named block looks blank or cluttered.

Open the Ad units report when

Open Ad units report basics when your sentence includes a unit name:

  • “Did my sidebar unit stop earning impressions?”
  • “Should I remove the in-content block on mobile?”
  • “Which Auto ads format row moved after a layout change?”

The report job is placement debugging: compare units you deliberately placed, then decide whether to remove, relocate, or resize—not whether /blog/ beats /newsletter/ (that is path scope).

Pair with Ad units versus Coverage when the unit row looks fine but you suspect site-wide fill issues. Coverage is request-matching vocabulary; ad units are which block on the page.

Open URL channels when

Open URL channels basics when your sentence includes a path or section:

  • “Does my /blog/ hub monetize better than /resources/?”
  • “Should I expand the cluster that already earns on long guides?”
  • “Did a landing page experiment change earnings after internal links shifted traffic?”

URL channels do not tell you which named unit on those pages won unless you combine insights with unit reports or custom channel grouping. They tell you whether the URL slice justifies more content, links, or ad policy attention.

If the real question is how to read Page RPM on a channel row, route through URL channels versus Page RPM after you pick path segmentation.

Custom channels and Coverage neighbors

Custom channels bundle units you assign—useful when you run “all above-the-fold units” as one group. The custom channels versus URL channels owner explains when path rules fail and unit grouping wins.

Coverage remains the layer for “did requests return ads?” at the scope you select. Neither URL channels nor ad units replace Coverage literacy when impressions disappear site-wide.

Rate vocabulary at account level still belongs on CPM vs RPM before you declare a path “dead” from one RPM cell.

A calm first-month reporting sequence

Week one after serving ads:

  1. Confirm ads appear on real posts (ads not showing owner if not).
  2. Read estimated earnings and pageviews at account level.
  3. When one placement looks wrong, open the ad units report for that name.
  4. When one section of the site deserves comparison, add one or two URL channels for paths with traffic.

Month two:

  • Add custom channels only if you manage many units and need grouped labels.
  • Use Page RPM basics when rate reading—not channel creation—is the bottleneck.

This sequence avoids configuring fifty channels while a single sidebar unit was mis-sized the whole time.

Scenario: sidebar earns, article body does not

A blogger notices strong earnings on long posts but weak totals on short pages. URL channels for /blog/ might show healthy combined rows because traffic concentrates on guides. The ad units report might show the in-article unit with low impressions because short posts never scroll to the slot.

Fix path: ad units report → relocate or remove the in-article block on templates with low scroll depth. Fix content path: URL channels → double down on guide URLs that already earn, not short announcement posts. Different levers; pick the report that matches the lever.

Mistakes that duplicate two tutorials

  • Creating URL channels to debug a misnamed unit instead of opening the ad units report
  • Opening the ad units report to compare /blog/ versus /tools/ when no unit rename will solve a path mix problem
  • Cloning this router into a third URL channel setup guide—depth stays on owners
  • Ignoring custom channels when the question is grouped units, not paths

FAQ

See the YAML faqs block for structured answers on setup order, clones, and neighbors.

Choose the dimension, then go deep

Named placement → Ad units report basics. URL path → URL channels basics. Grouped units → custom channels versus URL channels. Fill versus placement → Ad units or Coverage. This URL only picks which report job comes first so you do not run two walkthroughs in one slug.

Keep learning

More guides in the same topic lane.

Make Money Online6 min read

Word to PDF or Compress PDF: Which Job?

Word to PDF exports DOCX to a fixed PDF; Compress PDF shrinks a PDF you already have. Match the job to Word source files versus overweight PDF attachments.

Make Money Online5 min read

Word OCR or PDF OCR: Which Job?

Word OCR recovers text from image-heavy DOCX files; PDF OCR adds search layers to scan PDFs. Choose by whether the client keeps Word or stays in PDF.

Make Money Online5 min read

PDF to PPTX or Protect PDF: Which Job?

PDF to PPTX rebuilds slides for editing in PowerPoint; Protect PDF adds a password to a finished PDF. Pick by whether they need slides or a locked PDF packet.