Uncategorized

The Shift from Conversion to Post-Sale Operations Search engine optimization has historically lived on the front lines of the marketing funnel. For decades, the primary mandate of an SEO specialist was to capture search traffic, guide users to a landing page, and convert that traffic into leads or sales. Once the conversion occurred, the SEO’s job was done, and the customer was handed over to account management, customer success, or product delivery teams. Artificial intelligence has fundamentally disrupted this linear funnel. As search engines evolve into generative AI engines, recommendation systems, and autonomous agents, the signals they rely on to evaluate business credibility are shifting downstream. When an AI engine decides whether to recommend a B2B platform, a local service provider, or a SaaS product, it does not just look at landing page copy or keyword frequency. It evaluates real-world, post-sale signals: onboarding speed, integration depth, performance outcomes, and authentic customer advocacy. The challenge is that this critical proof is locked away inside operational siloes. It lives in customer relationship management (CRM) systems, Zendesk helpdesk logs, Slack channels, and internal quarterly business reviews. Because this information is hidden behind corporate firewalls, it remains completely invisible to the LLMs, web crawlers, and AI agents that determine modern search visibility. This creates a massive opportunity for forward-thinking SEOs: by moving into the operational core of the business, they can harvest this latent customer success data, codify it, and turn it into machine-readable proof that powers AI recommendation engines. The 5 Stages of the OPIDC Framework To bridge the gap between real-world customer success and AI visibility, we can look at a specialized operational framework: OPIDC. This acronym stands for Onboarded, Performed, Integrated, Devoted, and Codified. The first four stages of this model map directly to the standard customer-success lifecycle that service, B2B, and SaaS organizations already run daily. The fifth stage, Codified, is where SEO enters the picture to translate operational wins into structured, machine-legible evidence. The OPIDC Stage Traditional Customer Success Equivalent Onboarded Onboarding, implementation, initial setup Performed Adoption, first value, time-to-value, baseline success Integrated Retention, account expansion, organizational stickiness Devoted Advocacy, loyalty, unsolicited recommendations Codified The SEO layer: turning experiences into machine-readable proof By understanding how these stages function, we can see that the operational core of a business is not just a mechanism for retaining current clients; it is the raw material required to acquire future ones through AI search channels. How OPIDC Fits into the 15-Gate AI Engine Pipeline The five stages of the OPIDC framework represent the human or “people” phase of search and discovery. However, they do not exist in a vacuum. Instead, they sit directly behind the first ten gates of the AI engine pipeline, which dictate how assistive engines process your brand’s digital footprint. The complete 15-gate pipeline spans the following sequence: Discovered: The crawl and discovery of your assets. Selected: The initial algorithmic choice to evaluate your content. Crawled: The retrieval of raw page data by search bots and LLM parsers. Rendered: The execution of code to assemble the visual and structural page. Indexed: The permanent cataloging of your brand’s data. Annotated: The semantic mapping where the engine labels your content entities. Recruited: The retrieval stage where your brand is pulled into consideration for a user query. Grounded: The verification of facts against trusted knowledge bases. Displayed: The visual rendering of your brand within an AI chat interface or search snippet. Won: The user’s choice to click, converse, or convert. Onboarded: The post-sale delivery validation. Performed: The realization of measurable success. Integrated: The structural retention of your service. Devoted: The organic advocacy generated by the user. Codified: The translation of steps 11–14 back into steps 1–10. This 15-gate sequence expands upon the foundational concepts of Assistive Agent Optimization (AAO) and Answer Engine Optimization (AEO). In this paradigm, the funnel is a continuous loop. The final step—Codifying—feeds right back into the Discovery and Indexing gates, creating a self-sustaining marketing flywheel. OPID is an Operational Reality, Not a Marketing Gimmick For this framework to succeed, marketing teams must recognize that the four OPID stages are operational realities, not creative exercises. These stages are where the actual delivery of value occurs, and they are managed by customer success managers, technical support teams, implementation specialists, and account executives. If you approach these technical teams asking for “blog ideas,” they will likely ignore you. Their priority is resolving support tickets, reducing churn, and hitting implementation deadlines. They do not have time to brainstorm content ideas for a standard marketing calendar. If you reframe the conversation, the dynamic changes. When you explain that the case studies, client metrics, and daily workflows they generate are the exact signals AI search engines use to recommend your company over competitors, you turn them from gatekeepers into active collaborators. You are offering to capture their operational wins and turn them into visible assets that support their own churn-reduction goals. When this operational alignment functions properly, the sales dynamic shifts. For instance, industry expert James Dooley noted that his sales teams now spend most of their time filling out onboarding forms rather than pitching. Because AI engines have already crawled, analyzed, and validated the company’s real-world delivery metrics, prospective buyers arrive at the sales call already convinced. Inquiry volume may decrease because unqualified leads are filtered out early, but close rates and transaction values rise because the buyers who do reach out have already verified the company’s operational success through AI recommendations. The Dual-Customer Dilemma: Meeting the Needs of Humans and Agents In the age of AI search, every business must learn to serve two distinct audiences: the human buyer and the autonomous AI agent. While both demand proof of delivery, they consume and evaluate that proof in entirely different ways. The fundamental challenge of modern business is that your best work is often invisible. When your implementation team successfully onboarded a client ahead of schedule, or your software platform integrated with a complex legacy system, that success was experienced only by the

