Skip to content

Features
Pricing
Changelog
Status

Tag: API

Mastering SEO Reporting: Move Beyond Data Studio

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.

Inspired by this post on Search Engine Land.

April 21, 2026
Google Ads API: Embrace Enhanced Security with Multi-Factor Authentication

As someone who frequently works with Google’s advertising tools, I know firsthand how crucial security is. Starting April 21, Google is implementing a mandatory multi-factor authentication (MFA) requirement for its Ads API. This is a significant move towards enhancing security, but it’s one that might need us to rethink our authentication workflows.

Driving the news. Google will gradually enforce mandatory MFA for the Ads API, aiming for complete roll-out just weeks after the initial date. This means we all need to be prepared.

This update directly impacts those of us generating new OAuth 2.0 refresh tokens, as it mandates a more secure authentication process.

What’s changing. We’ll now need to add another step in verifying our identity. This could be in the form of a phone prompt or an authenticator app, alongside the usual password.

Existing OAuth tokens we’re already using will stay unaffected, but for any fresh authentications, MFA will become the default requirement. If we’re not yet using two-step verification, it’s time to set it up.

Why we care. This shift influences how we manage and access our Google Ads data through various APIs and connected tools. While it undeniably enhances security and mitigates unauthorized access risks, it could also require us to adjust existing workflows, especially when generating new credentials often. Preemptive preparation can save us from potential disruptions.

Who’s affected. If your applications or workflows rely on user-based authentication, you’re in for some changes.

User authentication workflows: These will need MFA for new token setups.

Service account workflows: Thankfully, these remain untouched. They’re actually recommended for automated or offline scenarios.

The requirement isn’t limited to the API alone. We’ll also see it in tools like Google Ads Editor, Scripts, BigQuery Data Transfer, and Data Studio.

The big picture. As we lean more heavily on ad platforms for sensitive data and automation, security can’t be pushed aside. This need grows as API access proliferates across various teams, tools, and integrations.

Yes, but. While boosting security against unauthorized intrusions is welcome, we must consider the challenges it introduces. Especially for teams like ours that often create new credentials or depend on manual authentication flows.

The bottom line. Google’s decision to make MFA standard for Ads API access marks a shift towards more stringent security policies across advertising tools and workflows.

Inspired by this post on Search Engine Land.

April 17, 2026
Google Ads Unveils Robust Merchant API Before Content API Exit

I recently discovered some exciting news that Google Ads has introduced a more robust Merchant API. This new API is crafted to offer advertisers scalable and feature-rich tools for handling product data, especially as we prepare for the shutdown of the Content API for Shopping.

Google is steering us toward a more modern, scalable infrastructure for Shopping integrations. This shift brings cutting-edge capabilities, including AI tools, directly into our scripting workflows.

What’s happening: Starting April 22nd, Google Ads scripts will support the Merchant API. This change comes as we approach the August 18th retirement of the Content API for Shopping. This new API will be available as an Advanced API within the scripts editor while we can still use the Content API until its official sunset.

What’s new: The Merchant API introduces a modular architecture, breaking down functionality into sub-APIs for quicker updates, easier maintenance, and fewer disruptions. This setup enhances capabilities with features like the Google Product Studio API for generative AI, APIs dedicated to product and store reviews, and a Notifications API for real-time updates.

Additionally, we now have more control over data management. This includes handling supplemental product data, managing local and regional inventories, and running promotions—all within an omnichannel system while still supporting our legacy setups.

Why it matters: The Merchant API provides a more flexible approach to managing product data at scale. It’s especially beneficial for complex or omnichannel setups and introduces new capabilities like AI-driven content tools that can boost feed quality and performance. With the imminent retirement of the Content API, transitioning to this new system is crucial to avoid disruptions and maintain competitiveness.

Yes, but: Switching to the new API requires adjustments, particularly for those of us with custom scripts or complex feed setups tied to the legacy API.

Bottom line: For those of us using scripts, this is our chance to upgrade to a more powerful and scalable integration, enabling new features while future-proofing our Shopping workflows before the cutoff date.

Dig deeper: Merchant API is coming to Google Ads scripts starting April 22, 2026

Inspired by this post on Search Engine Land.

