What Is GDN? Google Display Network vs. LINE Yahoo Ads in 2026
Published:
Last Updated:
Category: Ad Operations
Authors: Shusaku Yosa
GDN stands for Google Display Network: a network of advertising inventory across websites, apps, and other eligible destinations. It is distinct from a campaign menu and an ad format. A useful comparison with LINE Yahoo display advertising starts with geography, creative eligibility, operating conditions, and a consistent outcome definition.
What GDN means: network, campaign, and ad format
Separate where an ad can appear, how a campaign is configured, and what format it uses. A network does not guarantee every placement for every creative. Google’s GDN and Demand Gen announcement describes a phased change in campaign management while retaining the network. Demand Gen itself is not another name for GDN.
Term | Meaning | Record before launch |
|---|---|---|
Network | Eligible advertising inventory | Geography, exclusions, actual placements |
Campaign | Management of delivery, objectives, and bidding | Type, migration stage, budget, optimization outcome |
Format | The creative presentation | Eligible surfaces, specifications, required assets |
Outcome | An observed action or business result | Keep clicks separate from accepted inquiries |
How LINE Yahoo display ads relate to YDA and legacy LINE Ads
In Japan, LINE Yahoo’s integration announcement introduced the unified service from April 1, 2026. Its current Japanese name is LINEヤフー広告 ディスプレイ広告（運用型）. YDA refers to the former Yahoo! JAPAN auction-based display offering. Reservation advertising is a separate buying method.
The unified service launch did not mean every legacy LINE Ads account had already migrated. Check the account actually in use, its permissions, creative, conversion setup, and migration status. This article concerns the Japanese offerings; it is not a country-by-country inventory or agency directory.
2026 changes: phased Demand Gen migration and legacy LINE Ads dates
The following distinguishes completed changes from plans, as checked on October 11, 2026. Recheck official notices before scheduling spend.
Date or phase | Status and implication |
|---|---|
April 1, 2026 | Unified LINE Yahoo service launched; verify the current account and product. |
June 30, 2026 | New legacy LINE Ads account applications stopped; this was not the existing-ad serving stop date. |
Google’s phased migration | Eligible voluntary Demand Gen migration began rolling out from June. Later new-campaign restrictions and remaining automatic migration are subsequent stages. |
October 26, 2026, planned | Legacy LINE Ads creation, editing, and serving are scheduled to stop; verify migration and any schedule changes. |
The legacy LINE notice was published September 25 and updated September 28. Limited viewing is planned afterward, with its end date unannounced. October 26 is still in the future at this article’s check date. Likewise, do not assume every Google Display campaign has already migrated; inspect eligibility and settings in the relevant account.
Compare placements with format and eligibility conditions
Campaign and format conditions matter. Google’s format guidance says Display image ads do not appear on YouTube. Demand Gen has different YouTube format possibilities. Avoid turning a broad inventory description into a claim that every image ad runs everywhere.
Question | LINE Yahoo | |
|---|---|---|
Which surfaces? | GDN sites and apps, subject to campaign and format settings | Yahoo! JAPAN and LINE surfaces, subject to format and eligibility |
Which assets? | Confirm specifications for the chosen format | Confirm auction-based display specifications |
What changes? | Campaign migration eligibility and GDN settings | Legacy account transition and scheduled shutdown |
What should be reviewed? | Actual placements and accepted outcomes | Actual placements and accepted outcomes |
Eligible placements are different from delivered placements. Exclude unsuitable geography or context using a documented business reason. Blanket app exclusions do not guarantee better performance.
Choose inventory around objectives, geography, and creative
Choose a specific purpose: awareness, consideration, or accepted inquiries. Then identify serviceable regions, language, the landing-page offer, available creative, and a manageable test budget. Age stereotypes are not a reliable selection rule. Automation also depends on suitable inputs and a meaningful outcome signal.
Use the web marketing starter plan to establish the channel’s role. Assign responsibility for creative, the destination, and inquiry handling before spending.
A worked comparison with consistent costs and qualified outcomes
This fictional comparison uses the same 28 days, Japan targeting, and deduplicated qualified inquiries. Costs are media spend excluding tax; creative and management fees are excluded. These are teaching numbers, not network benchmarks.
Metric | Hypothetical A | Hypothetical B |
|---|---|---|
Media spend | JPY 100,000 | JPY 100,000 |
Clicks | 1,000 | 800 |
Qualified accepted inquiries | 10 | 8 |
CPC: spend ÷ clicks | JPY 100 | JPY 125 |
Qualified CPA: spend ÷ qualified outcomes | JPY 10,000 | JPY 12,500 |
Clicks are not people. Adding platform-reported conversions can count the same inquiry twice. Fix the acceptance criteria, attribution window, deduplication, and reporting period. If qualified outcomes cannot be reconciled, report qualified CPA as unmeasured instead of selecting a platform solely for inexpensive clicks.
Prelaunch and review checks for a fair comparison
- Before launch, check production hosts, geography, language, destinations, asset rights, and format eligibility.
- Validate success, failure, and retries against accepted records.
- During migration, check old and new schedules, budgets, duplicate delivery, and tags.
- Review actual placements and costs using consistent outcome conditions.
- With small samples, report counts and inquiry quality before percentage changes.
A GA4 key event is not automatically a count of registered people. Diagnose differences using traffic-source scopes and consistent URL and UTM parameter conventions. Choose inventory around observable business requirements, then refine the decision with comparable evidence.