It is one of the most satisfying scenarios a paid media manager can experience. You log into your advertising dashboard and find a campaign that is performing exceptionally well across every key performance indicator. The cost per acquisition (CPA) is low, the return on ad spend (ROAS) is outstanding, lead quality meets your exact benchmarks, and the average order value (AOV) is perfectly aligned with your business goals. Naturally, when stakeholders or clients see these stellar metrics, their immediate reaction is to scale. The directive comes down swiftly: double the budget and keep the momentum going. It seems like a simple, logical next step. If you are generating a 5x return on a $5,000 budget, it stands to reason that a $10,000 budget should yield the same ratio of success, right? Before you adjust that daily spend slider, it is critical to pause. While scaling your budget can unlock incredible growth, it only works if there is actual, productive room for that additional capital. If your campaign has already captured the available demand and maximized its efficiency, pumping more money into it will not yield a linear increase in revenue. Instead, it often leads to skyrocketing acquisition costs, diluted audience targeting, and diminishing returns. Understanding when to scale—and, more importantly, when to hold back—is what separates average advertisers from elite performance marketers. Below, we will explore the underlying mechanics of ad auctions, algorithmic learning phases, and market dynamics to explain why high-ROAS campaigns do not always deserve a higher budget, and how you can make data-driven decisions to scale your paid media accounts sustainably. What to evaluate before increasing your budget Before allocating more capital to an active campaign, you must thoroughly evaluate whether its infrastructure, target market, and the platform’s underlying algorithms can support the increased scale without sacrificing overall efficiency. Learning periods and algorithmic volatility Modern paid search and social platforms rely heavily on machine learning algorithms to optimize bid placement and targeting. Any substantial adjustment to a campaign’s daily budget, target CPA, or target ROAS acts as a disruption to these automated systems, often triggering a brand-new learning period. Within Microsoft Advertising, for example, changes to budgets or performance targets that exceed approximately 15% are highly likely to introduce volatility. During this recalibration phase, the bidding engine shifts from “exploitation” (using known data to get conversions) to “exploration” (testing new search queries, placements, and user behaviors to find more volume). This shift can result in short-term fluctuations in both cost efficiency and conversion volume while the system stabilizes. If you aggressively double or triple a campaign’s budget overnight, you risk throwing a finely-tuned, high-performing asset into a state of flux. The algorithm may struggle to find profitable placements at that higher spend rate, ultimately damaging the very efficiency that made the campaign attractive in the first place. To mitigate this risk, a more stable, systematic approach is to scale your budgets incrementally—increasing spend by 10% to 15% week over week—while actively managing stakeholder expectations regarding the timeline for growth. Validate that your performance data is accurate A phenomenal ROAS on a dashboard is only valuable if it translates directly to real-world business profitability. Before scaling up your monetary investment, you must conduct a rigorous audit to confirm that your conversion tracking is flawless. Ask yourself the following questions: Are your conversion tags firing accurately, or are they double-counting transactions due to page-refresh loops or duplicate pixel setups? Does your tracking account for post-purchase refunds, cancellations, or spam leads? Are your conversion values dynamic and reflective of actual profit margins, or are they static, estimated averages? If you are running lead generation campaigns, does the quality of those leads hold up when passed to your sales team, or are you scaling high-volume, low-intent inquiries? Before escalating your spend, document your conversion parameters and verify that your downstream business data aligns with your platform-reported metrics. Scaling a campaign with broken or inflated tracking metrics will only accelerate waste. The reality of market saturation and audience fatigue Every target audience, keyword set, and geographic region has a finite ceiling. If you continually pour budget into a single campaign without expanding its core parameters, you will eventually hit a point of market saturation. When you oversaturate an audience, the ad platform is forced to show your ads to the same group of users repeatedly, driving up frequency caps and banner fatigue. Alternatively, the bidding algorithm may be forced to bid on lower-intent search queries just to spend your newly allocated budget. Sustainable scaling often requires structural expansion, which might include: Entering new geographic markets or testing localized variations of your offers. Introducing fresh, highly-targeted audience segments or lookalikes. Splitting your budgets across a network of distinct campaigns rather than overloading a single, fragile campaign structure. Define the ultimate goal: Efficiency or scale? There is a fundamental, mathematical trade-off between volume and efficiency in digital advertising. As you scale your spend, your cost per acquisition will almost always rise, and your overall ROAS will decrease. This is because platforms naturally prioritize the cheapest, highest-converting traffic first. To get more conversions, the system must bid on more competitive, expensive search placements or audiences. Before making any budget decisions, you must align with your business stakeholders on the primary objective. Are you trying to preserve peak efficiency and maximum profitability per unit? Or are you looking to aggressively grow overall revenue volume, even if it means accepting a lower profit margin per sale? Having absolute clarity on these boundaries prevents friction when your 6x ROAS predictably settles into a 4x ROAS at double the spend. 3 strategic questions to ask before increasing budget To determine if a high-performing campaign is truly ready to absorb more spend, run it through this strategic diagnostic framework. 1. Do you actually have impression share room to grow? Impression share and share of voice are your best diagnostic tools for measuring a campaign’s growth potential. If a campaign is performing brilliantly, check your Competitive Metrics in your reporting

Google has officially confirmed the completion of its second major algorithm update of the year: the Google May 2026 core update. This critical search update began rolling out on May 21, 2026, and concluded its deployment on June 2, 2026, spanning a total of 12 days. For website owners, SEO professionals, and digital publishers, this marks the end of nearly two weeks of heightened search engine volatility and shifting organic rankings. As search landscapes continue to shift under the weight of artificial intelligence and changing user behaviors, core updates like this one serve as essential recalibrations of Google’s ranking systems. Understanding the mechanics of the May 2026 core update, looking at the data from its deployment, and knowing how to steer your content strategy forward are vital for maintaining and growing your search visibility. Inside the Rollout: Timeline and Key Volatility Spikes The Google May 2026 core update was deployed with notable speed compared to some of the multi-week rollouts of previous years. Officially initiated on a Thursday afternoon (May 21, 2026), the effects of the update were felt almost immediately across global search results. Unlike historical rollouts that slowly simmered before showing visible impacts, this update hit the ground running. SEO trackers and site administrators observed several distinct waves of volatility throughout the 12-day rollout window: First Wave (Saturday, May 23): Just 48 hours after the initial announcement, the SEO community reported substantial fluctuations in organic rankings. This initial spike suggested that the core update’s foundational algorithm adjustments were quickly indexed and applied to live search results. More details on this early volatility were captured by Search Engine Roundtable on May 23rd. Second Wave (Saturday, May 30): Exactly one week after the first major shift, a second, even more pronounced wave of volatility swept through the SERPs (Search Engine Results Pages). Many webmasters who thought their rankings had stabilized after the first weekend saw further adjustments. This secondary wave was heavily documented across tracking suites, as noted in the May 30th volatility reports. The Pre-Completion Tremor (June 1 – June 2): In the final 24 hours leading up to the official completion announcement, SEO monitoring tools flagged yet another sharp spike in ranking movement. This final adjustment phase, detailed in reports on late-stage volatility, represents the final settling of the core algorithms before Google officially updated its search status. Data from major SEO platforms like Semrush confirmed these distinct peaks. The 30-day volatility charts showcased extreme spikes on May 23 and May 30, with a baseline level of elevated movement bridging the days between. This indicates that while the overall update was completed in 12 days, it was characterized by sudden, high-intensity shifts rather than a slow, gradual realignment. What Google Is Saying About the May 2026 Core Update Throughout the rollout, Google maintained its standard communications protocol. The tech giant updated its official Search Status Dashboard, confirming the release of the update and noting that the rollout could take up to two weeks to fully resolve across all data centers globally. Additionally, Google Search Central shared insights via their official LinkedIn profile, stating: “This is a regular update designed to better surface relevant, satisfying content for searchers from all types of sites. The rollout may take up to 2 weeks to complete.” This statement reinforces Google’s ongoing objective: refining its automated ranking systems to ensure that search queries yield helpful, original, and deeply satisfying content. The emphasis on “all types of sites” suggests that Google’s systems are striving to level the playing field, ensuring that smaller independent publishers, niche blogs, and large-scale enterprises are all evaluated under the same rigorous helpfulness standards. Contextualizing 2026: Google’s Rapid Update Cycle To truly understand the May 2026 core update, we must view it as part of a larger, ongoing sequence of search algorithm refinements. This is not an isolated event; rather, it is the second core update of 2026 and comes on the heels of several major system overhauls earlier in the year. Here is a breakdown of how the first half of 2026 has shaped up in terms of Google search updates: February 2026: The year started with the release of the February 2026 Discover update, which specifically targeted how content is curated and displayed within the highly personalized Google Discover feed. March 2026: March was an incredibly busy month for search professionals. Google rolled out the massive March 2026 core update, which ran from March 27 to its completion on April 8. Simultaneously, Google launched the March 2026 spam update to clean up low-quality, scaled programmatic content and abusive link behaviors. May 2026: The newly completed May 2026 core update builds directly upon the foundational changes introduced during the spring updates, refining how the search engine rewards user-first value over search-engine-first optimization. A Look Back at 2025 Core Updates The rapid pace of 2026 updates follows a highly active 2025. Keeping track of these dates is crucial for forensic SEO audits, as it allows webmasters to match traffic drops or gains with specific system rollouts: The December 2025 core update began on Dec 11 and concluded on Dec 29 (covered at its launch here). The June 2025 core update rolled out between June 30 and July 17 (covered at its launch here). The March 2025 core update occurred between March 13 and March 27 (covered at its launch here). What to Do If Your Site Was Impacted by the May 2026 Core Update Now that the May 2026 core update is fully complete, the data in your Google Search Console, Google Analytics, and rank tracking software should reflect the new baseline of your organic visibility. If you notice a sudden drop in clicks, impressions, or keyword rankings during the late-May to early-June window, it is highly likely your site was impacted by this update. If your site’s rankings have taken a hit, it is important to avoid making immediate, reactive changes out of panic. Google’s core updates do not target individual sites or penalize specific pages in the

