N/A as a traffic source means Piano Analytics couldn't classify the visit at all, usually because key event properties were missing or arrived in the wrong order. It's different from Direct access, which is a legitimate, attributable source. N/A is a data quality signal: something didn't reach Piano Analytics the way it needed to. Most causes can be fixed, and a few can't.
|
|
Direct access |
N/A |
|---|---|---|
|
Meaning |
The first event of the visit had no referrer, or the referrer was the site itself, or it was local. |
The source attribution couldn't classify the visit, typically because key event properties were missing or arrived in the wrong order. |
|
What you see |
A normal, named source value. |
An empty cell, or a placeholder such as "N/A", "Undefined" or "Null". |
|
Common cause |
Bookmarks, session timeouts, etc. |
A missing |
Missing page.display event
Piano Analytics detects the two kinds of sources on different events:
-
Marketing sources: detected on any kind of event that carries campaign information.
-
Organic sources: such as Search engines, Social media and Direct access, detected on
page.displayevents only, from the referrer.
If a visit has no page.display, or its page.display doesn't carry the expected source properties, Piano Analytics has nothing to read an organic source from. A visit with no campaign information then has no source, and shows as N/A. This happens when:
-
-
the
page.displaynever fires, or fires late. -
the only event of the visit is a click, for example.
-
the first event comes from an external server-side integration.
-
a custom event fires before the SDK has initialized.
-
-
Investigation: in Data Query, look for visits that have transaction, conversion or click events but no
page.display. These visits are the most common producers of N/A. -
Fix: make sure the Piano Analytics SDK fires
page.displayon every entry page, and that it fires before any other event of the visit. If an event has to come first, add campaign parameters to it, since marketing sources are detected on any event. For server-to-server flows, see the Collection API guidance onprevious_urlto preserve the attribution context.
Transactions without a visit
A transaction event that arrives without a parent visit can't be attributed to a source. This is typical for server-side payment confirmation flows that don't forward the visitor's browser context. The transaction appears in transaction reports with an N/A source.
-
Fix: forward
idclientandprevious_urlfrom the browser session to the server-side flow, so the transaction joins its originating visit.
Subscriptions and conversions without source data
Some conversion records come from outside the browser entirely, such as telemarketing sales, migrated subscribers and bulk imports. They have no source by definition, so N/A is the correct value.
-
Fix: there's nothing to fix on the data side, because these conversions have no source. If their volume distorts your source analysis, filter them out.
Tagging gaps
If some entry pages don't carry the Piano Analytics tag, visits that arrive on those pages produce N/A. You see it as N/A concentrated on specific landing page URLs.
-
Fix: audit your tagging coverage, and use Tag Inspector to confirm that the SDK fires on every page of your site.
Processing rules that remove source properties
If you have Data Management processing rules that set src_medium or src_campaign to empty under some conditions, those conditions show up as N/A in your reports.
-
Fix: review your processing rules for the
src_properties. Look for rules that set values to empty instead of leaving them untouched.