April 10, 2026
Simplified Google Ads Conversions for Accurate Tracking

I’ve got exciting news from Google Ads! They’re making our lives a lot easier by simplifying the process of enhanced conversions into one convenient toggle switch. This means I can now enjoy more accurate conversion tracking with minimal setup effort.

Google is streamlining one of its key measurement tools by merging enhanced conversions for web and leads. By doing so, I can utilize multiple data inputs simultaneously, offering me more precise tracking with fewer hurdles.

What’s happening. Google Ads is consolidating its enhanced conversions into a single system. The best part? I no longer have to choose just one implementation method!

I can send user-provided data through various channels like website tags, Data Manager, and API integrations all at once. The prior separation between ‘enhanced conversions for web’ and ‘enhanced conversions for leads’ is disappearing, saving me from unnecessary complexity.

What’s changing and when: By June 2026, Google Ads is allowing the intake of user-provided data from website tags, Data Manager, and API connections. This collective approach is set to enhance conversion accuracy and boost bidding performance.

The switch to a single feature with an easy toggle removes the need for me to fuss over method selection like tag vs API.

Why I care. This update is a game-changer for conversion tracking during a time when data signals are vanishing. By utilizing multiple data sources, Google Ads can match conversions more precisely, which boosts my bidding efficiency and campaign successes. It also removes the technical obstacles, giving me seamless access to better data without needing to stick to one integration method.

Impact on advertisers. No action is required from me or any existing users if the customer data terms have already been agreed to. New users have the flexibility to enable enhanced conversions at both the account and individual conversion action levels, with the option to opt-out at the conversion action level if needed.

How to enable it (quick take). At the account level, I’ll simply go to Goals → Settings, enable enhanced conversions under Customer data use, and accept the data terms. For individual conversion actions, I can set up or edit a conversion action, enabling enhanced conversions during the process and agreeing to data terms.

Yes, but. To leverage enhanced conversions, I must agree to Google’s Data Processing Terms and ensure I’m complying with its expanding use of first-party data, a crucial step today.

Bottom line. Google is quietly pushing for broader adoption of user-provided data by making setup simpler. For me, this means improved performance with less manual input. I’m getting richer conversion data feeding into my bidding strategies and optimizations, and I can achieve greater results while simplifying my overall measurement strategy.

Inspired by this post on Search Engine Land.

April 10, 2026
Explore Google’s New Developer Hub for Ad Tools and Insights

I’ve recently discovered some exciting news from Google that’s perfect for those of us who rely on their ad tools and measurement resources. Google has just launched a developer hub that’s set to make our tech-driven advertising tasks a lot smoother.

The new Developer Hub centralizes everything into one easy-to-navigate destination, which promises to simplify our experience when building, automating, and scaling ad campaigns.

What’s Happening. Google is introducing the Advertising and Measurement Developers Hub. This centralized site is designed to give us seamless access to an array of tools and resources across their ad ecosystem. Say goodbye to hunting for documentation in multiple places!

The Hub organizes resources for products like the Google Ads API, Google Analytics, and publisher tools such as AdMob and Google Ad Manager into convenient categories including advertising, tagging, and measurement.

How It Works. It features a streamlined homepage where I can quickly access documentation, blog updates, and community channels. Plus, there are dedicated sections to explore products, connect with support, and engage with Google’s developer relations team.

Why We Care. For anyone deep into using Google’s tools, like me, this is a game-changer. The ease of access to advanced tools for automation, tracking, and optimizing campaigns can really boost efficiency. This new hub makes it nearly effortless to take advantage of Google’s robust ad tech ecosystem.

The Big Picture. As our advertising efforts increasingly lean on automation and APIs, Google is bolstering the infrastructure to support developers and technical users managing complex integrations.

Zoom In. New features I think are worth noting include a ‘meet the team’ section, a centralized support page with links to Discord and GitHub resources, and a media hub featuring content like Ads DevCast.

What to Watch. It’ll be interesting to see if this hub becomes the go-to entry point for developers across Google’s ad products, especially as more AI and measurement tools roll out.

Bottom Line. Google is betting big on developer support with this hub, anticipating that it will drive innovation and adoption within its ad tech ecosystem.