Search technology has recently achieved something truly remarkable. At the exact moment search should be cementing its place as the most critical and high-value marketing channel for corporate clients, a significant portion of the search industry has chosen to debate itself into irrelevance. Instead of seizing a massive structural evolution, practitioners are locked in an inward-facing linguistic civil war. The core of this disagreement isn’t actually about technical mechanics or search engine algorithms. The real conflict is about ownership. It centers on three fundamental questions that will define the commercial future of digital marketing: Who gets to define what search becomes next? Who gets the budget to build out generative search strategies? Who gets to explain what happens to brand visibility when search stops being a simple directory of blue links and becomes an active machine that recommends answers, highlights brands, and drives user actions? The dismissive phrase “it’s just SEO” has caused immense damage to the professional search landscape. On the surface, it sounds calm, measured, and experienced—the kind of statement a seasoned search veteran might use to quiet a room full of panicked clients. Yet, beneath its reassuring exterior, it is not a forward-looking strategy. It is an industry meme that actively constrains one of the most lucrative commercial opportunities search marketers have encountered in a generation. Why Memes Matter to the Search Industry To understand why this linguistic division has taken such a firm hold on the search community, we have to look at how ideas spread. The study of memetics is far from a modern internet phenomenon. Evolutionary biologist Richard Dawkins coined the term in his landmark 1976 book, The Selfish Gene. Dawkins proposed that ideas, behaviors, and catchphrases spread through human culture using the same biological logic that genes use to propagate through a population. They replicate, they mutate, and they compete for survival. Crucially, the concepts that survive are not necessarily the most accurate or the most useful; they are simply the easiest to copy and transmit. Psychologist Susan Blackmore expanded on this framework in her book, The Meme Machine. Blackmore argued that humans are essentially biological processing units designed to imitate, store, and pass along cultural information. The ideas that colonize our minds are those that are the stickiest. Consider the song “Happy Birthday to You.” The melody is basic enough for a toddler to memorize after a single hearing, the lyrics require no formal training to learn, and the social context—a celebration with cake and friends—gives everyone in the room an incentive to sing along. Nobody officially coordinates the preservation of the song; it simply wins the ongoing mental competition for memory space. Traditional holiday songs like “Jingle Bells” operate on the same premise. They require no licensing body or central authority to survive because repeating them signals belonging to a shared culture. Professional clichés, corporate slogans, and industry jargon spread in the exact same manner. They do not survive because they represent objective truth. They persist because they are easy to repeat, socially useful to the person saying them, and emotionally comforting to an audience facing change. In the survival of memes, factual accuracy is rarely a dominant selection criterion. This is the exact challenge currently facing Search Engine Optimization (SEO) and Generative Engine Optimization (GEO). How ‘It’s Just SEO’ Became the Dominant Meme When the concept of Generative Engine Optimization first entered the wider digital marketing conversation, the reaction was split. One camp looked at generative search engines and recognized a fundamentally different user interface. They saw AI systems summarizing complex topics, directly citing sources, and generating synthetic answers in ways that bore little resemblance to a standard Search Engine Results Page (SERP). They realized that optimizing for these Large Language Models (LLMs) would require entirely new datasets, novel workflows, modified tracking metrics, and a shift in tactical execution. The other camp, however, saw a direct threat to their established authority. For a significant portion of the SEO influencer and agency community, the immediate response was containment. “It’s just SEO” became the defensive posture of choice. It quickly evolved from a passing observation into a rallying cry, and eventually, a tool to shut down discussion. The phrase succeeded because it is highly effective meme material: it is short, highly repeatable, and projects an aura of absolute certainty without requiring any real investigation into LLM mechanics. More importantly, it protected the existing industry hierarchy. If GEO is dismissed as “just SEO,” then the old power structures remain unchallenged. The same conference speakers retain their keynotes, the same agency models remain unquestioned, and the same consultants keep their retainers without having to adapt to how conversational search engines synthesize information. This defensive posture paved the way for a more damaging counter-meme: the label of the “GEO grifter.” This phrase did not just challenge the technical boundaries of generative search optimization; it actively attacked the integrity of anyone trying to study it. It turned professional curiosity into suspect behavior and framed early experimentation as opportunism. Instead of encouraging deep, collaborative exploration of how LLMs retrieve and cite information, it justified immediate dismissal. This is how consensus often forms in the digital space. High-profile voices push a simplified, dismissive framing, algorithms reward the resulting conflict with high engagement, and the constant repetition of the message is eventually mistaken for industry agreement. As this narrative spread, search professionals who repeated the dismissive phrase received social validation from their peers, while the clients they served began to view generative search as a completely separate business challenge. Clients Buy Certainty, Not Acronym Wars While search professionals argue on social media, business leaders and brand managers outside the SEO bubble have already moved ahead. They do not need a theoretical debate to tell them that the digital landscape is changing; they can see it themselves because they use generative AI platforms daily to conduct research and make decisions. At several major industry events, including BrightonSEO, audiences of marketing professionals were asked a simple question: “Who here is

