Hey there! I’m excited to introduce you to something that has truly changed the way I approach coding projects—the Profound API Cookbook. If you’ve ever started with the thought, ‘I want this number,’ and wished for a seamless way to transform that into runnable code, this is for you.
Imagine having a collection of end-to-end recipes right at your fingertips, perfectly layered on top of our REST API references. This isn’t just about coding; it’s about enhancing your workflow and efficiency in a whole new way. Each recipe is designed to guide you from concept to execution with ease.
As a developer working with Google Ads, I’ve recently learned that Google is encouraging us to migrate offline conversion imports from the Google Ads API to the Data Manager API by June.
Starting June 15th, Google plans to phase out offline conversion imports through the Google Ads API for some developers, which could impact how we track conversions.
For those of us who depend on these offline conversion imports, including enhanced conversions for leads, it’s crucial to transition our workflows to the Data Manager API to ensure seamless operations.
Details. We’re now aware that after June 15, offline conversion imports using the UploadClickConversions request will become non-functional for accounts inactive with this feature for the past 180 days, as per Google’s notification to developers.
This change specifically targets offline conversion imports and enhanced conversions for leads, while all other operations in the Google Ads API will continue as usual.
According to Google, we should transition our workflows to the Data Manager API moving forward.
Why this matters. Offline conversion imports play a critical role in measuring leads, sales, and other actions occurring offline. Without timely migration, our conversion data might not integrate into Google Ads, affecting reporting, attribution, and automated bidding performance. This shift aligns with Google’s broader strategy towards AI-driven, centralized data infrastructure.
The bigger picture. This move signifies Google’s ongoing effort to centralize data ingestion and streamline measurement infrastructure through automation.
Google promotes the Data Manager API as a comprehensive system for sending advertiser data into Google Ads, embracing functions like Customer Match and conversion imports, with additional capabilities for developers.
Between the lines. With attribution leaning more on privacy-centric, first-party data, Google is narrowing down its advertising tools to more integrated systems that leverage AI-driven campaign products.
For developers and platforms, the migration necessitates updates to integrations, the redevelopment of import processes, and the testing of new workflows ahead of the deadline.
What’s next. We can continue using the Google Ads API for non-offline conversion functions, but must shift any workflows involving offline conversion imports to the Data Manager API before June 15th to avoid disruptions.
First spotted. I came across this update through a post by PPC Specialist Arpan Banerjee, who shared the communication he received on LinkedIn.
I’ve recently delved into Google’s exciting release of Ads API version 24.1, and it’s packed with valuable updates for advertisers. This version brings us advanced reporting capabilities, expanded AI campaign testing, and improved security measures.
In this update, Google has prepared us for their upcoming data retention policy changes, which will commence next year—something I believe every developer should be ready for.
Why we care. The latest release highlights three crucial areas: performance visibility, creative control, and testing automation, which are becoming vital for advertisers like me.
What’s more, brands now have greater control over creative displays in Demand Gen campaigns, overcoming the typical limits imposed by automation. It’s a significant update that I’m excited to explore further.
Those of us who lean heavily on reporting infrastructures should also be mindful of Google’s impending 37-month data retention limit, set to impact historical performance analysis come 2026.
Mobile reporting gets more granular. One of the features I’m most thrilled about is the new mobile device platform segment that allows for reporting by operating system.
With the new segments.mobile_device_platform field, I’m able to differentiate performance across iOS and Android, a game-changer for app marketers and ecommerce advertisers alike.
Demand Gen adds classic image support. I love how Google is providing us with more creative control in Demand Gen campaigns, specifically through the classic_display_images field.
This new field allows us to upload and display static image ads exactly as designed, which is perfect for maintaining branding consistency without AI alterations.
Passkeys come to Google Ads. Security is always a top concern of mine, so I’m pleased to see the inclusion of the passkey_enabled field to boost account security through passwordless authentication.
Experiment support expands. I’ve noticed that Google has significantly enhanced the support for Experiments, allowing us to run and analyze tests across AI Max, Video, Demand Gen, and Performance Max campaigns.
This update also enables us to view metrics such as clicks and conversions more transparently, making experiment analysis straightforward and insightful.
A major data retention change is coming. From June 1st, Google Ads and related APIs will enforce a 37-month data retention limit, something I must prepare for to avoid disruptions in performance analytics.
The release includes a new error code: DateRangeError.REQUESTED_DATE_GRANULARITY_NOT_SUPPORTED, and it’s essential that I update reporting workflows accordingly.
What’s next. I’ve already checked out the updated client libraries and code samples for v24.1, and I plan to participate in Google’s live walkthrough on Discord, YouTube Live, and LinkedIn Live for additional insights.
In my latest venture into Google Analytics, I’ve discovered exciting news. Google is enhancing its Analytics Data API by adding cross-channel conversion reporting. Although it’s still in the alpha phase, developers like myself now have programmatic access to both paid and organic conversion data in a unified view.
What’s happening. Currently in alpha, this new feature lets users pull conversion data across various channels through the API, mirroring data from the Conversion performance report in the Analytics interface.
For developers, this means we can now capture the same insights without the need for manual reporting, making the process smoother and more efficient.
Why it matters. In a world where digital measurement is increasingly complex, having a unified view of performance across both paid and organic channels is crucial. This feature empowers teams to automate their reporting processes, seamlessly integrate data into existing systems, and build advanced analysis workflows.
It’s a game-changer for businesses juggling multiple platforms, helping to centralize performance data for better strategic decisions.
The caveat. Not every Google Analytics property has access to this feature yet. Google is actively working to broaden availability, so it’s wise to connect with support teams to verify eligibility.
What to watch:
The transition from alpha to wide availability of the feature.
How advertisers leverage this API access to create customized attribution models.
Potential addition of more reporting capabilities to the Data API.
Bottom line. Google’s integration of cross-channel conversion data into the API equips advertisers and developers like me with more control over how we access, analyze, and act on performance data. You can find more information about this update here.
Google Ads API v20 will officially sunset on June 10, 2026, and I need to make sure I’m ready. If you’re like me, using older API versions, it’s crucial to act now to avoid any service disruptions.
Google has made it clear: after the cutoff date, any requests made to v20 will fail. This means we must move to a newer version if we want to maintain access to vital tools for managing our campaigns.
Why I Care. If I don’t upgrade in time, my automated workflows—ranging from reporting to bidding—could suddenly become dysfunctional. This could lead to data gaps, performance issues, and operational headaches. By transitioning early, I can ensure smooth operations and avoid last-minute scrambles.
What I’m Doing. Google encourages swift upgrades by providing helpful resources like release notes and upgrade guides. I am also using the Google Cloud Console to keep an eye on recent API activities and pinpoint the exact methods and versions my projects engage with.
Between the Lines. While API sunsets are nothing new, the potential impact can be daunting. Relying on custom scripts, tools, or third-party platforms means missing the upgrade deadline could disrupt essential workflows like reporting and campaign automation.
The Bottom Line. This deadline is serious and comes with real consequences. If I don’t upgrade to a newer Google Ads API version by June 10, I risk losing access to my tools entirely, something I can’t afford to let happen. More details here.
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.
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.
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.
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.
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.
