Have you ever wondered about the performance of your YouTube videos? With the time and resources invested in creating content, it’s crucial to track its success.
While YouTube Studio offers robust analytics, accessing the data can be tricky, especially for sharing with others. Here’s where Google Data Studio (previously Looker Studio) comes in handy, offering an easier way to analyze and share YouTube data.
With Data Studio, I can seamlessly integrate YouTube data, schedule updates for stakeholders, customize dashboards, and monitor performance without needing direct access to the backend.
Let me guide you on integrating YouTube analytics into a Data Studio report.
Using a template or starting from scratch
Setting up a report in Data Studio offers two paths. Google’s YouTube Analytics template is a quick start, presenting a clean report with foundational metrics. But be prepared to fix some common issues, which I’ll help you navigate. Alternatively, if you’re up for a challenge, creating a report from scratch can deepen your understanding of Data Studio.
This guide covers both options.
If you’re not the YouTube account owner
For those creating a report without owning the YouTube account, you may find the account isn’t showing as a source in Data Studio. Don’t worry; there’s a workaround. First, access YouTube Studio settings, navigate to Permissions, and grant Manager permissions to the email associated with your Data Studio. Then, obtain the Channel ID from the YouTube URL, add a YouTube connector in Data Studio, and paste the Channel ID under Advanced settings to access the account.
Using the Data Studio YouTube Analytics template
Getting started is simple. On the Data Studio home page, click on Templates followed by Template Gallery. Select YouTube Analytics from the dropdown menu. This template comes preloaded with sample data, which you can replace with your own by clicking “Use my own data.”
During setup, you’ll need to authorize your data by choosing the connected Google Account. Your YouTube channels will then be selectable from a dropdown menu. Note: the dropdown controls settings, not the charts. To update the charts, use the Edit and Share button, which allows you to adjust data sources and metrics.
Copying a template into an existing report
While Data Studio doesn’t directly support importing templates into existing reports, copying a page is an option. After setting up a report with the template, you can transfer it by selecting everything, copying, and then pasting into an existing report’s new page. Although the initial imported charts might show errors, you can reassign the correct data sources using the Properties sidebar.
Customizing your report
The YouTube template offers a solid starting point, but Data Studio allows for extensive customization. While some metrics like revenue and specific audience insights aren’t available, there’s plenty to explore. Adding new charts involves expanding the canvas and leveraging a variety of metrics and dimensions to tailor reports to specific needs.
By following these steps, we’ve crafted a report that’s both functional and informative, ready for sharing performance insights. Automating report exports as PDFs ensures easy distribution, facilitating informed decisions for all stakeholders.
As I delve into the world of SEO reporting, I realize just how much we’ve outgrown platforms like Data Studio. Let me share what I’ve discovered and the exciting changes on the horizon that promise more efficient workflows powered by AI and APIs.
Imagine this scenario: Our team depends on Data Studio for delivering SEO reports. Just as we’re gearing up for a crucial meeting, Data Studio unexpectedly crashes, leaving us with nothing to showcase. It’s frustratingly common and incredibly embarrassing.
Just last year, I was praising Looker Studio (now Data Studio) for its advantages in SEO reporting. Fast forward, and it seems outdated compared to the dynamic coding tools I’m now utilizing. Here’s why rigid dashboards are holding us back and why transitioning to code-driven SEO reporting is essential.
Data Studio once reigned supreme for customizing SEO reports, but technology advanced, revealing its limitations. From dataset crashes to tedious manual interfaces, let me take you through some challenges I’ve faced with Data Studio.
We’re all familiar with the struggle: vast datasets in Data Studio are prone to breaking, often due to the low limits on rows and fields. Hasn’t it been just one too many times when a minor data addition causes everything to crash?
Manual updates in a slow interface make any iteration seem endless. Even the introduction of AI features addresses only a fraction of report-building issues.
Debugging Data Studio reports feels like a never-ending click maze. Unlike code-based systems where agents breeze through files, I’m often left clicking mindlessly within the interface.
Data Studio’s weak API is another stumbling block. It’s representative of Google’s missed opportunities for API-centric platforms. This flaw severely limits external management capabilities.
Despite recent rebranding efforts, these platforms lag behind modern SEO reporting technologies. Let me show you how everything is shifting with AI, APIs, and coding.
The evolution we’re witnessing is astounding. AI-driven coding tools like Claude Code and OpenAI Codex have changed the game. I describe my SEO reporting needs, and these tools take over, executing multi-step workflows efficiently.
Without needing deep coding expertise, I’m able to set up programmatic report workflows from beginning to end. Tools generate code that directly connects to data sources, eliminating reliance on cumbersome dashboard connectors.
Within minutes, comprehensive reports appear as I get accustomed to these tools. Each offers unique advantages, from reasoning to integration speed, transforming manual, rigid processes into infinitely flexible options.
AI coding tools usher in new possibilities for SEO teams by removing barriers between data management and reporting.
Speed is an unmistakable upside. Coding assistants enable SEOs to achieve in hours what once took days, and what took hours, now takes minutes.
Interacting with data directly through coding instead of dashboard interfaces drastically cuts down wait times for refreshes and modifications.
I’m no longer bound by rigid templates. Alongside on-demand data plotting and diverse frameworks, I can tailor reports to perfectly match needs and provide insightful visualizations.
Setting up these tools requires some initial effort but soon transforms the team’s efficiency, offering clearer data constraints and enhanced process transparency.
I’ve discovered how agentic coding assistants can revolutionize real-world SEO applications, from pre-meeting reports to ad hoc stakeholder requests, reducing late-night work and ensuring quick, reliable data access.
AI is reshaping the landscape for all professionals, not just us in SEO. As we adopt this technology, especially in SEO reporting, studies from Stanford and MIT show increased productivity. The shift isn’t optional; it’s imperative.
Teams leveraging AI tools in SEO witness faster iterations and can tackle complex issues more robustly, transforming analysts into strategists with unprecedented capabilities.
Begin this transformation with a small, repeatable project, connect data sources, and slowly expand your use of code-driven reporting. Early adopters are set to lead in SEO efficiency and results.
Traditional SEO reporting tools no longer meet the fast-paced demands of today’s analytics and strategic needs. Through AI and coding, we can leap ahead in reporting accuracy and timeliness, securing a competitive edge.
There’s some exciting news from Google Ads that I believe will make our lives a lot easier! A new integration with Google Tag Manager could revolutionize how we set up conversion tracking, making the process quicker and much less error-prone.
Google is working on simplifying one of the trickiest parts of setting up campaigns—conversion tracking—by minimizing the need for manual tag implementation. This change is something I’ve been eagerly waiting for!
Driving the news. During the conversion setup flow in Google Ads, there’s a new option being tested: “Set up in Google Tag Manager.” This was highlighted in screenshots shared by Google Ads Specialist, Natasha Kaurra. I must say, it looks very promising.
This feature appears right alongside the existing installation methods and provides us with the ability to push conversion tracking setups directly into Google Tag Manager.
What’s new. Instead of having to manually copy conversion IDs and labels between platforms—which can be quite tedious—we can now click a new button that opens a pre-filled tag setup inside GTM. I can already see this saving us so much time.
This update means:
fewer manual steps,
less room for implementation errors,
and faster deployment across accounts.
Why we care. As you know, conversion tracking is critical for measuring our campaign performance. This new update significantly reduces the chances of errors and speeds up the implementation between Google Ads and Google Tag Manager, ensuring our data is accurate from the start. Reliable data means we can optimize better and make more informed decisions.
How it works. From the initial screenshots, it seems that users are prompted to select a GTM container, and a suggested tag configuration is then surfaced, ready for publishing. This could be a game-changer for agencies like ours managing multiple clients, working across several containers, or tackling complex tagging setups.
The bottom line. Even though it’s just a small UI change, it’s set to have a huge impact! This new feature will make it much easier for us to get conversion tracking right from the get-go.
First seen. This update was originally shared by PPC News Feed, who credited Google Ads Specialist Natasha Kaurra for spotting it. Don’t you just love how our community stays on top of things?
I’ve often marveled at high ROAS numbers during my campaigns, thinking they spell success. But, is this performance truly driving growth?
High ROAS numbers can be misleading, often masking mere demand capture rather than creation. To accurately assess growth, I focus on incrementality and marginal ROAS to guide more effective spending strategies.
An ecommerce company once collaborated with my PPC agency, eager to delve into the world of paid search. We crafted a robust plan that quickly led to impressive results: high conversion figures and a commendable ROAS.
It seemed like a strategy success story at first glance. However, when I took a closer look, I noticed something crucial.
Some conversions might have transpired naturally through direct or organic search channels, suggesting our campaigns perhaps weren’t spurring actual growth. This is a vital aspect that often remains unexamined. To gain genuine insight into performance, I examine incremental lift alongside marginal ROAS.
The truth about ROAS
I recall hearing about eBay’s paid search experiment. They heavily invested in brand PPC ads, only to later conduct controlled tests by pausing these ads for certain users, measuring their impact.
Much of the conversion was absorbed by organic traffic, scarcely affecting revenue. Yet, intriguingly, eBay reactivated the branded ads. Whether this was driven by fear or wisdom, I ponder the implications.
As automated search and multi-touchpoint customer journeys evolve, accurately attributing conversions to their channels becomes increasingly complex. Advert platforms often claim the credit, but adopting a skeptical view towards these reports is invaluable.
I comprehend that what these platforms report as attributed return doesn’t necessarily equate to causal lift. While ROAS indicates platform-influenced revenue, it falls short in revealing how much revenue would have materialized regardless of the ads.
With tools like Performance Max and Advantage+, platforms excel in optimizing conversion avenues, often not discovering new clientele but instead marking the costliest touchpoints in pre-determined conversion paths.
In the absence of incrementality assessment, automation tends to amplify non-incremental signals: capturing existing demand through brand search campaigns, retargeting nearly-converting users, and creating falsely “safe” channel reports.
Incrementality tells you whether marketing created something extra
By analyzing incrementality, I can determine how the campaign wrought changes it wouldn’t have caused otherwise, typically through comparisons of exposed groups with control groups. This reveals the actual organizational impact of the campaign.
Recognizing this might feel uncomfortable, yet it serves as a more precise lens for budget allocations than superficial platform attributions.
Sometimes, even a seemingly successful channel in-platform ROI might not equate to impactful incremental growth. Often, it merely realizes existing demand rather than inventing it.
If I truly wish to ascertain if a campaign drives genuine growth, the incrementality factor must become my focal question.
Despite being vital, incrementality only provides part of the picture. The necessity for marginal ROAS to chart subsequent steps can’t be overstated.
An incremental channel alone doesn’t specify where the next budget investment should proceed. Understanding marginal ROAS is essential here.
The marginal ROAS examines the revenue from an additional unit of spend, surpassing the average ROI across all expenses. Often, initial budget allocations perform well but subsequently deliver diminishing results.
As investments continue, dollars spent towards the end become disproportionately less efficient. This principle also holds true for CPA metrics: a blended CPA might appear satisfactory while the terminal dollars spent demonstrate poor efficiency, luring advertisers beyond optimum bidding zones.
I consider an example where an initial $10,000 budget generates $50,000 in revenue (500% ROAS). Deciding to expand, I then invest an additional $5,000, only to generate an incremental $5,000 revenue.
Your new average ROAS: 366%
Your marginal ROAS: 100% (Essentially a $1-to-$1 trade.)
In such instances, the final $5,000 expenditure was ineffective, despite overall acceptable “average” performance on dashboards.
This highlights the folly of focusing solely on average ROAS. It can obscure the genuine scalability that might only be viable at lower spend levels, misleadingly disguising profitable demand capture as flawed incremental expansion.
Informed decision-making requires peering deeper: platform ROAS aids in optimizing in-platform efforts, incrementality assesses campaign-generated value, while marginal ROAS indicates where the ensuing budgets should be directed.
A robust ROAS can reflect true efficiency or merely illustrate a platform ensnaring already-converting demand. Hence, incrementality tests form the cornerstone of my analysis.
My critical inquiry is not whether a channel is efficient per se, but whether subsequent dollars are sufficiently efficient. This understanding is essential for prudent scaling.
Embarking on incrementality testing doesn’t require a flawless measurement lab. Utilizing geo tests, holdouts, audience exclusions, and controlled spending reduction can enhance understanding far beyond another month spent in attribution debates.
Geo-split testing: Organize markets into dual comparable geographic groups, maintaining ad runs in a “test” grouping while halting them in a “control” group. Revenue disparities between these regions unveil the genuine incremental lift of your ads.
Search lift tests (holdouts): Leverage platform tools to generate holdout groups, excluding a small user fraction from ad exposure. The behavioral contrasts between them and exposed groups unveil Search or YouTube campaign direct impacts.
Furthermore, investigating remarketing, branding, awareness campaigns, or supplementary social channels can reveal additional insights.
The real shift: From reporting performance to allocating capital
For too long, marketing teams have restricted measurement to explaining past events. The optimal application lies in shaping future endeavors effectively.
Incrementality helps me discern value creation within a channel, while marginal ROAS justifies additional investments. Together, they elevate marketing measurement from mere reporting to informed capital allocation.
ROAS demonstrates credit allocation, incrementality pinpoints actual transactional changes, and marginal ROAS guides subsequent budgeting. It’s crucial to remember that incrementality differs from attribution. While attribution awards channel credit, incrementality evaluates whether this pursuit justified itself.
I recently discovered that Google is making significant updates to Analytics and Ads consent rules, which are set to take effect this June. This change will prioritize user permission as the key factor in how ads collect and utilize data.
Starting June 15th, the process of data collection in Google Ads will now rely exclusively on the ad_storage consent setting. This alteration removes the previous layer of complexity that came from linked Google Analytics configurations.
Previously, the flow of ad data between Analytics and Ads was governed by both Consent Mode and Google Signals settings within Google Analytics. This often led to confusion among marketers like myself, as many controls were hidden deep within the Analytics settings, rather than clearly visible in consent banners or tag implementations.
Moving forward, Google is streamlining the process. While Google Analytics data collection will still use Google Signals, Google Ads will now focus solely on whether users have consented to ad_storage.
This means that a linked Google Analytics tag will no longer influence Google’s ability to collect or use advertising identifiers.
The new update offers a cleaner, albeit more rigid, consent framework. If ad_storage consent is given, Google Ads can use all available advertising signals, including linking activity to a user’s signed-in Google account when feasible. If denied, Google will only utilize less persistent signals such as URL parameters like gclid.
This change substantially reduces ambiguity—marketers will have a clearer understanding of what drives ads data collection, with fewer options to customize what gets shared.
The primary concern here is that this adjustment makes consent settings more significant for measurement, attribution, and audience targeting. From June, whether Google Ads can leverage identifiers will depend largely on the ad_storage signal, highlighting the importance of correct consent mode setup for optimal campaign performance data.
The update simplifies some of the complexity hidden in linked Google Analytics settings, providing advertisers with more defined rules but less flexibility.
This move by Google underscores a broader strategy to enhance the understanding of consent systems for both advertisers and regulators. Having a single source of truth for ad consent could minimize implementation errors and simplify compliance explanations, but it also demands that brands ensure their Consent Mode is accurately configured.
Should consent updates be delayed or improperly configured, marketers might face gaps in measurement, attribution, and audience targeting.
Marketing teams need to take action before the June deadline by auditing their consent implementation. We should verify that Consent Mode update calls are firing correctly, and that ad_storage settings reflect users’ choices precisely. Brands with Google Signals disabled should be especially vigilant, as they could witness more Ads-linked data under the new setup if users allow ad consent.
The takeaway is clear: streamlined rules are on their way, but getting consent right will be more critical than ever.
I’m excited to share that Google is bringing back Data Studio as a streamlined platform for analyzing marketing and business data across its ecosystem. It’s aimed at helping us easily delve into and act on the data that powers our daily decisions.
Why the switch back? The new Data Studio will serve as our go-to central hub, encompassing a wide range of assets—from traditional reports and dashboards to advanced data applications created in Colab and BigQuery conversational agents. This single platform will enable us to access all the tools and insights essential for shaping our businesses.
Looking back. Three years ago, Data Studio was merged into Google’s analytics efforts with a rebranding as Looker Studio. Now, Google’s responding to evolving customer needs by separating these products again.
Two versions available. Google is introducing two variations of Data Studio:
Data Studio remains free for individuals and small teams seeking quick analysis and visualization capabilities.
Data Studio Pro is designed for larger organizations, providing enhanced security, compliance, management controls, and AI features. Licenses can be purchased through Google Cloud and Workspace admin consoles.
Why it matters to us. This revamped Data Studio can significantly ease the process of gathering campaign, audience, and performance data from Google’s ecosystem into one place. This means quicker reporting, more straightforward analysis, and faster responses—often eliminating the need for analysts or engineering support for everyday tasks.
Integrating Looker. Under the new setup, Looker will continue to be Google Cloud’s enterprise-level business intelligence platform, focusing on managed data, semantic modeling, and large-scale analytics. In contrast, Data Studio is geared towards more flexible personal exploration, ad hoc reporting, and accessible dashboards via services like BigQuery, Google Sheets, and Ads.
What’s on the horizon. For those of us already using Data Studio, the transition should be seamless. Reports, data sources, and assets will automatically transfer without requiring any action on our part.
Google plans to reveal more details about the relaunch and its expansive analytics strategy at Google Cloud Next ’26 later this month. I’m looking forward to discovering what’s next!
Dig deeper. For more in-depth information, check out this article on the new Data Studio.
I’ve been noticing the rapid transformation in how brands are tracking user behavior online. With privacy laws tightening and browser extensions increasingly blocking data, the demand for cleaner data from ad platforms is higher than ever. This change urged me to explore server-side tagging as a solution.
By implementing server-side tagging, I’ve managed to reduce data loss while collecting cleaner, privacy-compliant data. This approach is invaluable, especially considering the experiences I’ve had with providers like Elevar and Littledata.
So, what exactly is server-side tagging, and in which situations does it really shine? Let’s dive into the details!
What is server-side tagging?
Traditionally, tracking scripts ran directly in the browser. However, with server-side tagging, these scripts operate on a server I control, giving me more control over data processing.
Here’s how it works: instead of sending data straight to multiple third parties from the browser, events are sent to a first-party server endpoint, often using a Google Tag Manager server-side container. The server then processes, enriches, and forwards this data to tools like Meta and Google Analytics.
This setup provides benefits such as more data control, a cleaner page performance, and better compliance with privacy laws.
Moreover, server-side tagging grants me the flexibility to enrich and transform data before it reaches ad platforms, standardizing event names, filtering out low-quality events, and adding custom parameters for better audience segmentation.
Is server-side tagging right for you?
While server-side tagging isn’t a one-size-fits-all solution, many brands find it essential, particularly if you:
You need to meet strict privacy or compliance requirements
Server-side setups allow for greater control over how data is processed and shared, supporting compliance with regulations like GDPR and CCPA.
You want faster website performance
In my experience, client-side tracking can slow your page down, but server-side tagging shifts data processing to the server, resulting in faster websites.
You want more accurate tracking (despite ad blockers)
Ad blockers can hinder client-side scripts, but server-side tagging circumvents many of these restrictions, making your data collection more reliable.
You’re investing heavily in paid media
For those heavily invested in platforms like Meta and Google Ads, achieving better data accuracy can significantly impact return on ad spend.
How to implement server-side tagging
When it comes to implementing server-side tagging, you have two main options: building it internally or using a service provider.
Option 1: Internal setup
Choosing an internal setup gives me complete control but requires technical expertise and ongoing maintenance. This involves setting up a GTM server-side container and adding logic for data processing.
Option 2: Use a server-side tagging service
Platforms like Elevar and Littledata offer turnkey solutions that integrate seamlessly with existing tools, allowing me to focus on strategy rather than technicalities.
Our direct experience: Littledata vs. Elevar
In my experience with Littledata and Elevar, each caters to different needs. Littledata is ideal for emerging brands with simpler tech stacks, while Elevar is suitable for those outgrowing entry-level solutions.
Investing in server-side tagging has transformed how I handle data, ensuring that I remain compliant with privacy laws while boosting site performance and data reliability across all my platforms.
As someone who manages ad campaigns across various platforms, I’m thrilled to share that Meta has launched a new template for Google Tag Manager! This makes setting up the Pixel incredibly simple, ensuring smoother cross-platform tracking with more consistency for advertisers like us.
Meta Platforms is committed to reducing the technical challenges we face, especially when juggling campaigns on different platforms. This new update is a step towards minimizing those hurdles.
What’s happening. Meta has unveiled an official Pixel template within Google Tag Manager. This effectively replaces the need to rely on third-party or community-generated solutions.
How it works. This template takes advantage of our existing GA4 dataLayer, allowing us to utilize pre-configured events for Google Analytics 4 without needing to rebuild our tracking systems. It also makes mapping enhanced e-commerce events automatic, such as purchases and add-to-cart actions, which means we don’t have to worry about redundant tagging.
Why we care. The simplified setup reduces the time we spend implementing these systems while lowering the risk of tracking errors. This ensures our campaigns run smoothly across Google and Meta platforms.
What to watch. I’m curious to see if this user-friendly setup encourages more advertisers to adopt Meta Pixel tracking and whether it will lead to similar integrations in the future.
Bottom line. By removing one of the biggest pain points in ad tracking, Meta is making it quicker and simpler for us to gain reliable insights across various platforms.
First seen. This update was discovered by Paid Media expert Thomas Eccel, who highlighted it on LinkedIn.
Recently, I discovered that Google is addressing a pesky bug in Search Console that has been inflating impression counts. Since May 13, 2025, there has been a logging error misreporting impression data, and Google has assured us that corrections will be rolling out in the coming weeks.
This bug has been a longstanding issue, and I was relieved to hear that Google is finally correcting it. They’ve updated their Data anomalies in Search Console page with the following message:
“A logging error is preventing Search Console from accurately reporting impressions from May 13, 2025 onward. This issue will be resolved over the next few weeks; as a result, you may notice a decrease in impressions in the Search Console Performance report. Clicks and other metrics were not affected by the error, and this issue affected data logging only.”
I also read a statement from a Google spokesperson who confirmed: “We identified a reporting error in Search Console that temporarily led to an over-reporting of impressions from May 13, 2025 onward. Bug fixes are being implemented to ensure accurate reporting.”
So, what’s changing? As Google works on these fixes, we can expect changes in how impressions are logged and reported. With this rollout, I anticipate seeing a drop in impression numbers in my Performance report, although clicks and other metrics remain unaffected.
The timeline of this issue stretches back to May 13, 2025, and it has persisted until now. Google mentioned that the complete correction will take several weeks for full implementation across various reporting areas.
Why is this important to me? If my Google Search Console impression numbers change in the near future, it’s likely due to this bug fix. Staying informed helps me understand these shifts better.
I’ve noticed that when I rely too heavily on micro-conversions, my PPC campaigns don’t quite perform as expected. This often leads to distorted CPA and ROAS figures. Here’s how I’m learning to refine my approach to micro-conversions and align my strategies with real revenue.
AI-powered ad bidding systems are remarkably advanced, yet I find myself grappling with conversion tracking that isn’t as evolved. While ad platforms nudge me to keep track of multiple actions, I’ve heard from experts that it’s actually more beneficial to zero in on final outcomes.
From my experience, neither approach is entirely foolproof. Both over-signaling and under-signaling can impact PPC campaigns negatively. Too many vague micro-conversions can introduce noise, steering the bidding process toward less valuable actions, hampering the actual results. Conversely, with too few signals, the system lacks sufficient data for learning.
This issue becomes particularly apparent in my work with Performance Max and similar setups. The optimization here leans heavily on whatever signals I provide, irrespective of their true business value.
I started reflecting on how micro-conversions can overshadow real conversions, leading me to explore why these bidding systems operate this way and how to create a conversion framework that better aligns signal volume with actual business impact.
The Myth of a ‘Data-Hungry’ PPC Algorithm
I had always believed that algorithms thrive on data, a notion reinforced by platform guides and numerous PPC articles. They often imply that more signals inherently equate to better learning.
Yet, I’ve realized that while bidding systems need a certain signal density, they don’t necessarily gain from indiscriminate micro-conversion logging. More data doesn’t equate to better data.
When I add low-intent or weakly related actions, performance can degrade. The system might start optimizing for actions not aligned with real revenue.
It’s clear to me that these machine-learning systems assess frequency, consistency, and predictability without discerning the strategic relevance of a signal.
My account often contains a blend of meaningful actions like purchases and others less significant, like pageviews. Without a value hierarchy, the algorithm treats all signals as viable targets, leaning toward easy, frequent actions that offer little business value.
As I adjust my approach, I’m finding the need to streamline my focus. By applying disciplined strategies and value-based bidding, I can align my signal structures more effectively with my business outcomes.
![```json
{
"alt": "Menu options in a [Sample] YouTube Channel Report interface, highlighting 'Current page settings'.",
"caption": "Navigating through a [Sample] YouTube Channel Report, the 'Page' menu option is highlighted, focusing on 'Current page settings'.",
"description": "This image shows a dropdown menu within a [Sample] YouTube Channel Report interface. The 'Page' menu is opened, highlighting 'Current page settings' in red, indicating it as a selected option. Options like 'New page', 'Duplicate page', and others are visible. The interface appears to be part of a reporting tool for YouTube channels, used for managing and customizing report pages."
}
```](https://crushpress.ai/wp-content/uploads/2026/04/gap-69e792797170b.png)