As digital marketing continues to evolve toward automation and multi-format experiences, Google is taking a major step to unify its advertising ecosystem. Starting June 10, Google will begin rolling out official support for Demand Gen campaigns within the Display & Video 360 (DV360) API. This rollout is scheduled to reach full availability by June 24, marking a significant milestone for programmatic advertisers, ad-tech developers, and enterprise brands. By bringing Demand Gen resources directly into the programmatic API, Google is addressing a long-standing need for deeper integration, automation, and operational efficiency. The update allows advertisers to manage visually rich, social-first inventory with the same programmatic precision they apply to traditional display, video, and Connected TV (CTV) campaigns. Understanding the Shift: What is Demand Gen? To fully appreciate the impact of this API update, it is essential to understand what Demand Gen campaigns represent in Google’s advertising portfolio. Designed to succeed the legacy Discovery campaigns, Demand Gen campaigns are built specifically for today’s visually driven, fast-scrolling consumer. They leverage Google’s advanced artificial intelligence to deliver immersive, high-impact creative formats across Google’s most engaging touchpoints. Demand Gen campaigns primarily serve ads across several key environments: YouTube Shorts: Engaging, vertical, short-form video content that reaches billions of active viewers globally. YouTube In-Stream and In-Feed: High-visibility video placements that capture attention during active content consumption. Google Discover: A highly personalized, visual feed where users discover new interests and content. Gmail: Highly targeted, interactive promotions delivered directly to user inboxes. Unlike traditional search or display campaigns that rely heavily on explicit intent or simple banners, Demand Gen focuses on stimulating consumer interest and driving conversions through visual storytelling. By combining video and image assets into a single campaign type, Demand Gen helps brands capture attention and guide prospective customers from awareness to action. What the DV360 API Integration Changes Historically, managing Demand Gen campaigns required distinct workflows, often forcing media buyers and ad operations teams to toggle between different interfaces or utilize separate automation streams. The integration of Demand Gen into the DV360 API changes this dynamic entirely. With this update, developers and advertisers gain the ability to perform standard CRUD (Create, Retrieve, Update, and Delete) operations on Demand Gen resources programmatically. This includes direct API management of: Demand Gen Line Items: The core targeting and budgeting units within the DV360 hierarchy. Ad Groups: The structural elements used to organize targeting, bidding, and creative assets within those line items. Ad Formats: The specific creative templates and configurations used to render visually engaging ads across YouTube, Discover, and Gmail. Once the update is fully deployed, Demand Gen resources will be treated as first-class citizens within the DV360 API. They will appear seamlessly in standard line item and ad group list responses alongside other programmatic inventory types, such as standard display, video, and audio campaigns. Why the June 10 Rollout Requires Immediate Action For ad-tech developers, agencies, and enterprise brands utilizing custom API integrations, this update brings a critical technical caveat. Because Demand Gen resources will begin appearing in standard list queries, existing codebases must be prepared to handle these new objects. If your internal platforms, reporting dashboards, or automated optimization scripts pull lists of line items or ad groups from the DV360 API, they may soon receive unexpected data structures. Without proactive adjustments before the June 10 rollout, these new resource types could cause processing errors, break automated reporting pipelines, or skew internal data classifications. Google strongly advises all API partners and developers to audit and update their integrations ahead of the rollout. Ensuring your applications can gracefully parse, categorize, or filter the incoming Demand Gen data structures will prevent operational disruptions during the transition phase between June 10 and June 24. The Strategic Advantages for Advertisers and Agencies The transition of Demand Gen from a manual, UI-dependent feature to a fully supported API resource offers several strategic advantages for sophisticated advertisers and agencies. 1. Seamless Cross-Channel Workflows In modern digital advertising, operational efficiency is a primary competitive advantage. Managing campaigns across disjointed systems leads to fragmented data, higher human-error rates, and lost productivity. By enabling Demand Gen management via the DV360 API, enterprise teams can manage their programmatic display, CTV, video, and social-style Demand Gen assets within a single, unified workflow engine. 2. Advanced Programmatic Automation The ability to programmatically create, update, and delete Demand Gen resources opens up new possibilities for dynamic campaign orchestration. Advertisers can now build custom automation scripts that adjust Demand Gen campaigns in real-time based on external data feeds, such as local weather patterns, real-time inventory levels, local events, or proprietary customer relationship management (CRM) signals. 3. Simplified Reporting and Deeper Insights Consolidating data across multiple campaign types has long been a challenge for marketing analysts. With Demand Gen integrated directly into the DV360 API, developers can build unified reporting pipelines that automatically aggregate performance metrics. This allows for cleaner, faster data visualization and more reliable attribution modeling across different media formats. 4. Scaling Creative Orchestration Because Demand Gen relies heavily on creative assets to drive engagement, managing multiple asset variations across dozens of campaigns can quickly become overwhelming. Through API integration, creative management platforms and dynamic creative optimization (DCO) engines can programmatically push, update, and rotate creative elements within Demand Gen ad groups, ensuring that audiences always see the most relevant and high-performing variations. How to Prepare Your Tech Stack for the Update To ensure a smooth transition and take full advantage of these new capabilities, technical teams should implement a structured preparation plan: Audit Existing Queries Review all active API calls that retrieve lists of line items, ad groups, or campaign structures. Identify where your system might fail if it encounters a previously unrecognized line item type or ad group schema. Update your data validation rules to accommodate the new Demand Gen object types. Consult the Official Developer Documentation Google has provided technical details and guidelines on the upcoming changes. Developers should review the official announcement on the Google Ads Developers Blog to familiarize themselves with the precise

