If you see “dv360” in Google Analytics 4, the first thing to understand is that it does not always mean the generic GA4 Source dimension literally equals dv360.
Google distinguishes between Source and Source platform.
For linked Display & Video 360 activity, Google documents that the Source platform dimension is populated with DV360. That field tells you which advertising platform managed the media buying.
This is different from:
Source
Medium
Source / medium
Default channel group
Session source
Session source platform
First user source
First user source platform
DV360-specific campaign dimensions
That distinction is the key to reading DV360 traffic correctly in GA4.
Quick answer: In GA4, “DV360” most precisely identifies Display & Video 360 as the Source platform. Source, Medium, Campaign and Default channel group can show different values because they describe different parts of the same session and attribution path.
For a broader DV360 reporting workflow, see the DV360 to Data Studio guide.
What does “dv360” mean in GA4?
When a GA4 property is linked to a Display & Video 360 advertiser, Google can bring DV360 campaign metadata into Analytics reporting.
Google explicitly states that:
Source platform = DV360
for Display & Video 360 marketing activity.
That means GA4 is identifying DV360 as the platform where the media buying activity is managed.
It does not automatically mean that:
the generic Source dimension equals
dv360;every DV360 session will appear under the same Default channel group;
the session came from a single publisher or site;
the user was first acquired through DV360;
the campaign is classified only as Display.
A useful way to think about it:
GA4 dimension | What it answers |
|---|---|
Source platform | Which advertising platform managed the traffic? |
Source | Where did GA4 attribute the traffic source? |
Medium | What type of traffic was it? |
Source / medium | How were source and traffic type combined? |
Default channel group | How did GA4 classify the traffic into a reporting channel? |
DV360 campaign | Which DV360 campaign was associated with the traffic? |
DV360 insertion order | Which insertion order was associated with the traffic? |
DV360 line item | Which line item was associated with the traffic? |
The most important rule is simple:
Always check the exact GA4 dimension name before interpreting the value.
Is “dv360” a Source or a Source Platform?
In most cases where marketers are using the label to identify the buying platform, DV360 is a Source platform value.
Google defines:
Source
Source identifies the specific website, app, search engine, platform or location that referred traffic.
Examples include:
google
youtube
facebook.com
direct
Source platform
Source platform broadly identifies where the advertising or marketing activity is managed.
Examples include:
Google Ads
DV360
Manual
SA360
So if someone says:
“My GA4 source says dv360”
the first question should be:
“Which dimension are you looking at?”
It may actually be:
Session source platform
First user source platform
DV360 source
Session DV360 source
Those are different dimensions with different scopes.
Where do you find DV360 traffic in GA4?
For most day-to-day reporting, start here:
Reports → Acquisition → Traffic acquisition
Then use:
Session source platform
and filter for:
DV360
This is also the filtering approach Google references in its Display & Video 360 documentation for working with GA4-linked data.
Once you isolate DV360 traffic, add more dimensions depending on what you want to analyze.
Useful next dimensions include:
Session source
Session source / medium
Session default channel group
Session DV360 campaign name
Session DV360 insertion order name
Session DV360 line item name
Session DV360 source / medium
What is Session source platform?
Session source platform identifies the platform associated with the current session.
That matters because the platform that originally acquired the user may be different from the platform responsible for the current visit.
Example:
A user first finds your brand through organic search.
Later, the same user clicks a DV360 ad and returns to your site.
For the new session:
Session source platform = DV360
But the user's first-touch acquisition dimensions may still reflect the earlier organic visit.
Use Session dimensions when you are evaluating current campaign traffic.
Use First user dimensions when you are evaluating original user acquisition.
Session source platform vs First user source platform
This distinction is central to GA4 reporting.
Session source platform
Answers:
Which platform was associated with this session?
Use it for:
campaign reporting;
traffic analysis;
session performance;
channel analysis.
First user source platform
Answers:
Which platform originally acquired this user?
Use it for:
customer acquisition analysis;
first-touch reporting;
new-user source analysis.
These two values can legitimately be different for the same person.
That is not a tracking error.
It is a scope difference.
What is Session DV360 source?
GA4 also provides dedicated DV360 traffic-source dimensions.
Session DV360 source identifies the source associated with the Display & Video 360 campaign that acquired the session.
This is not the same as the generic Session source dimension.
The DV360-specific dimensions are useful because they isolate campaign information from the linked advertising platform instead of mixing it with other acquisition sources.
Common DV360-specific session dimensions include:
Session DV360 advertiser name
Session DV360 campaign name
Session DV360 creative format
Session DV360 exchange name
Session DV360 insertion order name
Session DV360 line item name
Session DV360 medium
Session DV360 source
Session DV360 source / medium
These dimensions make GA4 much more useful for programmatic analysis than a simple Source / Medium report.
Why does Source platform matter more than Source for DV360 identification?
Because Source platform answers a very specific question:
Which ad-buying platform managed the traffic?
That is often the first thing marketers actually want to know when they search for “dv360 source in GA4.”
If you only look at generic Source, you can lose the distinction between:
platform;
publisher;
campaign;
medium;
channel classification.
For DV360 reporting, a stronger structure is:
Session source platform → DV360 campaign → insertion order → line item → business outcome
That gives you a much clearer path from acquisition to performance.
How GA4 classifies DV360 traffic into channel groups
DV360 traffic does not always appear under a single GA4 Default channel group.
Google's current channel definitions classify DV360 traffic based on creative format.
For example, DV360 traffic can be classified as:
Display
Paid Video
Audio
Paid Other
depending on the creative format and channel rules.
That means two sessions can both have:
Session source platform = DV360
while appearing under different channel groups.
This is expected.
It means:
Source platform tells you the buying platform;
Default channel group tells you how GA4 categorized the traffic.
Do not treat those dimensions as interchangeable.
What DV360-specific dimensions are available in GA4?
GA4 supports a wide range of DV360 dimensions when the advertiser and property are linked correctly.
Examples include:
DV360 advertiser ID
DV360 advertiser name
DV360 campaign ID
DV360 campaign name
DV360 creative format
DV360 creative ID
DV360 creative name
DV360 exchange ID
DV360 exchange name
DV360 insertion order ID
DV360 insertion order name
DV360 line item ID
DV360 line item name
DV360 partner ID
DV360 partner name
DV360 site ID
DV360 site name
DV360 source
DV360 medium
DV360 source / medium
DV360 default channel grouping
This is one reason native platform linking is more powerful than relying only on manually tagged campaign URLs.
GA4 Traffic Acquisition vs the dedicated DV360 report
GA4 can also provide a dedicated Display & Video 360 report.
This report is useful for analyzing:
campaigns;
insertion orders;
line items;
exchanges;
creatives;
placements;
traffic;
conversions;
revenue.
But it is important to understand the scope.
Google states that the dedicated DV360 report includes only sessions attributed to DV360 using non-direct cross-channel last click for the session.
It also excludes traffic when the Session DV360 advertiser ID is empty or (not set).
That means:
Traffic Acquisition and the dedicated DV360 report may not always show identical totals.
They are not necessarily wrong.
They are answering slightly different reporting questions.
Why does DV360 traffic appear as Direct in GA4?
If DV360 traffic appears as:
(direct) / (none)
the problem is usually not “DV360 optimization.”
It is more likely an attribution or tracking issue.
Possible causes include:
missing campaign information;
incorrect or missing platform linking;
landing-page redirects stripping parameters;
URL shorteners;
tracking identifiers being lost;
consent or browser restrictions;
ad blockers;
incorrect tagging.
Google specifically notes that Direct traffic can occur when referral or campaign information is missing.
Before changing campaigns, verify how the session is being attributed.
Why might GA4 show Manual instead of DV360?
If Source platform appears as Manual instead of DV360, GA4 may be relying on manually collected campaign information rather than linked platform metadata.
Check:
Is the GA4 property linked to the correct DV360 advertiser?
Are DV360-specific dimensions populated?
Are manual UTMs being used?
Are redirects stripping identifiers?
Are you looking at Session source platform or generic Source?
Is the reporting scope correct?
Do not troubleshoot only from one field.
Compare generic and DV360-specific dimensions together.
Why does GA4 show (not set) for DV360 fields?
(not set) means Analytics does not have the value required to populate that dimension for the record.
For DV360, possible causes include:
no linked advertiser attribution;
missing campaign metadata;
missing or incorrect link configuration;
unavailable identifiers;
wrong dimension scope.
Google's dedicated DV360 report excludes sessions when Session DV360 advertiser ID is empty or (not set).
So if (not set) appears frequently, treat it as a configuration or attribution question first.
Why does GA4 show DV360 but a different Source / Medium?
Because the dimensions describe different layers.
Think of them like this:
Source platform
Which platform managed the media?
Source
What source did GA4 attribute?
Medium
What type of traffic was it?
Default channel group
How did GA4 classify that traffic?
DV360 campaign
Which campaign generated it?
These values do not have to match textually.
The fact that Source platform is DV360 while another field contains a different label is not automatically an error.
Do you still need UTMs for DV360?
Not necessarily.
If GA4 and DV360 are linked correctly, Google's native integration can populate DV360-specific reporting dimensions.
UTMs can still be useful when:
you need a consistent taxonomy across many platforms;
another analytics system depends on UTMs;
you need additional campaign naming outside Google's native dimensions;
you are validating traffic across multiple environments.
But UTMs should not be added without a clear tagging framework.
Mixing:
native platform tagging;
manual UTMs;
redirect logic;
multiple naming systems
can make reporting harder to interpret.
Can UTMs change what you see in GA4?
Yes.
Manual tagging can influence generic traffic-source dimensions.
This is why you should compare:
Session source platform
Session source / medium
Session DV360 source / medium
Session DV360 campaign
Session default channel group
instead of assuming one field tells the entire story.
A clean reporting taxonomy should define which dimension is used for:
platform reporting;
campaign reporting;
channel reporting;
acquisition reporting;
business-performance reporting.
How to check whether GA4 and DV360 are linked correctly
In GA4 Admin, confirm that the Display & Video 360 advertiser is linked to the intended Analytics property.
Google says the user creating the link needs:
Editor access to the GA4 property;
Admin access to the DV360 advertiser.
A correct link supports:
DV360 data in Analytics reporting;
audience sharing;
Analytics conversion export to DV360.
If you cannot see DV360-specific dimensions, the product link is one of the first things to verify.
A practical DV360 reporting setup in GA4
A useful GA4 reporting structure can be built in five layers.
1. Platform
Use:
Session source platform
Filter:
DV360
This tells you whether the session was associated with Display & Video 360 activity.
2. Channel
Add:
Session default channel group
This lets you separate:
Display
Paid Video
Audio
Paid Other
3. Campaign
Add:
Session DV360 campaign name
This tells you which DV360 campaign drove the session.
4. Buying structure
Add:
Session DV360 insertion order name
Session DV360 line item name
This maps GA4 behavior back to the buying structure in DV360.
5. Business metrics
Add the KPIs that matter to the campaign, such as:
Sessions
Engaged sessions
Engagement rate
Key events
Purchases
Revenue
Average engagement time
For campaign-level optimization, read 21 DV360 Optimization Tips.
Recommended GA4 dimensions for DV360 reporting
Reporting question | Recommended dimension |
|---|---|
Which buying platform drove the session? | Session source platform |
Which channel did GA4 assign? | Session default channel group |
Which DV360 campaign drove it? | Session DV360 campaign name |
Which insertion order? | Session DV360 insertion order name |
Which line item? | Session DV360 line item name |
Which DV360 source / medium? | Session DV360 source / medium |
How was the user originally acquired? | First user source platform |
The main mistake to avoid is building a complete DV360 performance report around Session source alone.
Troubleshooting checklist: “dv360” source in GA4
If DV360 traffic looks wrong, use this sequence.
1. Confirm the product link
Make sure the correct DV360 advertiser is linked to the GA4 property.
2. Check Session source platform
Look for:
DV360
3. Add DV360-specific dimensions
Review:
Session DV360 advertiser name
Session DV360 campaign name
Session DV360 insertion order name
Session DV360 line item name
Session DV360 source / medium
4. Compare channel classification
Check whether the traffic appears under the expected channel:
Display
Paid Video
Audio
Paid Other
5. Check Direct and (not set) separately
These may indicate missing attribution or platform metadata rather than poor campaign performance.
6. Review manual tagging
If UTMs are used, confirm that the taxonomy is intentional and consistent.
7. Check redirects
Make sure campaign information is not being stripped before the user reaches the landing page.
For a broader technical campaign review, use the DV360 Audit Checklist.
Common mistakes when reading DV360 traffic in GA4
Mistake 1: Calling every DV360 value “the Source”
Check the exact dimension name.
Mistake 2: Using First user dimensions for current campaign reporting
First user dimensions describe original acquisition.
Mistake 3: Using only Source / Medium
Use platform-specific DV360 dimensions for campaign and buying-structure analysis.
Mistake 4: Treating Direct as proof that the campaign failed
Direct often reflects missing attribution information.
Mistake 5: Assuming all DV360 traffic should be Display
DV360 can appear under multiple GA4 channel groups.
Mistake 6: Mixing manual UTMs and native platform tagging without a reporting standard
This can create confusing reporting even when the campaign itself is functioning correctly.
The bottom line
If you see “dv360” in GA4, do not interpret it as a generic source label without checking the dimension.
In Google's current Analytics documentation, DV360 is a Source platform value for Display & Video 360 marketing activity.
The best way to analyze it is:
use Session source platform = DV360 to isolate platform traffic;
use DV360-specific dimensions for campaign, insertion order and line item analysis;
use Source, Medium and Default channel group as separate reporting dimensions;
distinguish Session reporting from First user acquisition reporting;
troubleshoot Direct, Manual and
(not set)as attribution/configuration questions.
The key idea is simple:
DV360 tells you the advertising platform. Source, medium, channel and DV360-specific dimensions tell you different parts of how GA4 attributes and classifies the traffic.
For broader reporting, read the DV360 to Data Studio guide.
For campaign QA, use the 86-point DV360 Audit Checklist.
Frequently Asked Questions
What does dv360 mean in GA4?
It identifies Display & Video 360 marketing activity. Google specifically documents DV360 as a Source platform value in GA4 when Display & Video 360 data is available through the integration.
Is DV360 the same as Session source?
No. Session source and Session source platform are different dimensions. Source platform identifies the buying platform, while Session source identifies the source attributed to the session.
Where do I find DV360 traffic in GA4?
Go to Reports → Acquisition → Traffic acquisition, use Session source platform and filter for DV360.
Why does DV360 traffic show as Direct?
Common causes include missing campaign information, broken platform integration, lost parameters, redirects, consent limitations or other attribution gaps.
Why does GA4 show (not set) for DV360 fields?
It means GA4 does not have enough information to populate that specific DV360 dimension for the record.
Does DV360 always appear as Display in GA4?
No. Depending on creative format, DV360 traffic can be classified as Display, Paid Video, Audio or Paid Other.
Do I need UTMs for DV360?
Not always. Native DV360–GA4 linking can populate DV360-specific dimensions, but UTMs may still be useful for a broader cross-platform taxonomy.
What is Session DV360 source?
It is the source of the Display & Video 360 campaign associated with the session.