Dig Deeper. For more details, check out the full story on the Google blog: Introducing the Google Advertising and Measurement Developers Hub!

Inspired by this post on Search Engine Land.

April 8, 2026
Discover Google Ads API v23.2: Enhancements and Insights

I’m excited to share that Google has released version 23.2 of its Ads API, bringing several exciting updates that enhance video, app campaigns, and audience planning tools.

What’s New in This Release?

First, there’s the new VideoEnhancement resource. It now allows me to identify whether a video ad is Google-generated or advertiser-provided. This provides much-needed clarity on how ads are enhanced automatically.

Additionally, the AppTopCombinationView resource offers read-only insights into top-performing asset combinations in app campaigns, a valuable tool for optimizing my campaign strategy.

For those utilizing Demand Gen campaigns, I can now disable the hotel feed using HotelSettingInfo.disable_hotel_setting. This gives me more control over my ad placements.

This update also introduces a new conversion metric for tracking indirect first in-app installs across Campaign, Customer, and AdGroup resources, giving me deeper insights into conversion performance.

Moreover, enhancements to ContentCreatorInsightsService and ReachPlanService means I can further refine my content strategies and audience reach planning.

Steps to Upgrade

To benefit from these updates, I’ll need to upgrade to v23.2 by updating both client libraries and client code. Fortunately, all updated libraries and code examples are already available.

Join the Live Walkthrough

If you’re looking for more information, I recommend attending Google’s live release walkthrough on March 26 at 11am ET. It will be streamed live on Discord and YouTube, and a recording is provided afterward.

Why This Matters

The addition of the VideoEnhancement resource addresses a significant gap in Performance Max reporting. For those of us developing custom reporting tools, this means improved visibility into creative performance.

Final Thoughts

Although this release is part of Google’s routine updates, the enhancements, particularly in the VideoEnhancement resource, are worth noting. It’s a significant step forward for developers like myself working on Performance Max creative reporting.

Inspired by this post on Search Engine Land.

March 27, 2026
Navigate Google’s New Rule on Duplicate Lookalike Lists
I recently discovered an important update from Google affecting how I run Demand Gen campaigns using Lookalike user lists. Starting April 30, Google will block creating duplicate Lookalike lists via the Google Ads API and return an error code for any breaches.

This update might seem quiet, but its implications are significant, especially for those of us utilizing automated systems or third-party tools. Google is now enforcing a uniqueness check to prevent duplicates that have identical seed lists, expansion level, and country targeting.

Why do I care about this change? An unaddressed error could disrupt the workflow of my campaigns if I don’t update my integrations in time.

Here’s what I plan to do:
- Audit my current Lookalike lists and reuse those that already align with my goals instead of creating new ones.
- Update my API error handling processes to catch the new DUPLICATE_LOOKALIKE error code in versions v24 and above, or RESOURCE_ALREADY_EXISTS in older versions.
The bottom line is, while this change is housekeeping, the deadline is firm. I need to ensure my campaigns are technically prepared before the end of April to maintain stability in Google’s systems.

If you’re interested in a deeper dive, I highly recommend checking out Google’s blog post detailing these changes: Upcoming changes to Lookalike user lists in the Google Ads API, starting April 30, 2026.

Inspired by this post on Search Engine Land.
March 23, 2026
Unlock AI Insights with Google’s New Ads DevCast for Developers

I’ve been eagerly following the latest developments from Google, and their new Ads DevCast is truly a groundbreaking resource for developers like me. This initiative offers technical insights into Google Ads and highlights how AI-driven changes are transforming ad APIs.

The new show is hosted bi-weekly by Cory Liseno, as part of the Google’s Advertising and Measurement Developer Relations team. Ads DevCast focuses on deep technical dives across key tools like Google Ads, Google Analytics, and Display & Video 360. It feels like a direct line to the experts who are constantly innovating in our field.

What’s interesting here is that Ads DevCast complements Ads Decoded, which is more about campaign strategy, hosted by Ginny Marvin. It’s specifically designed with us developers in mind, highlighting the need for a specialized approach to understanding these platforms.