DV360 API Adds Demand Gen Support Google’s programmatic advertising suite is undergoing a major upgrade that will streamline how enterprise-level advertisers run visually-driven, AI-powered campaigns. Starting June 10, 2026, Google will begin rolling out support for Demand Gen resources within the Display & Video 360 (DV360) API. This rollout is expected to reach full availability by June 24, 2026, marking a significant milestone in Google’s efforts to unify and automate its modern advertising stack. For developers, agency partners, and programmatic advertisers who rely on automated workflows, this update bridges a critical gap. By bringing Demand Gen into the API fold, Google is enabling programmatic management of these highly engaging, multi-format campaigns. Here is a comprehensive look at what this update entails, why it matters for the programmatic ecosystem, and what steps developers need to take to prepare for the June launch. Understanding Demand Gen and Its Place in DV360 Before diving into the technical details of the API integration, it is important to understand why Demand Gen has become such a focal point for modern digital marketers. Launched as the next-generation evolution of Discovery campaigns, Demand Gen is designed to capture the attention of consumers across Google’s most visual and entertainment-focused touchpoints. This includes YouTube (including Shorts and In-Stream), Google Discover, and Gmail. Unlike traditional search or display campaigns, Demand Gen relies heavily on AI to optimize combinations of image and video assets, serving them to audiences when they are in an active state of consumption and discovery. These campaigns are built to drive conversions, site visits, and high-value actions by combining Google’s audience signals with visually compelling creatives. Historically, managing these campaigns at scale presented challenges for enterprise advertisers. While DV360 offers unparalleled reach and sophisticated programmatic targeting, the manual creation and optimization of complex, asset-heavy Demand Gen campaigns could be time-consuming. The lack of robust API support forced many teams to rely on manual UI updates or separate tools, creating friction in cross-channel campaign execution. The Technical Blueprint: What the API Update Introduces The upcoming API release directly addresses these challenges by offering programmatic control over Demand Gen structures. Starting June 10, developers will gain the ability to interact with Demand Gen elements programmatically through the DV360 API. According to the official Google Ads Developer Blog, the update introduces comprehensive CRUD (Create, Read, Update, and Delete) support for a variety of critical Demand Gen resources. These resources include: Demand Gen Line Items: Define budgeting, flighting, and core campaign parameters. Demand Gen Ad Groups: Manage audience targeting, bidding strategies, and structural groupings. Demand Gen Ad Formats: Programmatically handle the diverse mix of image, video, and text assets that power Google’s AI-driven ad placements. Once the system goes live, these new resources will not exist in a silo. Instead, they will be seamlessly integrated into standard line item and ad group list responses. This means that a standard query requesting campaign structures within a DV360 advertiser account will return Demand Gen objects alongside existing native programmatic formats, such as traditional display, video, connected TV (CTV), and audio line items. Why This Matters for Enterprise Advertisers and Agencies The integration of Demand Gen into the DV360 API is more than a minor technical update; it represents a major shift in how programmatic media buying can be scaled and optimized. There are several key reasons why this update is highly anticipated by the industry: 1. Unified Programmatic Workflows Large agencies and in-house marketing teams rarely manage campaigns manually through a single user interface. Instead, they use proprietary dashboard tools, multi-DSP platforms, and custom software to coordinate media buys across multiple channels. By adding Demand Gen support to the API, Google allows these custom platforms to manage the entire lifecycle of a Demand Gen campaign without requiring users to log into the DV360 user interface. This reduces operational fragmentation and keeps campaign management consolidated under a single, unified workflow. 2. Automation at Scale Managing asset-rich campaigns across hundreds of different regions, product categories, or client accounts is incredibly complex. With API access, developers can build tools that automate the tedious parts of campaign management. For example, an agency can write a script to automatically update promotional assets across thousands of ad groups simultaneously when a seasonal sale begins, or dynamically adjust budgets based on external triggers like weather, stock levels, or real-time business performance metrics. 3. Real-Time Reporting and Optimization Because the API allows developers to retrieve Demand Gen resources programmatically, it becomes much easier to feed granular campaign performance data directly into custom business intelligence (BI) tools and data warehouses. This facilitates faster decision-making, as marketing analysts can run advanced custom attribution models and programmatic optimizations using fresher, more unified data sets. Crucial Steps for Developers: Preparing for the June 10 Rollout While this update brings massive opportunities, it also introduces immediate responsibilities for developers maintaining existing DV360 API integrations. Because Demand Gen resources will begin appearing in standard list responses, unprepared systems could experience errors or data parsing failures. Google has explicitly warned that existing list queries may start returning these new, unmapped resource types as soon as the rollout begins on June 10. To prevent service disruptions, development teams should prioritize the following action items: Schema Validation and Parsing Updates If your system parses API responses based on strict, pre-defined schemas of expected line item types or ad group formats, you must update your code to recognize and gracefully handle the new Demand Gen object types. Ensure that your JSON parsers do not throw errors or fail to load data when they encounter unfamiliar fields associated with Demand Gen structures. Reviewing Filter Parameters If your application only supports specific types of media buys (for example, standard programmatic display or video), you should verify that your API queries use explicit filters. Relying on default “get all” queries could result in Demand Gen data bleeding into reporting dashboards where it does not belong, potentially skewing performance metrics or breaking visual layouts. Testing in Sandbox Environments Utilize DV360’s developer sandbox environments to

In the rapidly evolving landscape of digital advertising, first-party data has transition from a competitive advantage to an absolute necessity. As third-party cookies phase out and global privacy regulations tighten, advertisers are constantly searching for ways to streamline how they collect, unify, and activate their own customer data. Google is addressing these operational hurdles by restructuring its data ingestion workflows. To help businesses unify their measurement and marketing efforts, Google has announced a major upgrade to its Data Manager API. This tool now supports direct offline conversion event uploads to various Google Marketing Platform (GMP) destinations, including Campaign Manager 360, Search Ads 360, and Display & Video 360. Additionally, the update introduces new IP-based ingestion capabilities designed to boost Google Ads Customer Match performance ahead of upcoming industry shifts in 2026. For modern enterprise advertisers, digital marketers, and ad tech developers, this shift marks a significant step toward a more unified, privacy-compliant, and efficient data ecosystem. Let’s dive deep into what these changes mean, how they function technically, and how your business can leverage them to improve attribution and audience targeting. The Evolution of Google’s Data Manager API Historically, managing data across Google’s sprawling advertising ecosystem was a highly fragmented process. Enterprise marketing teams and agency partners had to maintain multiple independent API integrations to route offline conversion data to different platforms. For instance, sending offline conversion signals to Google Ads, Campaign Manager 360, and Search Ads 360 simultaneously required separate codebases, varying data schemas, and redundant processing workflows. This fragmentation created several pain points for technical teams, including increased developer overhead, higher latency in conversion reporting, and a higher risk of data discrepancies between platforms. The expanded Data Manager API solves these issues by acting as a centralized, singular ingestion layer for first-party offline data. Instead of managing multiple endpoints, advertisers can now use the Data Manager API to pipe offline conversions, customer lists, and event data into Google’s infrastructure once, routing it seamlessly to multiple end destinations. This consolidation reduces complexity and ensures that your conversion signals are consistent across every stage of the marketing funnel. Key Features of the Expanded Data Manager API The latest updates to the API introduce several features designed to optimize developer workflows and improve data utility across marketing platforms. Multi-Destination Routing in a Single Request One of the most valuable aspects of the updated Data Manager API is its ability to route conversion events to multiple Google Marketing Platform destinations simultaneously. Through a single API call, an advertiser can send a localized offline purchase event to Campaign Manager 360 for attribution, Search Ads 360 for bidding optimization, and Display & Video 360 for programmatic audience suppression. This eliminates the need for redundant, parallel API requests, reducing server load and minimizing potential data integration errors. A Single, Standardized Schema Previously, formatting offline conversion data required adhering to different schemas depending on which Google product was receiving the data. The Data Manager API removes this friction by introducing a unified schema. Developers can build a single pipeline that packages consumer interaction data, encrypts sensitive identifiers, and distributes it across Google’s advertising suite without needing to reformat or map data fields multiple times. Support for Encrypted User Identifiers Data privacy is a foundational element of modern ad tech. To ensure compliant data transfers, the Data Manager API supports secure, hashed customer identifiers, such as SHA-256 hashed email addresses and phone numbers. This ensures that sensitive user information remains secure while still enabling Google’s platforms to match offline actions back to digital ad interactions accurately. Migrating from Campaign Manager 360 API With this expansion, Google is actively encouraging advertisers currently using the legacy Campaign Manager 360 API for offline conversion uploads to transition to the Data Manager API. The company emphasizes that the newer API framework is not only simpler to implement but also provides far greater flexibility for modern measurement, attribution, and audience activation use cases. While legacy APIs served their purpose in an era of direct, channel-specific tracking, they lack the multi-platform versatility required in today’s cross-channel marketing environments. Migrating to the Data Manager API ensures that your organization’s data pipeline is future-proofed against upcoming API deprecations, while immediately unlocking more sophisticated multi-destination targeting and attribution capabilities. Boosting Customer Match Performance with IP Ingestion Alongside the expanded event ingestion for Google Marketing Platform, Google has introduced a major update to its Google Ads Customer Match capabilities. The Data Manager API now supports IP address ingestion via a new structured field called CompositeData. Customer Match has long been a cornerstone of first-party audience targeting on Google Search, YouTube, Shopping, and Gmail. Traditionally, advertisers matched their offline customer databases with Google’s logged-in users using identifiers like email addresses, phone numbers, and physical mailing addresses. By allowing the ingestion of IP addresses alongside these traditional identifiers, Google is providing advertisers with an additional signal to boost match rates. The Role of Observation Timestamps To ensure accuracy and maintain compliance with privacy standards, the API requires that uploaded IP addresses be accompanied by corresponding observation timestamps. Because IP addresses are dynamic and can change frequently as users move between cellular networks, home Wi-Fi, and office environments, a timestamp allows Google’s matching system to verify that the IP address was active for that specific user at the precise moment of the recorded interaction. The Q3 2026 Milestone Google has indicated that incorporating IP addresses and observation timestamps will begin playing a crucial role in improving Customer Match rates starting in Q3 2026. This timeline gives advertisers ample opportunity to upgrade their CRM, CDP, and backend database systems to capture and store IP addresses with high-precision timestamps at the point of conversion or sign-up. By preparing for this integration now, brands can ensure their first-party audiences remain highly reachable and accurately targeted even as other traditional tracking methods continue to degrade. Why This Update Matters to Advertisers For brands running large-scale first-party data programs, this API expansion offers several strategic advantages that directly impact the bottom line. Improved Match

A Centralized Layer for Privacy-Safe Data Ingestion Google is taking another significant step toward unifying its advertising ecosystem. In a move to simplify conversion tracking and audience management, Google has expanded the capabilities of its Data Manager API. The API now supports offline conversion event ingestion directly into the Google Marketing Platform (GMP), establishing a unified framework for data activation across multiple platforms. For enterprise advertisers, maintaining separate data pipelines for different marketing tools has long been a source of technical debt and operational inefficiency. By positioning the Data Manager API as a centralized ingestion layer, Google aims to streamline how first-party data flows from customer databases into its primary advertising channels: Campaign Manager 360, Search Ads 360, and Display & Video 360. This update not only simplifies programmatic integration but also addresses the pressing need for robust, privacy-first measurement solutions in an era where traditional tracking mechanisms continue to degrade. The Evolution of Google Data Manager API Google Data Manager was initially designed to help advertisers connect their data warehouses and customer data platforms (CDPs)—such as BigQuery, Salesforce, and HubSpot—directly to Google Ads. It serves as a low-code or no-code interface for data syncing, alongside a robust API for custom development. With this latest expansion, the Data Manager API evolves from a Google Ads-specific tool into a cross-platform data pipeline. Advertisers can now use a single, unified schema to transmit offline conversion data to several GMP destinations at once. Instead of writing distinct integration code for each platform’s legacy API, engineering teams can configure a single API call to route conversion events to Campaign Manager 360, Search Ads 360, and Display & Video 360 simultaneously. This consolidation reduces API maintenance costs, simplifies data governance, and ensures that attribution data remains consistent across all planning, buying, and measurement tools within the Google stack. Key Features of the Expanded Data Manager API The updated API introduces several features designed to optimize data workflows and improve the accuracy of offline conversion matching: 1. Single-Schema Multi-Destination Routing Historically, sending a single offline purchase event to both Campaign Manager 360 and Search Ads 360 required formatting the data differently for each product’s specific API. The updated Data Manager API standardizes the data schema. Advertisers can format the payload once and designate multiple destinations within a single API request, ensuring that all platforms evaluate the exact same dataset for optimization and reporting. 2. Privacy-Safe User Identifiers Modern data pipelines must prioritize user privacy and regulatory compliance. The Data Manager API supports secure, encrypted user identifiers, including hashed email addresses and hashed phone numbers. By using SHA-256 hashing protocols, advertisers can safely transmit first-party customer signals without exposing personally identifiable information (PII) to the open web. 3. Seamless Tool Consolidation By bringing Campaign Manager 360, Search Ads 360, and Display & Video 360 under the same ingestion umbrella, Google is eliminating redundant point-to-point connections. Marketing operations teams can monitor and manage all active data connections from a single dashboard, making it easier to audit data flows and maintain compliance with regional privacy regulations like GDPR and CCPA. The Push for Migration: Moving Beyond Legacy APIs With this expansion, Google is actively encouraging advertisers currently using the legacy Campaign Manager 360 API for offline conversion uploads to migrate to the Data Manager API. The legacy systems, while functional, were built for an older era of the web and lack the flexibility required for modern real-time data activation. Google emphasizes that the Data Manager API offers a far more resilient implementation framework. As advertising networks transition away from third-party cookies, API-based conversion ingestion acts as the primary bridge for measuring the offline impact of online advertising. Transitioning to the newer API ensures that advertisers can take advantage of future measurement updates and attribution models that Google integrates directly into the Data Manager backend. For technical teams, migrating to the Data Manager API offers an opportunity to refactor legacy code, reduce reliance on outdated SDKs, and build a more robust integration with enterprise data lakes like Snowflake, AWS Redshift, or Google Cloud’s BigQuery. Enhancing Customer Match with IP Ingestion Beyond conversion measurement, the update introduces a major improvement to Google Ads Customer Match. Google has introduced support for IP address ingestion via a new CompositeData field. Customer Match allows brands to use their first-party data to re-engage customers across Search, Shopping, Gmail, YouTube, and the Display Network. Traditionally, these match rates relied heavily on static identifiers like email addresses, phone numbers, and physical mailing addresses. While highly accurate, these identifiers are not always available for every user interaction. The introduction of the CompositeData field allows advertisers to upload IP addresses alongside traditional contact information. To support this new signal, Google has outlined a clear timeline for implementation: The Mechanism: Advertisers can send IP addresses combined with corresponding observation timestamps. The Timeline: Beginning in Q3 2026, Google will fully leverage these IP addresses and timestamps to improve Customer Match rates. The Impact: This additional signal layer is designed to help match offline or app-based interactions to Google accounts more effectively, expanding the overall reach of custom audiences while maintaining user privacy through aggregated matching models. This long runway gives development teams ample time to update their CRM pipelines and customer consent management frameworks to ensure that IP data is captured, stored, and transmitted in compliance with regional laws before the performance benefits go live in 2026. Why This Matters for Enterprise Advertisers The unification of data ingestion pipelines has several strategic implications for brands managing large-scale, first-party data programs: Consistent Cross-Channel Attribution When different ad platforms receive conversion data via separate, mismatched pipelines, discrepancy issues inevitably arise. A conversion credited in Search Ads 360 might not register in Campaign Manager 360, leading to fragmented reports and misallocated budgets. Standardizing on the Data Manager API ensures that every system in the marketing stack views the exact same conversion touchpoints, leading to cleaner attribution models and better strategic decision-making. Improved Bid Optimization Modern machine learning-based bidding algorithms rely on high-quality, real-time