The first episode, intriguingly titled “MCPs, Agents, and Ads. Oh My!”, delves into the “agentic shift” that Google is observing. With AI agents becoming the main users of ad APIs, this shift is something we’re all keenly interested in.

For those of us deeply involved with Google’s ad tools, Ads DevCast is an invaluable resource. It helps us stay ahead of technical evolutions, discover new capabilities quickly, and build efficient integrations in a landscape increasingly dominated by AI.

I see Google broadening the horizon from a niche “Ads Developer Community” to a wider “Ads Technical Community.” This change allows marketers to carry out technical tasks without needing exhaustive development cycles.

As a pilot project, Ads DevCast is still very much in development, and Google is actively seeking feedback from us to refine future episodes. It’s exciting to know we can influence its direction.

This initiative reinforces Google’s commitment to keeping us in the loop with their latest innovations, enabling us to adapt quickly and effectively in an AI-first world. Check out Ads DevCast if you haven’t already!

Inspired by this post on Search Engine Land.

March 20, 2026
Google’s Big Shift: Customer Match Uploads Change Coming in April 2026

Recently, I discovered that Google is making a significant change that could impact how I manage ads. Starting from April 1, 2026, Google will block any inactive developer tokens from uploading Customer Match data through the Google Ads API.

In a heads-up to developers like me, Google has sent out messages explaining this upcoming change. If I haven’t uploaded Customer Match data using my developer token in the last 180 days, I won’t be able to do so through the Ads API anymore.

What’s changing: If I fall into that inactive category after April 1, any attempts to upload Customer Match lists through the Google Ads API will simply fail. Google advises moving these tasks to the Data Manager API. I’m reassured that this change only affects Customer Match uploads; other campaign management activities will continue as usual in the Google Ads API.

Why Google says it’s doing this: According to Google, the Data Manager API provides a more modern and unified data ingestion system across its platforms, featuring stronger security protocols. It also offers functionalities that aren’t available in the Ads API, such as confidential matching and improved encryption, reflecting Google’s push for centralized and secure audience data management.

Why this matters to me: If neither I nor my developers have interacted with Customer Match uploads over the last six months, this could be a sudden disruption. Post-April 1, 2026, this previous routine will be obsolete, causing errors in place of successful uploads.

The takeaway: I need to verify if my developer token has been recently used for Customer Match and plan for a transition to the Data Manager API before Google implements this new policy.

First noticed: This update was initially spotted by Paid Search specialist Arpan Banerjee, who shared the information he received from Google on LinkedIn.

Inspired by this post on Search Engine Land.

March 4, 2026
Google’s New $5 Budget Rule for Demand Gen Campaigns: What You Need to Know

Starting April 1, 2026, Google will require that all Demand Gen campaigns in the Google Ads API maintain a $5 daily minimum budget.

What’s happening: To ensure better performance, Google is implementing a rule that demands a minimum daily budget of $5 USD, or the local equivalent, for all Demand Gen campaigns. This directive aims to facilitate a smoother transition through the ‘cold start’ phase, giving Google’s models the necessary data to optimize effectively.

This change will be implemented as an unversioned API update and will impact all pathways through which ads are bought.

Technical details:

In API v21 and beyond, if a campaign budget dips below the required threshold, a BUDGET_BELOW_DAILY_MINIMUM error will be triggered. Further specifics about the error can be found in the error metadata.

For those using API v20, a generic UNKNOWN error will be shown, referencing the specific validation failure within the unpublished error code field.

The rule applies whenever budgets, start dates, or end dates are altered in ways that result in daily spending falling below the $5 mark. This includes both daily budgets and those allocated over a flighted schedule.

Impact on existing campaigns: Campaigns currently operating below the minimum threshold can continue as they are. However, any adjustments to budgets or scheduling will necessitate adherence to the new budget requirement.

Why we care: For advertisers and developers, this adds an additional layer of compliance in campaign management workflows. Systems must be updated to identify and handle these validation errors before campaigns are launched.

The bottom line: Google aims to standardize a minimum investment level for Demand Gen campaigns, prioritizing performance stability and compelling advertisers to adjust their budgets and automation strategies accordingly.

Inspired by this post on Search Engine Land.

March 3, 2026

←Previous Page

1 2 3