Introduction The digital advertising ecosystem is undergoing one of its most significant structural shifts. With the ongoing phase-out of traditional tracking mechanisms, privacy regulations tightening globally, and platforms restricting cross-site tracking, advertisers are increasingly reliant on first-party data. To successfully navigate this transition, brands require robust, streamlined infrastructure to connect their offline data directly to their marketing suites. Recognizing this need, Google has announced a major expansion of its Data Manager API. The update introduces Google Marketing Platform (GMP) offline conversion event ingestion, consolidating measurement and audience activation workflows across Google’s core advertising systems. By allowing advertisers to route offline conversions and first-party data to multiple destinations simultaneously, Google is positioning the Data Manager API as the definitive centralized pipeline for first-party data management. This expansion simplifies complex technical workflows and introduces new capabilities for Google Ads Customer Match. Through advanced IP-based matching and unified schemas, modern marketers can look forward to more accurate attribution, reduced developer overhead, and improved audience match rates. Let us dive deep into what these updates entail, how they function, and what they mean for the future of your digital marketing strategies. The Evolution of Google Data Manager To understand the significance of this update, it is helpful to look at the role Google Data Manager plays within the broader Google Ads and Google Marketing Platform ecosystem. Historically, managing first-party data across multiple Google tools was a fragmented and resource-intensive process. If an advertiser wanted to send offline conversion data to Google Ads, Search Ads 360, and Campaign Manager 360, they often had to build and maintain separate API integrations, manage distinct data schemas, and coordinate multiple server-side pipelines. Google Data Manager was introduced to solve this exact pain point. Acting as a simplified, user-friendly data preparation and ingestion layer, it bridges the gap between external data warehouses—such as BigQuery, Snowflake, and Salesforce—and Google’s advertising platforms. The latest updates to the Data Manager API represent a major step forward, transforming this tool from a basic connector into a powerful, automated data routing engine. Consolidated Event Ingestion Across Google Marketing Platform The headline feature of this update is the Data Manager API’s new support for offline conversion event uploads across Google Marketing Platform destinations. Specifically, advertisers can now seamlessly transmit data to: Campaign Manager 360 (CM360): The leading ad server and measurement system for tracking campaign performance across sites and networks. Search Ads 360 (SA360): The enterprise search management platform used to build, manage, and track campaigns across multiple search engines. Display & Video 360 (DV360): Google’s demand-side platform (DSP) designed for programmatic media buying across display, video, TV, audio, and other channels. Rather than managing separate connections for each of these platforms, engineers and database administrators can now write to a single, unified API. This consolidated framework reduces the margin for error, minimizes api call volume, and drastically cuts down on custom development hours. A Single Schema for Multi-Destination Routing Previously, sending a single offline conversion—such as an in-store purchase, a phone call consultation, or a finalized insurance quote—to multiple Google tools required formatting that data differently for each system. Each platform had its own set of required fields, naming conventions, and payload expectations. With the expanded Data Manager API, Google introduces a standardized schema. Advertisers format the offline event once, package it with the necessary user identifiers and transaction details, and send it to the API. Within a single API request, the system can route that conversion event to multiple destinations. This multi-destination routing ensures that your analytics, programmatic bidding, search campaigns, and ad serving platforms are all looking at the exact same source of truth in near real-time. Prioritizing Data Privacy with Encrypted Identifiers As privacy standards continue to elevate, protecting user identity during data transfers is non-negotiable. The Data Manager API supports secure, industry-standard hashing protocols. Advertisers can upload encrypted user identifiers, including hashed email addresses and phone numbers. This ensures that sensitive personally identifiable information (PII) is securely protected before it ever leaves the advertiser’s infrastructure, maintaining compliance with global privacy regulations while still enabling precise closed-loop attribution. The Push to Migrate: Moving Away from Legacy Campaign Manager 360 APIs For organizations currently relying on legacy tools like the Campaign Manager 360 API for offline conversion uploads, Google’s latest announcement serves as a clear call to action. The company is actively encouraging advertisers and technology partners to migrate their conversion pipelines over to the Data Manager API. Why make the switch? Legacy APIs were often built around older data handling methodologies. They lack the flexibility, speed, and cross-platform synergy of modern cloud integrations. By transitioning to the Data Manager API, engineering teams can benefit from: Lower Maintenance Overhead: Maintaining a single API connection is substantially easier and more cost-effective than managing a web of legacy point-to-point connections. Greater Scalability: The Data Manager API is architected to handle the massive data volumes generated by enterprise-level first-party databases without performance degradation. Future-Proofing: Google is concentrating its engineering resources on the Data Manager suite. New measurement, modeling, and privacy features will be introduced natively here, rather than being retrofitted into legacy pipelines. To help companies transition, Google offers detailed documentation outlining mapping practices, schema translations, and deployment guides, facilitating a smooth migration with minimal disruption to active advertising campaigns. Enhancing Customer Match with IP-Based Ingestion Beyond tracking conversions, first-party data is vital for finding and retaining high-value customers. Google Ads Customer Match is a foundational tool for this, allowing advertisers to upload their customer lists to target specific audiences, build lookalikes, or exclude existing buyers from acquisition campaigns. However, the efficacy of Customer Match relies entirely on the match rate—the percentage of uploaded customer records that Google can successfully pair with an active Google account. To boost these rates, Google is introducing IP address ingestion support for Customer Match via a new database field called CompositeData. Understanding the CompositeData Field The introduction of the CompositeData field allows advertisers to combine traditional first-party identifiers with newly supported network signals. Now, when uploading list updates

Introduction The landscape of programmatic advertising is undergoing a rapid evolution, driven by the need for deeper integration, smarter automation, and cross-channel efficiency. In a major move to streamline workflows for enterprise advertisers and ad tech developers, Google has announced that the Display & Video 360 (DV360) API will officially begin supporting Demand Gen campaigns. Scheduled to kick off on June 10, with a full rollout completed by June 24, this update marks a significant shift in how modern marketing teams build, manage, and scale their creative-first campaigns. By bringing Demand Gen resources directly into the DV360 API, Google is closing the gap between manual platform management and programmatic execution, allowing advertisers to orchestrate complex campaigns with unprecedented speed and precision. Understanding Demand Gen and Its Place in Modern Marketing To fully appreciate the impact of this API update, it is important to understand what Demand Gen campaigns are and why they have become central to Google’s advertising suite. Introduced as the modern evolution of Discovery campaigns, Demand Gen is designed specifically for today’s visually driven, social-first consumer behaviors. Demand Gen campaigns leverage Google’s most engaging, highly visual placements across multiple platforms, including: YouTube Shorts: Capitalizing on the explosive growth of short-form vertical video. YouTube Feed and In-Stream: Reaching users while they actively consume video content. Google Discover: Engaging users on their personalized content feeds. Gmail: Capturing attention in a high-intent, personal environment. Unlike traditional search campaigns that capture existing demand, Demand Gen focuses on creating new demand. It uses a mix of high-impact image and video assets, combined with Google’s proprietary machine learning, to find and convert potential customers who may not yet be actively searching for a brand or product. Because of this visual and creative focus, managing these campaigns historically required a high degree of hands-on curation inside the user interface—until now. The Technical Details: What Is Changing in the DV360 API? Starting June 10, developers and partners utilizing the Display & Video 360 API will gain programmatic access to Demand Gen resources. This integration allows for a full suite of Create, Read, Update, and Delete (CRUD) operations, transforming how teams interact with these campaign types. Programmatic Resource Management Through the API, users will now be able to manage several key components of their Demand Gen infrastructure programmatically: Demand Gen Line Items: Set budgets, targeting parameters, and flight dates at the line-item level without manual platform navigation. Ad Groups: Define audience segmentation, bidding strategies, and organization across multiple ad groups dynamically. Ad Formats: Upload, update, and manage the highly visual creative assets (both images and video formats) required for Demand Gen distribution. Unified Query Responses Once the rollout is complete, Demand Gen resources will no longer exist in a silo. When developers run standard list queries for line items or ad groups within the DV360 API, the responses will seamlessly include Demand Gen objects alongside existing display, video, and connected TV (CTV) campaign objects. This unification simplifies database architecture and reporting schemas for ad tech providers. The Timeline: Key Rollout Dates to Remember Google is deploying this update using a phased rollout strategy to ensure platform stability and give development teams ample time to adapt their systems. Marketers and developers should mark these crucial dates on their calendars: June 10: The initial rollout begins. A subset of DV360 API users and partners will start seeing Demand Gen resources supported in their environments. API queries may begin returning Demand Gen data. June 24: Full availability. By this date, the rollout will be complete across all accounts globally. Every developer and advertiser utilizing the DV360 API will have full access to Demand Gen functionalities. Critical Preparation Steps for Developers and Ad Tech Teams While this update represents a major step forward, it also introduces immediate technical changes that could impact existing workflows if not addressed proactively. For developers and technical marketers relying on custom-built dashboards, reporting pipelines, or automated bidding tools, preparation is key. 1. Update Integration Schemas Because standard list queries for line items and ad groups will soon begin returning Demand Gen objects, existing API integrations must be prepared to handle these new resource types. If your proprietary software or database relies on strict data validation rules that only recognize traditional display or video formats, the introduction of unexpected Demand Gen objects could trigger system errors or data pipeline failures. 2. Audit Filtering Logic Ensure that your reporting and campaign management dashboards can intelligently filter, categorize, and display these new line items. If your platform separates campaign types visually for end-users, your code must be updated to correctly identify and group Demand Gen resources as they pull through the API. 3. Test Error-Handling Procedures Before the June 10 rollout begins, run sandbox tests to verify how your applications react when receiving unknown or newly structured payload fields. Ensuring robust fallback mechanisms and error-handling routines will prevent downtime during the transition period. Strategic Benefits for Enterprise Advertisers and Agencies The addition of Demand Gen support to the DV360 API is more than just a technical upgrade; it is a strategic shift that unlocks significant business value for large-scale advertisers and agency partners. 1. Unlocking True Automation at Scale For brands managing hundreds of localized or audience-specific campaigns, manual setup is a bottleneck. By leveraging the API, agencies can build custom internal tools that automatically generate Demand Gen campaigns, set up ad groups, and assign budget allocations based on real-time performance data or external business triggers (such as regional weather, inventory levels, or local sales events). 2. Streamlined Creative Asset Testing Because Demand Gen relies heavily on creative variations to drive engagement, finding the winning combination of video, image, and copy is critical. Managing these creative assets programmatically via the API allows teams to execute dynamic creative testing on a massive scale. Assets can be systematically uploaded, rotated, and optimized based on performance metrics retrieved directly through automated loops. 3. Cross-Channel Budget Orchestration When Demand Gen campaigns are managed alongside display, native, audio, and YouTube video campaigns within