Category: Advertising

Google Ad Tech Antitrust Remedies: What to Do Next
If your publishing revenue stack depends on Google Ad Manager or AdX, the words “no breakup” may sound like permission to stand down. They aren’t. Google keeps its advertising exchange, but the finding that it violated antitrust law remains in place.

Your practical task is to separate the ownership decision from its operational consequences. That means documenting your dependence, establishing performance baselines, watching how the behavioral remedies are implemented, and avoiding expensive migrations based on assumptions the court did not make.

The ruling separates liability from remedy

U.S. District Judge Leonie Brinkema declined to force Google to sell AdX, the exchange through which publishers offer digital advertising inventory in real-time auctions. The court instead chose behavioral remedies and adopted most of the proposals submitted by the parties.

That outcome answers one narrow but consequential question: Google can continue to own AdX. It does not reverse the April 2025 finding that Google illegally monopolized publisher ad-server and ad-exchange markets. The liability decision also found that Google’s conduct harmed publishers, consumers, and the competitive process by locking publishers into its advertising technology.

The distinction matters because a liability ruling and a remedy order do different jobs. Liability identifies unlawful conduct. A remedy determines what must change. A structural remedy, such as divestiture, changes ownership. A behavioral remedy leaves the business intact while restricting, requiring, or supervising specified conduct.

It is therefore inaccurate to reduce the result to either “Google won” or “Google was broken up.” The Department of Justice and a coalition of states did not obtain the AdX sale they requested, but Google did not erase the underlying monopoly judgment. If you brief executives, clients, or readers, put both halves in the same sentence.

Do not confuse AdX with Google Ads, either. AdX is part of the publisher-side infrastructure at issue here. The court did not order a breakup of Google’s advertiser-facing campaign platform, and the ruling does not itself invalidate campaigns running through Google Ads.

Behavioral remedies make measurement more important

A divestiture would have created a visible transition: a new owner, technical separation, contract changes, and migration work. Google argued that such a sale would be technically difficult, lengthy, and harmful to customers. That was Google’s position in the litigation, not a neutral measurement of what a sale would have produced.

Behavioral remedies create a quieter challenge. Ownership can look unchanged even as auction rules, contractual restrictions, access conditions, integrations, reporting, or enforcement obligations change underneath it. The label “behavioral remedies” does not tell you which of those mechanisms will change or when.

Do not infer fee caps, new interoperability rights, data portability, auction changes, or access guarantees merely because they sound like plausible antitrust remedies. The operative order, its timetable, and its enforcement provisions control Google’s obligations. Treat a claimed product consequence as unverified until you can connect it to that language or to a concrete Google product or contract notice.

This is why your baseline matters. If performance moves after implementation, you need to know whether the cause was a remedy-related product change, seasonality, demand quality, consent rates, floor settings, latency, or an unrelated auction adjustment. Without a dated baseline, those explanations collapse into guesswork.

Company-level financial figures will not answer the dependency question for you. A Wedbush estimate based on court documents put Ad Manager at about 4.1% of Google’s revenue and 1.5% of its operating profit in 2020; more recent figures were redacted. Those older percentages describe Google’s business mix, not the importance of the stack to a publisher that routes most of its sell-side operations through it.

A practical plan for publishers, advertisers, and agencies

You do not need to predict the final commercial effect before preparing for it. Build the evidence that will let you distinguish a meaningful change from normal ad-market noise.

For publishers and revenue operations teams
1. Map the complete monetization path. Trace inventory from the page or app through the publisher ad server, exchange, demand source, auction decision, creative delivery, and reporting system. Mark every point where Google technology, identifiers, contracts, or data are required. A vendor list alone will miss dependencies embedded in trafficking and reporting workflows.
2. Capture a dated baseline. Preserve gross and net revenue, eligible impressions, bid participation, win rate, fill rate, effective revenue per thousand impressions, viewability, latency, discrepancies, and observable fees by format, device, geography, and demand path. Keep the relevant floor, timeout, consent, and inventory-quality settings with the data so future comparisons remain interpretable.
3. Design fair alternative-path tests. Do not send only remnant, high-latency, or otherwise weak inventory to a competing exchange and call the result a comparison. Hold geography, device, format, consent status, viewability, floor strategy, and traffic quality as constant as your stack permits. Compare net publisher revenue after measurable costs, not a single headline CPM.
4. Monitor the implementation layer. Assign an owner to review court orders, contractual notices, product documentation, reporting-field changes, auction behavior, and access conditions. Record what changed, the effective date, the affected inventory, and the evidence linking it to the remedy. This log will be more useful than a folder of undated screenshots.
5. Set decision triggers before results arrive. Define which outcomes would justify a larger test, contract review, engineering work, or migration analysis. Use your own revenue concentration, operational capacity, and risk tolerance. A change that is immaterial across the market can still be material to a publisher with concentrated dependence.
Do not treat the antitrust judgment as an automatic right to terminate or disregard an existing agreement. If a contract decision depends on the legal effect of the ruling, have commercial or antitrust counsel examine the actual agreement and operative order before you act. The downside of guessing can include breach claims, lost demand access, and an unnecessary technical migration.

For advertisers and agencies

Your exposure is less direct, but publisher-side changes can alter supply paths, reporting, auction participation, inventory availability, and measurable costs. The useful response is supply-path scrutiny, not an automatic campaign pause.
- Separate performance by exchange, inventory source, domain or app, format, and other supply-path dimensions available in your reporting.
- Preserve pre-implementation baselines for spend, impressions, effective CPM, reach, viewability, conversion performance, invalid-traffic signals, and platform-to-platform discrepancies.
- Ask your agency or technology partners which reports expose exchange-level changes and which parts of the buying path remain aggregated or opaque.
- Require a dated change log when a partner attributes performance movement to the antitrust remedies. The explanation should identify the affected mechanism, not merely mention the case.
- Avoid converting the liability finding into a claim that every impression, auction, fee, or campaign outcome involving Google was unlawful. The ruling concerns specified publisher ad-tech markets and conduct.
Publish the decision accurately for search and AI systems

If you create SEO, AEO, or GEO content about the case, accuracy begins with entity separation. Google, Google Ads, Google Ad Manager, and AdX are related names, but they are not interchangeable entities or products. Blurring them makes it easier for a search engine or language model to extract a false answer such as “Google Ads was ordered sold.”

Put the decisive answer near the beginning of the page: Google retains AdX; the antitrust liability finding remains; the court selected behavioral rather than structural relief. Then explain the relevant markets, the difference between liability and remedy, and the practical audience affected. Do not bury the no-divestiture result below a general history of Google’s advertising business.

Keep the April 2025 liability finding distinct from the later remedy decision. Dates should be attached to the event they describe. A vague phrase such as “the Google antitrust ruling” can cause a human reader or retrieval system to merge separate legal stages into one event.

Your structured data should match the visible page. Use an appropriate Article, BlogPosting, or NewsArticle type; provide an accurate headline, author, publisher, datePublished, and dateModified; and identify the case, AdX, Google, and the antitrust-remedy subject in the visible copy. Do not use structured data to add claims or dates that a reader cannot verify on the page.

Update the page when the operative requirements, implementation schedule, product behavior, or legal status materially changes. Change dateModified only when you make a substantive update, and add a visible note describing what changed. That gives readers and retrieval systems a reason to trust the newer version rather than silently mixing it with an earlier one.

Key takeaways
- Google was not ordered to sell AdX, so the publisher advertising exchange remains under Google ownership.
- The April 2025 finding that Google illegally monopolized publisher ad-server and ad-exchange markets remains intact.
- Behavioral remedies are not the same as no remedy. Their practical effect depends on the operative requirements, implementation, and enforcement.
- Publishers should map dependencies and preserve segmented performance baselines before interpreting later changes.
- Advertisers should monitor supply paths and reporting rather than treating the ruling as a breakup of Google Ads.
- SEO and AI-facing coverage should distinguish Google Ads, Google Ad Manager, and AdX while separating liability from remedy.
Your next move is neither a rushed migration nor passive waiting. Schedule the dependency audit, assign an owner for remedy-related changes, and start the baseline now. When a concrete product, contract, or auction change arrives, you will be able to evaluate it against evidence instead of a headline.

References
- Search Engine Land — Google avoids AdX breakup in ad tech antitrust case
September 2, 2026

Google AdSense Begin-to-Render: A Publisher Action Plan

If AdSense revenue helps you judge whether your content strategy is working, February 2027 could produce a misleading signal. Your reported display impressions may fall even when traffic and reader behavior have not materially changed.

The right response is to establish a clean baseline, mark the measurement break, and compare impressions with traffic, clicks, and earnings before changing your site. That lets you separate a new counting rule from a real monetization or SEO problem.

Key takeaways

Beginning February 17, 2027, an AdSense display impression will be counted after the ad has successfully loaded and started to render, not when it merely starts downloading.
Downloads that never reach rendering will disappear from the impression total. An early page exit is one example of how that gap can occur.
A lower impression count does not, by itself, prove that traffic, ad demand, viewability, engagement, or revenue declined.
Click-through rate and other per-impression ratios may change mechanically because their denominator has changed.
Preserve pre-change data now, separate display inventory from inventory already using Begin-to-Render, and evaluate post-change results by page type, device, and placement where your reporting supports those dimensions.

What Begin-to-Render changes in AdSense

Three generic browser panels show an empty ad space, the first visible pixels appearing with an indicator light, and the completed ad rendering.

On February 17, 2027, Google will change the counting trigger for AdSense display impressions. Under the current method, the impression is recorded when an ad starts downloading to the user’s device. Under Begin-to-Render, or BTR, the ad must successfully load and start rendering on that device.

Measurement point	Current display method	Begin-to-Render method
Counting trigger	The ad starts downloading	The ad successfully loads and starts rendering
User leaves after download starts but before rendering	The impression can be counted	The impression is not counted
Inventory affected by the transition	AdSense display ads	Display joins the unified BTR approach
Other inventory	Native, app, and video inventory already uses or complies with Begin-to-Render counting

The important difference is the interval between download and render. If an ad crosses both points, it qualifies under either method. If it begins downloading but never reaches rendering, it can contribute to the old total but not the new one.

Begin-to-Render should not be treated as another name for viewability, attention, or engagement. It confirms that rendering began after a successful load. It does not tell you how much of the ad the person saw, how long it remained available, or whether the person interacted with it. Avoid relabeling the new count as a viewable impression in internal reports unless the metric you are using separately establishes viewability.

The transition also is not a directive to move every placement higher on the page. It is a measurement change. First identify where download-to-render failures actually occur; otherwise, a layout overhaul may damage the reading experience without addressing the cause.

Why the dashboard can look better and worse at once

Google has warned that publishers may see a change in total impressions because downloads that never render will no longer count. No universal percentage change has been specified. Your result will depend on how often your display ads currently enter that unfinished state.

That creates a break in the time series. A chart that places pre-February 17 impressions beside post-February 17 impressions without an annotation makes the two periods look directly comparable when they are not. Treat the date as a measurement boundary in dashboards, forecasts, stakeholder reports, and automated alerts.

Derived rates require even more care. Click-through rate divides clicks by impressions. If clicks remain unchanged while the newly defined impression total falls, the reported rate rises automatically. That increase does not prove that people became more interested in the ads. Part of it may be denominator removal.

The same arithmetic applies to any earnings-per-impression calculation. If earnings remain stable while counted impressions decline, earnings per thousand impressions can rise without any improvement in total revenue. If earnings and impressions fall together, the rate may remain similar even though the site earns less. A rate by itself cannot tell you which situation occurred.

This is why neither conclusion is safe on impression data alone. Fewer impressions do not automatically mean your SEO traffic weakened, and a higher per-impression rate does not automatically mean monetization improved. Keep the numerator and denominator visible: traffic, display impressions, clicks, and earnings should be reviewed as separate values before you interpret their ratios.

Build a baseline that survives the February change

The useful work happens before the switch. You need enough context to answer one practical question afterward: did the business change, or did only the definition change?

Map the inventory in scope. Identify the reports and dashboards that contain AdSense display impressions. Keep native, app, and video inventory distinct where possible because those formats already use or comply with BTR counting.
Save a stable pre-change baseline. Export the reports you routinely use before February 17, including their exact date range and filters. Preserve raw impressions, clicks, and earnings rather than saving only calculated rates.
Add independent traffic context. Retain pageviews, landing-page visits, sessions, or the equivalent traffic measures your analytics setup uses. Align site scope and reporting dates so that an AdSense property is not accidentally compared with traffic from a different set of pages.
Record operational changes. Note ad-placement edits, template releases, consent-flow changes, performance work, major campaigns, and content migrations near the transition. Any of these can complicate the comparison even though they are separate from the counting rule.
Choose meaningful cohorts in advance. Where your existing reports support them, prepare comparisons by device, page template, content section, and ad placement. A site-wide total can hide a problem concentrated in one implementation.
Annotate February 17, 2027 everywhere. Put the date in reporting calendars, dashboard notes, forecast assumptions, and recurring stakeholder reports. Future analysts should not have to rediscover why the series changed.

Four paired calculations are especially helpful: display impressions per pageview, clicks per display impression, earnings per display impression, and earnings per pageview. Use the same definitions and scope on both sides of the change.

The per-impression measures show what happened inside the newly counted population. The per-pageview measures show whether the economic result changed for the traffic you actually received. If earnings per impression rises while earnings per pageview stays flat, you may be looking mainly at a denominator effect. If earnings per pageview declines as well, there is a business outcome to investigate rather than merely relabel.

Do not force a comparison between periods with visibly different traffic composition. A major campaign, seasonal event, ranking change, or shift in device mix can move ad behavior independently of BTR. Use comparable traffic cohorts and keep those differences explicit.

Turn the post-change gap into a defensible decision

An analyst compares four abstract measurement streams across a divider, with only the impression tiles dropping while traffic, clicks, and earnings remain steady.

Read the pattern before changing the site

Start with the shape of the change, not a theory about its cause. The following patterns point to different next steps:

Traffic is stable, display impressions fall at the transition, and clicks and earnings are broadly stable: a counting-definition effect is plausible. Document the break before treating it as an optimization problem.
Traffic and display impressions decline together: investigate acquisition and audience changes as well as ad measurement. BTR alone cannot establish why fewer people reached the site.
Display impressions fall mainly on one template, device group, or placement: inspect that implementation. A concentrated gap deserves more attention than a uniform site-wide adjustment.
Click-through rate rises while clicks are flat: treat the increase as denominator-sensitive. Do not claim stronger engagement without additional evidence.
Earnings per pageview declines: the economic result changed for the traffic received. Review earnings, traffic mix, placement behavior, and render failures together rather than assuming the counting rule explains the entire loss.

For an SEO-led publisher, compare organic landing traffic with display impressions separately. Stable organic visits alongside a lower ad-impression total are not evidence of a ranking loss. Falling organic visits and falling impressions, by contrast, require an SEO investigation that is independent of the AdSense definition change.

Inspect the download-to-render interval

Once you find a cohort with an unusual gap, test representative pages on the affected device type. Observe whether the ad begins loading, whether the creative starts rendering, and whether navigation or another page event occurs first. Browser developer tools, the visible page state, and the diagnostics already available in your ad implementation can help you distinguish an initiated request from an actual render.

Treat possible causes as hypotheses. A user may leave before rendering, which is the explicit example behind the change. A slow page, late ad initialization, template-specific integration, consent sequence, or navigation behavior may also deserve inspection when the evidence points there. Do not declare one of these the cause merely because it sounds plausible.

Change one relevant variable at a time and review the same cohort again. If several layout, performance, consent, and placement changes launch together, you will not know which one affected rendering or revenue.

Optimize the outcome, not the retired counter

The old metric gave credit at an earlier technical milestone. Trying to recover every disappearing impression can push you toward the wrong goal. A download that repeatedly begins but never produces a rendered ad is not a number you should preserve merely for continuity.

Prioritize genuine implementation failures, avoidable delays, and placements that fail to render despite meaningful reader activity. Avoid disruptive layout changes whose only justification is restoring the old impression total. The decision should improve rendered ad delivery, earnings per visit, or the reader experience under the new definition.

Put February 17, 2027 on your reporting calendar now and preserve the unaggregated values behind your ratios. When the switch arrives, make the first review a measurement audit. Redesign a placement only after the traffic, cohort, and earnings evidence shows that you have a delivery problem rather than a cleaner count.

References

Search Engine Land — Google AdSense to change how it counts impressions: Begin-to-Render

September 1, 2026

How to Prepare for Google’s Demand Gen Campaign Expansion

If your Demand Gen campaigns already attract attention but lose people between the ad and the next meaningful step, Google’s expansion matters. The new capabilities change how a viewer can respond, how a travel offer can be matched to demand, and how quickly your team can produce the video formats a campaign needs.

The useful question is not whether to activate everything. It is which constraint currently limits growth: a long lead path, generic travel merchandising, or too little usable video. Identify that constraint first, then test the corresponding capability against a customer outcome.

Treat the expansion as a change to the conversion path

Demand Gen begins in a discovery context, but its expansion brings several later-stage functions closer to the ad. That distinction matters because each function solves a different problem.

Google is testing direct messaging from Demand Gen ads on YouTube. A person who discovers your brand through a video may be able to begin a conversation through a messaging app instead of navigating through a conventional website journey first. This can shorten the path for a prospect who already has a specific question or strong intent.

Travel advertisers are getting a different kind of expansion. Demand Gen can surface local activities, events and real-time offers while personalizing hotel selections for audiences Google considers relevant. Here, the opportunity is not a new contact method. It is a closer match between what a traveler may want and what the advertiser can offer.

Creative teams have a third option. Multimodal Video Creation in Asset Studio is generally available, with a workflow that can move from storyboarding to horizontal and vertical video production. This addresses creative supply, not conversion-path friction by itself.

Capability	Availability described	Problem it can address	Readiness requirement
Messaging from YouTube ads	Testing	Too much friction between high-intent discovery and direct contact	A team and process that can receive, qualify and advance conversations
Travel activities, events, offers and personalized hotels	Expanding	Generic merchandising that does not reflect what a traveler may want to do or book	Accurate, current and fulfillable offer information
Multimodal Video Creation	Generally available in Asset Studio	Insufficient horizontal and vertical video assets	A creative brief, brand controls and human review

These are not interchangeable optimizations. Adding video will not fix an unanswered message. Messaging will not make a stale travel offer relevant. Personalization will not rescue a weak proposition. Match the feature to the blockage you can actually observe.

Choose the bottleneck before you choose the feature

Strategist choosing among three visual bottlenecks representing a long response path, generic travel offers, and too few adaptable video assets.

Use messaging only when a conversation can move the sale forward

A shorter route helps only if the conversation has somewhere to go. Before entering the messaging test, map the entire handoff from the ad promise to the business outcome:

State what the prospect is being invited to discuss. A vague invitation may produce activity without useful intent.
Define the information that makes a conversation qualified, such as the need, intended purchase, service fit or booking question.
Assign responsibility for receiving and advancing the conversation. An opened thread that sits unanswered is not a customer-acquisition improvement.
Specify the outcome that matters after the conversation begins: a completed purchase, accepted lead, confirmed appointment or another business result already used by your organization.
Preserve a route for people who prefer the website. The messaging path should remove friction for the right prospect, not force every prospect into the same behavior.

Messaging is a sensible test when interested prospects regularly need clarification before acting and the existing site journey makes that clarification difficult. If the real problem is weak demand, an unclear offer or slow internal follow-up, changing the contact channel will expose that problem rather than solve it.

Make travel personalization earn its relevance

Travel personalization increases the importance of offer quality. A locally relevant activity or timely event can make discovery more useful, but only if the advertised experience is current, available and consistent with what the traveler reaches next.

Audit the material that could appear before expanding:

Confirm that each promoted activity, event, offer or property can still be booked or purchased.
Check that the location and audience context fit the offer. Geographic proximity is not the same as traveler relevance.
Make the destination page continue the same promise, price context and experience shown in the ad.
Remove or update offers promptly when availability changes. Real-time promotion creates little value if the underlying information is stale.
Measure activity discovery and hotel selection as different decisions. They may sit within the same campaign type, but they do not necessarily represent the same customer intent.

Personalization should narrow the gap between the traveler’s situation and the offer. If your team cannot keep the offer layer accurate, broader personalization may create more mismatches at scale.

Use AI video creation to build a testable asset system

The practical benefit of Multimodal Video Creation is not simply that it can generate video. It can help a team carry one concept from storyboard into horizontal and vertical executions within a single workflow. That can reduce the production friction involved in supplying multiple formats.

Do not turn that production speed into uncontrolled variation. For the first asset set, keep the offer and desired action consistent. Change one major creative dimension at a time, such as the opening frame, narrative emphasis or orientation. You will have a better chance of learning why one execution performs differently.

Every generated asset still needs human review. Check factual claims, brand presentation, cropping, text legibility, the destination and the relationship between the creative promise and the next step. General availability means the workflow is broadly accessible; it does not make every output ready to spend against.

Measure customer quality instead of celebrating new activity

Google attributes the hundreds of Demand Gen improvements made during the second half of 2025 to an average 30% increase in conversions or conversion value. Treat that as a platform-reported aggregate, not a forecast for your account or for any one new feature. Conversion count and conversion value are also different outcomes; an increase in one does not establish an increase in the other.

Write a measurement contract before launch so that a new interaction cannot quietly redefine success:

Choose the business outcome. Use the result that matters to the campaign, such as a purchase, booked stay or qualified lead, rather than a generic engagement signal.
Name the feature-level behavior. This could be a conversation started, an offer explored or a video execution viewed, but treat it as an intermediate signal unless it is itself the business outcome.
Define quality. For messaging, decide what makes a conversation qualified. For travel, distinguish a fulfilled booking from interest in an unavailable offer. For video, judge the asset against the same acquisition goal as the campaign.
Preserve a meaningful comparison. Keep the audience, offer and desired outcome as consistent as the campaign design allows while introducing the capability you want to evaluate.
Set the decision in advance. State what evidence would justify expansion, revision or a pause. Do not invent the rule after seeing the most flattering metric.

The pattern of the results should tell you where to look next:

If conversion volume rises but customer quality falls, inspect qualification and the action being optimized before increasing exposure.
If messaging creates more conversations but few advance, check the ad promise, opening response and sales handoff.
If video engagement improves without a customer outcome, the creative may be earning attention without establishing intent.
If travel interactions rise around activities but bookings do not, inspect availability, offer continuity and the booking path rather than assuming the audience is wrong.

This prevents a common measurement mistake: treating the new behavior made possible by a feature as proof that the feature produced valuable demand.

Run a controlled rollout instead of a broad switch-on

Marketing team observing baseline and limited-test campaign assets moving through parallel customer-outcome pathways.

A controlled rollout gives you a clear reason for making each change and a better chance of learning from it. Use this sequence:

Write the constraint in one sentence. For example: interested viewers need answers before converting, travel offers are too generic, or the campaign lacks enough video formats.
Apply a readiness gate. Messaging requires response ownership; travel personalization requires current offers; AI video requires a brief and an approval process.
Select the capability that directly addresses the constraint. Do not add unrelated features to the same initial test.
Prepare the downstream path before launch. Check the conversation handoff, booking destination or creative-to-landing-page continuity from beginning to end.
Record volume and quality separately. More interactions can increase workload without increasing valuable customers.
Expand only after the downstream outcome supports it. If the result is ambiguous, revise the handoff or creative variable before broadening the test.

This sequence is especially important for messaging because it remains a test, while Multimodal Video Creation is generally available. Feature status should affect how cautiously you operationalize a capability, but availability alone should never be the business case for using it.

Key takeaways

Demand Gen’s expansion addresses three different constraints: contact friction, travel-offer relevance and video-production capacity.
Messaging can shorten the route from a YouTube ad to a brand conversation, but it needs qualification, ownership and a defined downstream outcome.
Travel personalization is only as useful as the accuracy, availability and continuity of the activities, events, offers and properties being promoted.
AI video creation can supply horizontal and vertical assets more efficiently, but generated output still requires controlled variation and human review.
Google’s reported average lift is useful context, not an account-level promise. Base your decision on customer quality and business value.

Your next move is deliberately small: write down the single constraint limiting your current Demand Gen campaign, choose the one expansion capability that addresses it, and define the downstream result before changing the campaign. That turns the expansion from a bundle of new options into a test your team can understand and act on.

References

Search Engine Land — Google expands Demand Gen with messaging ads, travel tools and AI video creation

August 27, 2026

How to Test ChatGPT Ads Bidding and Platform Targeting

You are deciding whether to turn on Maximize results, separate iOS, Android and Web traffic, or trust a larger conversion total. Those look like three independent choices. They are actually one measurement problem: automated bidding can only optimize the goal and conversion signals you give it.

The safest rollout is deliberate. Use platform controls to isolate meaningful behavior differences, automate bids only after the outcome is trustworthy, and keep view-through attribution separate from evidence of incremental growth.

Platform targeting controls surfaces, not audiences

A single crowd connects through separate illuminated routes to smartphone, mobile device, and desktop surfaces.

The Eligible platforms setting lets you choose one or more of the iOS app, Android app and Web when creating a campaign. This answers where an eligible ad can appear. It does not tell the system which customer is valuable, make the conversion event more reliable or replace your campaign goal.

That distinction matters because platform selection can look more precise than it is. Excluding Android, for example, is not an audience strategy. It is a distribution decision that removes Android opportunities from that campaign. You need evidence that the surface itself changes the economics or user journey before you make that trade.

What you know	Practical campaign structure	Main risk
You have no reliable evidence that iOS, Android and Web perform differently	Keep the eligible surfaces together and report them separately where possible	Aggregated results can conceal a weak surface
A surface has a repeatable difference in conversion quality, customer value or user behavior	Create a separate campaign for that surface so its eligibility and budget decisions can be managed independently	Each campaign receives a smaller pool of conversion signals
Conversion tracking is inconsistent between an app and the Web	Repair and validate the measurement path before using reported performance to exclude or scale either surface	Automated bidding may optimize toward a tracking difference rather than a business difference

Do not split campaigns because one platform has a lower click-through rate. First compare the result that matters after the click or view: accepted leads, completed purchases, retained customers or another outcome your business can verify. A surface can attract fewer clicks yet produce better customers. It can also produce cheap conversions that your sales or fulfillment systems later reject.

Before separating platforms, write down the hypothesis in a falsifiable form. For example: Web traffic produces a higher rate of accepted applications than app traffic when both use the same qualification rules. Then confirm that the conversion event, attribution treatment and downstream acceptance rule are comparable. If you cannot make that comparison cleanly, segmentation will create more campaign controls without creating more knowledge.

Maximize results needs a business constraint outside the algorithm

Maximize results automatically sets and adjusts bids toward the campaign’s selected goal, with the aim of generating as many results as possible from the available budget. That is a volume objective. It should not be read as a promise to maximize profit, customer lifetime value or qualified pipeline.

The selected conversion therefore becomes an operating instruction. If you optimize for a shallow event because it happens frequently, the system can become efficient at producing that shallow event. The campaign dashboard may improve while the commercial outcome stays flat.

Write a short optimization contract before enabling automation:

Primary result: Name the exact event the campaign will optimize. Avoid labels such as qualified conversion unless the qualification rule is explicit.
Business acceptance rule: Define what makes the result useful after it enters your CRM, commerce system or other system of record.
Quality metric: Choose the downstream rate or value you will inspect alongside campaign conversion volume.
Budget boundary: Decide how much spend you are willing to treat as test exposure before the business outcome is validated.
Scale rule: State what must improve before you increase the allocation. A higher platform-attributed conversion count is not sufficient by itself.
Stop rule: Identify the signal that will pause the test, such as deteriorating accepted-result cost or a measurement failure.

Because automated bidding spends real money, start with a deliberately limited test allocation. Do not use an amount that would create a material problem if the selected event turns out to be a poor proxy for revenue or qualified demand.

Change one major variable at a time. Expanding platform eligibility and enabling Maximize results in the same test makes a positive result ambiguous: you will not know whether the improvement came from new inventory, different bids or a changed conversion mix. Test the platform structure while holding the bidding approach steady, then test the bid strategy while preserving the chosen platform mix. Keep the goal, creative, offer, landing experience and conversion implementation as stable as the campaign permits.

Evaluate the test over a period that covers your normal conversion delay and business cycle. There is no universal number of days that makes a low-volume campaign conclusive. If the campaign produces too little verified outcome data to distinguish improvement from ordinary variation, keep the decision provisional rather than inventing certainty from percentages.

View-through conversions change the report, not necessarily demand

ChatGPT Ads Manager reports one-day view-through conversions at the campaign, ad group and ad levels. A view-through conversion is attributed when a person converts within one day of seeing an eligible ad and no qualifying ad click receives credit for that conversion.

A view-through conversion is not automatically invalid. It answers a different question from a click-through conversion. It shows that an ad exposure preceded the conversion within the defined window. It does not, by itself, establish that the ad caused a conversion that otherwise would not have happened.

Keep three measurement questions separate

Did the person click before converting? Use click-through conversion reporting to understand the measurable engagement path.
Did an eligible ad view precede the conversion? Use the one-day view-through metric to understand attributed exposure without a credited click.
Did advertising create additional business? Use a controlled incrementality method where the decision warrants it. Attribution reporting alone cannot answer this causal question.

The addition of view-through reporting means more conversions can be attributed beyond conversions generated directly from clicks. Annotate the point at which this reporting became visible in your account. Otherwise, a pre-and-post chart may look like campaign performance improved when only the attribution coverage changed.

Build a compact scorecard with four lines:

Click-through conversions and their cost.
One-day view-through conversions and their share of all ChatGPT-attributed conversions.
Verified business outcomes from your system of record and their cost.
The acceptance rate or realized value of the results attributed to the campaign.

The view-through share is a diagnostic, not a quality score. Calculate it by dividing view-through conversions by all ChatGPT Ads-attributed conversions for the same scope and period. If that share rises sharply, investigate the composition before declaring better performance. Ask whether the eligible platform mix, ad exposure, reporting availability or customer behavior changed.

Use conversion integrations to improve signals, not inflate counts

Advertisers can connect WorkMagic to view ChatGPT campaign performance with other channels and send conversion signals to OpenAI through the Conversions API. That can make downstream outcomes more useful to campaign measurement, but connecting systems does not validate the data automatically.

Document each event name, timestamp, originating system, business definition and rejection rule. Confirm how the same real-world outcome is handled if it can arrive through more than one measurement route. A cross-channel dashboard is useful for reconciliation, but it does not turn overlapping attribution claims into incremental customers.

Use a staged rollout that preserves a readable baseline

Four separated testing chambers show a baseline, added device traffic, constrained automation, and distinct conversion signals.

A clean rollout gives each new control one job. Use this sequence:

Record the baseline. Save the current bid approach, eligible surfaces, goal, conversion definitions, spend and downstream outcome metrics. Include a representative period that covers your usual conversion lag.
Validate the goal event. Trace reported conversions into the system of record. Check that the event fires at the intended moment and maps to the business result named in your optimization contract.
Form a platform hypothesis. Decide whether iOS, Android or Web should differ based on repeatable outcome quality or customer value, not a single top-of-funnel metric.
Test platform eligibility first. Hold the bid strategy and other major inputs steady while you learn whether a surface warrants separate management.
Test Maximize results second. Preserve the selected platform structure so you can judge the automated bidding change against a readable reference.
Separate attribution types. Review click-through and one-day view-through conversions independently, then reconcile both with verified business outcomes.
Scale on commercial evidence. Increase the allocation only when volume and downstream quality support the decision. If they disagree, repair the goal or signal before giving the system more budget.

ChatGPT Ads is also expanding into Brazil and Mexico. If either market is part of your plan, treat geographic expansion as another major variable. Launching a new market while changing platforms and bidding creates several plausible explanations for any movement in performance. Keep the market, offer, language, conversion path and bid test documented separately so you know what you are scaling.

Keep paid ChatGPT performance separate from organic AI visibility as well. Ad-attributed conversions tell you about the paid campaign under its attribution rules. They do not measure whether your brand is cited, recommended or discovered organically in AI-generated answers. Use distinct reporting for those two jobs.

Key takeaways

Platform targeting determines whether a campaign can run on iOS, Android, Web or a combination; it is not a substitute for audience or conversion strategy.
Separate platforms only when repeatable differences in business outcomes justify smaller data pools and additional campaign management.
Maximize results seeks more results from the available budget, so the quality of the selected goal determines what the automation learns to pursue.
Test platform eligibility and bidding changes separately. Changing both at once makes the outcome difficult to interpret.
Report one-day view-through conversions separately from click-through conversions, and do not label attributed exposure as incremental lift.
Scale only when campaign metrics agree with accepted leads, revenue or another verified outcome in your system of record.

Your next move should be a measurement decision, not a settings decision. Name one verified business result, confirm how it reaches ChatGPT Ads, and choose the eligible platform structure that gives you a clean test. Only then should Maximize results receive more budget to optimize.

References

Search Engine Land – ChatGPT Ads adds automated bidding, platform targeting

August 24, 2026

ChatGPT Ads Expand in Europe: A Practical Launch Plan

If you run paid media in Europe, the immediate question is not whether ChatGPT Ads sound interesting. It is whether this channel can reach a valuable decision point, produce an outcome you can measure, and justify budget that already has other jobs.

You do not need a 31-country launch plan yet. You need one testable use case, one clean conversion path, and a firm boundary between paid ChatGPT placement and the separate work of earning visibility inside AI-generated answers.

What the European expansion actually gives advertisers

ChatGPT Ads are expanding to 31 European countries, with Germany, France, Spain, Italy, Sweden, Norway, Denmark, the Netherlands, and Austria among the named markets. This is OpenAI’s largest geographic expansion of the ad product so far.

The European rollout is not initially a broad self-service release. Campaign access will first run through OpenAI’s Ads Solutions team, agency partners, and technology partners. Self-service access through Ads Manager is expected later in the summer. If you want to participate before then, the practical first step is to identify the approved route available to your business rather than waiting for a button to appear in an existing advertising account.

Operational fact	What it means for your plan
Initial access is managed through OpenAI and selected partners.	Prepare a concise campaign brief before requesting access. Expect a sales or partner conversation rather than an instant account setup.
Ads appear only to people using ChatGPT Free and Go.	Do not model reach against all ChatGPT users. Plus, Pro, and Enterprise users remain ad-free.
Ads are labeled and kept separate from generated answers.	Evaluate the placement as paid media. Do not treat it as a way to purchase an endorsement inside the answer.
Advertisers do not receive users’ conversations.	Do not build targeting or reporting assumptions around access to prompt transcripts. Plan around the controls and conversion data actually made available.
Available capabilities include CPM and CPC bidding, conversion optimization, geo-targeting, custom audiences, the OpenAI Pixel, the Conversions API, and third-party measurement integrations.	You can design a performance test, but its value will depend on clean conversion signals and a credible attribution plan.

The platform has moved beyond a minimal ad experiment. OpenAI says testing began in the United States in February, followed by eight additional markets, and that tens of thousands of marketers have advertised on ChatGPT. Those are vendor-reported scale indicators, not proof that the channel will work for your offer. Treat them as a reason to evaluate the opportunity, not as a performance benchmark.

Before authorizing spend, ask your access provider for the exact countries available on your intended start date, supported placements and creative requirements, minimum commitments, targeting options, reporting fields, brand-safety controls, and conversion configuration. A forecast built without those answers is an assumption sheet, not a media plan.

Paid placement and AI answer visibility are separate systems

Two parallel conversational pathways show a glowing sponsored card on one side and source materials flowing into an AI answer on the other.

The most important strategic boundary is easy to miss: advertising does not influence the answers ChatGPT generates. Buying an ad does not make your brand more likely to be recommended, cited, or described favorably in the answer. An ad can appear around a conversation while remaining visibly separate from it.

That means you need two workstreams with different success measures:

Paid ChatGPT advertising: Optimize for delivery, qualified traffic, conversions, customer acquisition, pipeline, or revenue. Judge it as a media investment.
GEO, AEO, and AI visibility: Improve whether your brand and content can be understood, retrieved, cited, and represented accurately in generated answers. Judge it through answer visibility, citations, brand inclusion, accuracy, and resulting traffic or demand.

Keep those results separate in your reporting. Paid conversions are not evidence that your organic AI visibility improved. A new brand citation in an answer is not a paid-media conversion. You can place both under one broader ChatGPT strategy, but combining them into one metric will hide which work produced the outcome.

The opportunity for advertisers comes from the decision context surrounding the placement. People use ChatGPT to explain goals, compare options, test trade-offs, and narrow a purchase. A conventional keyword might show that someone wants project-management software. A conversational decision could include team size, integration needs, budget pressure, security concerns, and a deadline. That context can make the moment commercially valuable even though the advertiser does not receive the conversation itself.

Do not translate that opportunity into an unsupported targeting claim. The expansion details do not establish that you can target individual prompt wording or inspect the reasoning that led to an ad impression. Build your campaign around an identifiable customer decision, then confirm which targeting controls can actually reach it.

A useful campaign brief describes the decision in plain language: help a finance lead compare invoicing platforms for a multi-country team is stronger than target accounting software users. The first gives your message, landing page, proof, and conversion event a common purpose. The second is only an audience label.

Build the first test before self-service access arrives

Self-service Ads Manager is expected later in the summer, but the account interface is not the hard part. Use the lead time to remove ambiguity from the test. A campaign that launches quickly with an unclear decision, mixed markets, and unreliable events will generate data without generating an answer.

Write one business question. Use a form such as: Can ChatGPT Ads generate qualified demo requests for this offer in this market at an acquisition cost we can sustain? Replace the outcome with a purchase, application, booking, or other event only if that event matters to the business.
Select one decision job. Identify what the person is trying to choose, what constraints shape that choice, and what uncertainty prevents action. Do not start with a broad topic such as AI software, travel, or insurance.
Choose one market or a tightly related cluster. Keep language, offer, pricing, sales coverage, and conversion operations consistent enough that you can explain performance. A pooled 31-country campaign may conceal why one market worked and another failed.
Prepare message components, not format assumptions. Define the problem, the relevant differentiator, the proof available, the next action, and any qualification condition. Adapt those components to the supported ad format after access is confirmed.
Continue the decision on the landing page. Reflect the same use case and constraints in the headline, explain who the offer is for, show the proof needed to compare it, and make the next step obvious. Sending conversationally qualified interest to a generic homepage discards the context that made the channel promising.
Map the conversion path before spending. Write the expected sequence from ad interaction to meaningful business outcome. Define which event is primary, which events are diagnostic, who owns each event, and where revenue or sales qualification enters the record.
Pre-commit the decision rules. Decide what would justify expansion, require a landing-page change, trigger a targeting review, or stop the test. Use thresholds based on your economics rather than copying a generic click-through rate or cost-per-click target.

The landing page deserves particular attention. Someone arriving from a decision-oriented conversation may need comparison evidence, eligibility details, implementation requirements, pricing context, or a clear explanation of the next step. Give that person the shortest credible path to resolving the uncertainty. Do not force them to reconstruct the offer from a company-wide navigation menu.

If qualification matters, capture it with deliberate fields or downstream sales data. An optional question such as What are you trying to solve? can add context, but every field adds friction. Ask only for information that will change routing, qualification, or follow-up.

The OpenAI Pixel and Conversions API are intended to measure outcomes beyond the click. Your implementation plan should still specify event names, primary and secondary conversions, browser-versus-server ownership, and deduplication so the same action is not counted twice. Validate events in a test environment before using them to optimize live spend.

Tracking deployment also deserves a market-by-market privacy and legal review. Pixel, server-side, and custom-audience implementations can involve different data flows. Give the responsible privacy, security, and legal owners an accurate data map before launch rather than asking them to approve a vague description of conversion tracking.

Treat 31 European countries as a portfolio, not one market

A strategist allocates test tokens among color-coded regional clusters on an unlabeled map of Europe beside abstract conversion and measurement pieces.

A large availability map can create pressure to launch everywhere. Resist it. Geo-targeting gives you the ability to select markets; it does not make the same offer, language, evidence, or conversion process equally ready in each one.

Score every candidate market on five practical dimensions:

Commercial fit: Is the offer available, competitively priced, and economically viable in that country?
Decision fit: Can you identify a specific evaluation or purchase decision that ChatGPT may help the customer work through?
Localization readiness: Are the ad message, landing page, proof, pricing, terms, and follow-up appropriate for the local language and market rather than merely translated?
Operational coverage: Can sales, support, fulfillment, onboarding, or service delivery handle the demand you are trying to create?
Measurement readiness: Can you collect the primary conversion consistently and connect it to qualification, revenue, or another business outcome?

Launch first where all five are credible. Germany, France, Spain, Italy, Sweden, Norway, Denmark, the Netherlands, and Austria are among the included countries, but inclusion alone does not establish priority. Your first market should be the place where a clean test is possible, not automatically the largest country on your planning sheet.

Keep country-level reporting visible even if several markets share a campaign structure. A low blended acquisition cost can hide an expensive market being subsidized by a strong one. The reverse is also possible: a small but efficient market can disappear inside an aggregate report dominated by a larger market.

Localization should cover the decision, not just the words. Check whether the proof points are recognizable locally, whether the stated price and availability are accurate, whether the conversion action matches local buying behavior, and whether follow-up arrives in the promised language. These are conversion controls, not cosmetic refinements.

Measure whether conversational intent becomes business value

ChatGPT Ads now support CPM and CPC buying as well as conversion optimization. That gives you several ways to buy media, but it does not remove the need to define success. A cheap click can still be commercially useless, while a higher-cost visit can be valuable if it produces a qualified customer.

Use a four-level measurement ladder:

Delivery: Record spend, impressions, and the buying model used. This tells you whether the campaign ran as intended, not whether it worked.
Traffic quality: Track whether visitors reach the relevant offer content, continue through the intended path, and complete meaningful intermediate actions. Define those actions before launch.
Business outcome: Connect the primary conversion to qualification, purchases, bookings, accepted applications, pipeline, revenue, or the outcome your campaign was designed to create.
Incremental value: Ask whether ChatGPT Ads produced outcomes that would probably not have occurred through your existing channels. Where feasible, use a controlled geography, a credible holdout, or another pre-agreed comparison rather than relying only on platform-attributed conversions.

Do not compare ChatGPT Ads with search or social using only click-through rate. Those channels can reach different contexts and use different placement mechanics. Compare them at the deepest reliable business outcome you share, then use channel-specific diagnostics to explain the difference.

Conversion optimization is useful only when the chosen event is accurate and meaningful. If the platform is trained toward an easy but weak event, such as an unqualified form submission, it may improve the reported result while moving away from business value. Start with clean measurement, verify lead or transaction quality, and then decide which event deserves optimization priority.

OpenAI has also added third-party measurement integrations. Use independent measurement where it helps reconcile platform reporting with analytics, CRM, commerce, or finance records. Differences between systems should be investigated through attribution windows, event definitions, identity matching, and deduplication rather than resolved by automatically choosing the larger number.

Key takeaways

ChatGPT Ads are expanding to 31 European countries, but initial campaign access is managed rather than broadly self-service.
Only Free and Go users receive ads; Plus, Pro, and Enterprise users remain ad-free.
Paid placement is labeled and separate from ChatGPT’s answer, so ad spend must not be reported as improved GEO or organic AI visibility.
The strongest first test pairs one customer decision with one market, one relevant landing path, and one meaningful conversion.
Judge the channel through qualified business outcomes and incremental value, not clicks alone.

Before requesting access, write the one-sentence business question, select the first market, and audit the conversion event you would ask the platform to optimize. If any of those three remains vague, use the time before self-service arrives to fix it. That preparation will tell you more than launching across Europe simply because the inventory became available.

References

Search Engine Land — ChatGPT Ads are expanding to 31 European countries

August 19, 2026

Merchant Center Agency Scaling for Up to 1,000 Accounts

You’re adding clients faster, and the immediate question is whether one Merchant Center agency account can keep carrying the portfolio. The harder question is whether your operating model will remain controlled as the account count rises.

Google’s documented ceiling removes one important uncertainty. A Merchant Center for Agencies account can accommodate a large portfolio, but capacity alone won’t prevent confused ownership, unauthorized changes, stalled onboarding, or forgotten offboarding. You need to turn the limit into an account-management plan.

Treat 1,000 as a capacity ceiling, not a growth target

Agency Admins can link up to 1,000 client Merchant Center accounts under one agency account. The maximum was previously undocumented, and its clarification does not introduce new linking functionality.

That distinction matters. The number helps you plan infrastructure, but it says nothing about how many accounts your team can manage well. An agency with unclear ownership can lose control long before it reaches the platform ceiling. An agency with a disciplined operating system can use the available capacity without turning the central account into an unsearchable holding area.

Start by measuring linked accounts as the platform measures them. Your sales team may count clients, contracts, or brands, but the relevant capacity unit is the linked Merchant Center account. Maintain four portfolio figures:

Current load: accounts that are linked now.
Committed demand: accounts attached to signed or approved onboarding work but not yet linked.
Probable demand: accounts likely to enter onboarding from the active pipeline.
Planned removals: relationships moving through an authorized offboarding process.

Use those figures to calculate headroom rather than waiting for a linking request to expose a capacity problem. Keep committed and probable demand separate. Treating every sales opportunity as guaranteed inflates the forecast, while ignoring signed onboarding work understates it.

The practical trigger is not account number 1,000. It is the point at which forecast demand could consume your remaining headroom before you have approved another structure. That is when leadership needs to make the decision, because account architecture should not be designed in the middle of a client launch.

Build an account registry before scaling the portfolio

An organized modular registry holds rows of abstract merchant account cards while hands add a new card and verify an access token.

The agency interface should not be your only system of record. Maintain a registry that explains why every account is present, who owns the relationship, and what should happen next. This can live in your established work-management system as long as it is governed and consistently updated.

At minimum, give every linked-account record these fields:

Client name and the exact Merchant Center account identifier.
Internal lifecycle state.
Client-side contact responsible for approving access.
Agency relationship owner.
Operational owner and backup contact.
Date and reason for the original linking request.
Agency Admin who completed the approved action.
Applicable team, business unit, or portfolio segment.
Open exceptions or unresolved handoff work.
Offboarding decision and completion state, when relevant.

The account identifier is especially important. Names change, abbreviations collide, and staff members remember clients differently. The identifier gives onboarding, delivery, and offboarding teams one unambiguous object to reference.

Use internal lifecycle states

Define lifecycle states in your registry instead of assuming everyone interprets a generic status such as active in the same way. A workable internal sequence is:

Requested: an intake record exists, but the request has not passed validation.
Approved for linking: the client, account identifier, agency owner, and authority to proceed have been confirmed.
Admin action pending: the request is ready for an Agency Admin.
Linked, handoff pending: the administrative action is complete, but operational ownership has not been accepted.
Managed: the account has a named owner and has entered the agency’s normal workflow.
Exception: the record has a mismatch, failed handoff, ownership question, or another issue requiring review.
Offboarding approved: the commercial relationship has ended or changed, and the authorized removal process is underway.
Closed: the offboarding work and internal recordkeeping are complete.

These are operating labels, not claims about status names inside Merchant Center. Their purpose is to keep a submitted request from being mistaken for a completed handoff.

Make linking a controlled handoff

Because Agency Admins perform the linking action, they can become either an effective control point or an avoidable bottleneck. Give them a complete, validated request rather than asking them to reconstruct missing context.

Establish authority. Record who requested the relationship and who approved it on the client and agency sides.
Validate the target. Match the client name to the intended Merchant Center account identifier before an admin acts.
Assign ownership. Name the agency relationship owner, operational owner, and backup before linking.
Complete the approved action. An Agency Admin links the validated account and records the outcome.
Accept the handoff. The operational owner confirms responsibility, reviews the account in the normal delivery workflow, and closes or escalates any exception.

A successful link proves that the administrative relationship was established. It does not prove that the client account is correctly configured, that its product data is healthy, or that the delivery team knows what it owns. Keep linking confirmation and operational validation as separate checklist items.

Decide whether one agency structure still fits

The newly documented maximum makes one part of the decision simple: a single agency account cannot be your unexamined plan for a forecast beyond 1,000 linked accounts. Below that ceiling, the better structure depends on governance as well as capacity.

Decision area	Reason to keep the portfolio together	Trigger to design another structure
Capacity	Forecast demand remains within the documented limit with deliberate headroom.	Committed and probable demand could consume the remaining capacity before a new structure can be approved.
Administration	The same controlled Agency Admin process can serve the full portfolio.	Separate groups require materially different approval authorities or access governance.
Operations	Teams use the same intake, ownership, exception, and offboarding standards.	Business units operate independently and cannot maintain one dependable system of record.
Risk isolation	Central oversight improves consistency and makes reconciliation easier.	Contractual, organizational, or security boundaries require stronger operational separation.
Continuity	A central owner can reconcile the complete portfolio during staffing or organizational changes.	No team has credible responsibility for the portfolio as a whole.

Do not create extra agency accounts merely as an assumed workaround. The published maximum defines what one agency account can carry; it does not, by itself, establish which fallback structure Google will support for your organization. If your forecast could exceed the ceiling, confirm the supported arrangement with Google before promising an onboarding path to clients.

Likewise, do not fragment the portfolio solely to make the numbers look tidy. Every additional operating structure introduces another administrator roster, capacity view, reconciliation process, and handoff boundary. Separation should solve a defined capacity or governance problem that is worth that overhead.

Scale controls and exception handling with the account count

A large network of blue account nodes passes through control gates while one amber exception is diverted to an operator for review.

Large portfolios usually become difficult at their edges: a request with the wrong identifier, an employee who changes teams, a client that has left but remains in the registry, or a linked account that never received an operational owner. Your control system should make those exceptions visible before they disappear into the total account count.

Assign explicit responsibility for the functions below. One person may hold more than one role, but the responsibility should never be implicit:

Agency administration: performs validated linking actions and maintains the authorized administrator roster.
Portfolio ownership: maintains the registry, capacity forecast, and reconciliation process.
Relationship ownership: confirms that each linked account corresponds to a current, authorized client relationship.
Operational ownership: accepts the delivery handoff and resolves account-level work.
Offboarding ownership: coordinates authorized removals and closes the internal record.

Reconcile the registry against the agency view after meaningful change, not only when someone notices a discrepancy. Useful triggers include a batch of onboardings, a change to the Agency Admin roster, an employee departure, the end of a client relationship, an acquisition, or a period of unusually high intake.

Your exception queue should surface conditions that require a decision:

A linked account has no active relationship owner.
An onboarding request has no validated account identifier.
An admin action has no matching approval record.
A completed link still lacks operational acceptance.
An offboarding record remains open after the relationship has ended.
The registry count does not match the visible agency portfolio.
The capacity forecast has entered the agency’s internally defined buffer.

Track the age and ownership of exceptions, not just their quantity. A small queue of unowned issues is more dangerous than a larger queue in which every item has an accountable person and a clear next action.

Automation can help with reminders, duplicate checks, status synchronization, and capacity warnings if your toolchain supports them. Keep authority with people: linking and offboarding should still trace back to a validated request and an identifiable approver. Automating an incomplete process only makes the resulting ambiguity move faster.

Key takeaways

One Merchant Center for Agencies account can support up to 1,000 linked client accounts, and Agency Admins perform the linking.
The 1,000-account figure is a documented ceiling, not evidence that every agency can operate effectively at that scale.
Forecast linked accounts separately from clients, contracts, or sales opportunities.
Maintain a governed registry with exact account identifiers, approval records, owners, lifecycle states, and offboarding status.
Treat linking and operational acceptance as separate steps.
Design another structure before forecast demand reaches the ceiling, and confirm the supported arrangement with Google rather than assuming an unlimited workaround.

Start with the registry. Reconcile it against your current agency view, name an owner for every account, classify every pending request, and calculate the headroom against committed onboarding work. Once you can explain who owns each link, why it exists, and what happens next, the 1,000-account capacity becomes useful infrastructure instead of a future surprise.

References

Search Engine Land – Google Merchant Center for Agencies now supports up to 1,000 linked accounts

August 14, 2026

Campaign Manager 360 Real-Time Reporting API Guide

You need Campaign Manager 360 performance data inside a dashboard while someone is still looking at the screen. The traditional create-run-poll-download workflow can do the reporting, but it makes an interactive product carry the machinery of a batch job.

The reportData.query endpoint gives you a shorter path: describe the data you need in the request and receive structured JSON synchronously. That can simplify dashboards and ad-hoc analysis considerably. It does not mean every reporting workload should move, nor does the word “real-time” guarantee that every underlying metric is updated instantly.

The reporting flow is now a direct request-response path

The traditional Campaign Manager 360 reporting flow is built around generated reports. Your application creates a Report resource, runs it, polls until processing finishes, and downloads the resulting file. That sequence remains useful when the file is part of the deliverable, but it introduces several states that an interactive application must manage.

Create or identify the report configuration.
Start the report run.
Poll for completion.
Download and parse the generated CSV or Excel file.
Transform the result into the shape required by your interface or analysis.

With reportData.query, developers can instead specify dimensions, metrics, and filters in the request body and receive structured JSON in the response. You do not have to create a Report resource before asking for the data.

Define the dimensions that determine the result’s grain.
Select the metrics needed by the dashboard or analysis.
Apply filters that keep the request focused.
Submit the synchronous query.
Map the returned JSON into your application’s data model.

The practical gain is not simply fewer API calls. Your application no longer has to model a report job, persist its status, poll it, retrieve an artifact, and parse that artifact before it can show a result. For a user-driven dashboard, removing that orchestration can make both the code and the experience easier to reason about.

Keep the distinction precise, though: reportData.query simplifies the retrieval path. It does not make the Reports service obsolete, remove the need for a reporting data model, or turn an unfocused query into a fast one.

Choose the endpoint by workload, not by which API is newer

Two data-reporting routes show a short interactive query path beside a larger multistage batch-processing path.

The clearest implementation decision is based on how the result will be consumed. Use reportData.query when a person or application needs a structured answer immediately. Keep the Reports service when the workload is large, scheduled, or expected to produce a downloadable file.

Decision factor	reportData.query	Reports service
Interaction model	Synchronous request and response	Create, run, poll, and download
Response format	Structured JSON in the API response	Generated CSV or Excel file
Best fit	Interactive dashboards, real-time reporting experiences, and ad-hoc analysis	Large datasets, scheduled reporting, and file-based workflows
Configuration	Dimensions, metrics, and filters are supplied directly with the query	A Report resource defines the report before retrieval
Execution consideration	A query can run for up to 60 seconds	Completion is handled as an asynchronous report job

Four questions usually settle the choice:

Is a person waiting for the answer? A dashboard refresh, filtered table, or investigative view is a strong candidate for reportData.query.
Is the output itself a CSV or Excel deliverable? Keep the Reports service rather than retrieving JSON only to recreate the same file workflow.
Is this a large or scheduled extraction? The existing Reports service remains the preferred route.
Does the same system have both interactive and batch needs? Use both paths. A hybrid architecture is a deliberate workload split, not an incomplete migration.

This prevents a common architectural mistake: replacing a sound batch process merely because a more convenient interactive endpoint exists. The new endpoint solves a different access pattern. It should take over the requests that benefit from synchronous JSON while the Reports service continues handling work that benefits from generated files and asynchronous execution.

Design interactive queries that remain useful under pressure

A direct endpoint removes report-job ceremony, but your dashboard still needs a disciplined query layer. The following design choices determine whether reportData.query feels responsive and trustworthy in production.

Start with the user’s question, not every available field

Define one question for each dashboard component. A campaign summary, a filtered placement table, and a diagnostic drill-down do not need to share one universal request. Give each component the smallest dimension grain, metric set, and filter scope that answers its question.

Write down a compact query contract before implementation:

The decision or question the result supports.
The dimensions that determine what one result row represents.
The metrics the interface will actually display or calculate with.
The filters controlled by the application and the filters controlled by the user.
The behavior the user sees while the request is running.
The fallback shown when the request cannot return a usable result.

This contract helps you notice accidental scope growth. If a new chart needs a different grain, give it a separate query rather than quietly expanding an existing request and making every dashboard refresh carry the extra work.

Treat 60 seconds as a ceiling, not a target

The endpoint allows queries to run for up to 60 seconds. That accommodates meaningful interactive analysis, but a dashboard can still feel broken long before the request reaches its limit.

Design the interface for a genuinely synchronous operation. Show a clear loading state, keep unrelated controls usable, and decide what happens if the request takes longer than the user’s workflow can tolerate. Where appropriate, retain the last successful result and label it as such rather than replacing useful data with an indefinite spinner.

Do not hide a consistently slow query behind a longer loading message. Narrow its dimensions, metrics, or filters. If the workload is inherently large rather than accidentally broad, route it to the Reports service.

Do not equate synchronous retrieval with instant measurement

“Real-time” describes the reporting access pattern here: your application submits a query and receives data directly instead of waiting for a generated report file. That alone does not establish how quickly every underlying campaign event becomes available as a reportable metric.

If freshness affects an operational decision, verify it for the dimensions and metrics you use. Give the dashboard an “as of” indicator based on information your implementation can substantiate, and avoid labels such as “live” or “instant” unless you have validated what those words mean for that view. This keeps a faster retrieval method from creating a stronger freshness promise than the data supports.

Put a stable adapter between CM360 and the interface

Structured JSON is easier to consume than a downloaded file, but your UI should not become a direct reflection of a vendor response. Map the response into an internal model with names and types that make sense to your application.

Keep the API request definition in one reporting layer rather than duplicating it across dashboard components.
Validate that the returned structure contains what the component needs before rendering it.
Centralize metric labels and formatting so the same measure is not presented differently across views.
Record the query definition alongside operational logs so a bad result can be traced to its dimensions, metrics, and filters.
Version your internal contract when a dashboard changes its grain or meaning.

This adapter also preserves your options. The UI can consume one internal shape even if some views use reportData.query and other data arrives through the Reports service.

Separate no data, zero, slow, and failed

These states can look similar in an empty chart, but they mean different things:

No matching data: the selected dimensions and filters produced no rows.
Measured zero: the query returned a legitimate result whose displayed metric is zero.
Still running: the application has not received the synchronous response yet.
Failed request: the application cannot present the requested result.
Last successful result: a previous result remains visible while its replacement is unavailable.

Model and label these states explicitly. Otherwise, an API problem can be mistaken for campaign performance, or an empty filter result can be presented as a technical failure.

Also control how often the interface sends requests. Trigger queries on deliberate actions, avoid submitting a new request for every unfinished input change, and reuse identical results for an appropriate period when your freshness requirements permit it. The right reuse period is a product decision; the existence of a synchronous endpoint does not require every screen interaction to generate a new API call.

A low-risk rollout keeps the batch path intact

Parallel reporting pipelines pass through a controlled traffic junction and comparison stage, with a return route to the established batch system.

You do not need to redesign the entire reporting stack to benefit from reportData.query. Start with one view where report creation, polling, or file parsing is clearly getting in the way of an interactive experience.

Inventory the current flow. Identify where the application creates the Report resource, starts the run, polls, downloads the file, parses it, and transforms it for display.
Classify the use case. Confirm that a person or interactive application needs the result directly. Leave scheduled, large, and file-based jobs in the Reports service.
Write the query contract. Specify the exact dimensions, metrics, filters, expected result grain, loading behavior, and failure behavior for the selected view.
Build the response adapter. Convert the returned JSON into the internal shape already expected by the interface, or introduce a stable model that both reporting paths can use.
Verify meaning, not just transport. Compare the new view with the existing reporting output for the same requested scope. Investigate differences before assuming that receiving JSON means the migration is complete.
Exercise the slow and empty paths. Confirm that the interface remains understandable if a query runs for a substantial part of the allowed window, returns no matching data, or fails.
Switch only the interactive read path. Keep existing scheduled reports and downloadable exports running until there is an independent reason to change them.

Measure the rollout by what it removes from the interactive path: report-resource management, polling, file retrieval, and parsing. Do not judge it by how much legacy reporting code you can delete. If that code still supports a valid batch workload, retaining it is the correct design.

Campaign Manager 360 reporting API FAQ

Is reportData.query a streaming API?

No. Its documented interaction is a synchronous query that returns structured JSON. Your application requests a defined result; it is not described as subscribing to a continuous stream of campaign events.

Does “real-time reporting” mean every metric is instantly current?

Not on the evidence available for this endpoint. The direct synchronous response removes the generated-report workflow, but that does not by itself define the freshness of every underlying metric. Validate freshness for your use case before making a user-facing promise.

Should an existing Reports service integration be migrated completely?

No. Keep the Reports service for large datasets, scheduled jobs, and workflows that require CSV or Excel downloads. Move only the interactive and ad-hoc requests that benefit from direct JSON.

What is the best first use case?

Choose one narrowly scoped dashboard view whose user currently waits for a report job or whose implementation exists mainly to download and parse a file. Define its dimensions, metrics, and filters; build the JSON adapter; then compare its output with the established reporting path before expanding the rollout.

Your next step is small and concrete: identify one interactive report, write down the exact question it answers, and determine whether a synchronous query can answer it within the endpoint’s 60-second window. If it can, migrate that read path. If it is fundamentally a large export or scheduled artifact, leave it where it belongs.

References

Search Engine Land – Google adds real-time reporting endpoint to Campaign Manager 360 API

August 12, 2026

ChatGPT Ads and Transactions: A Practical Growth Strategy

If your ChatGPT plan ends when your brand earns a mention or a click, you are planning for a funnel that is already changing. Diners can now move from a restaurant recommendation to a Yelp reservation or waitlist inside the conversation, while eligible advertisers can buy placement around relevant conversations through ChatGPT Ads.

You now need to manage three connected layers: recommendation visibility, paid acquisition, and transaction readiness. They can reinforce one another, but they are not interchangeable. The first strategic decision is to identify which layer should produce the result you want.

ChatGPT now holds three parts of the commercial journey

Traditional search marketing assumes a familiar handoff: the search engine presents a result, the user clicks, and the website handles the remaining persuasion and conversion. ChatGPT can support that journey, but it can also insert advertising before the click or host an action before the user reaches your site.

Commercial surface	What the user does	What you can control	Primary measurement
Recommendation visibility	Receives your brand, product, or business as part of an answer	Clear factual content, consistent entity information, supporting evidence, and reliable external business records	Presence, factual accuracy, citations, qualified referral traffic
Sponsored placement	Sees an ad associated with a relevant conversation and may click	Eligibility, geography, first-party audiences, context hints, bid, creative, and landing page	Impressions, clicks, CPC, landing-page conversions, CPA
Embedded transaction	Completes an action such as reserving a table or joining a waitlist in the chat experience	Partner data, availability, transaction infrastructure, confirmation, and post-transaction service	Completed actions and the corresponding records in the transaction provider

A business may participate in one layer without participating in the others. Buying an ad does not mean you should assume stronger placement in an unsponsored answer. Being recommended does not mean ChatGPT can complete a transaction for you. An embedded action may also send the user to a partner, rather than your website, for later management.

Report the layers separately. Otherwise, a rise in paid clicks can be mistaken for better AI-search visibility, while an increase in partner-managed transactions may be invisible in website analytics.

Run four checks before allocating a ChatGPT Ads budget

Two marketing professionals examine four visual readiness checkpoints before moving an advertising token through an illuminated gateway.

ChatGPT Ads will not fit every audience or business. Before you write creative, pass four go-or-no-go checks.

Audience: Ads can serve only to people OpenAI believes are 18 or older on the Free and Go tiers, including logged-out sessions. If your most valuable buyers tend to use higher paid tiers, the reachable audience may be a poor match.
Location: Current targeting covers the United States, Australia, Canada, Japan, New Zealand, South Korea, and the United Kingdom. You can target or exclude locations at the country, region, designated market area, or postal-code level.
Policy: Restricted categories include adult content, alcohol, tobacco, financial services, gambling, and others. Policy materials have also shown ambiguity around legal-service advertising, so visible ads from a competitor are not proof that your own offer is eligible.
Economics: The self-service minimum is $25 per day, while early campaign observations put average CPCs around $2 to $5 across industries. Those CPCs are preliminary observations, not a dependable benchmark for every market. A bid below $3 may trigger a warning that the ad will not deliver; that threshold appears to be fixed rather than a personalized forecast.

The budget floor is an entry requirement, not evidence that $25 will generate enough activity for a sound decision. Work backward from the maximum customer-acquisition cost your business can tolerate. If the observed CPC range cannot support that number at a realistic landing-page conversion rate, fix the offer or measurement before funding the campaign.

Account ownership deserves attention as well. The advertiser should create and own the account, then add its agency as a user. Agencies are not supposed to create accounts on behalf of clients, and the platform does not yet offer a direct equivalent to Google Ads Manager Accounts or Meta Business Manager. Collect the legal business name, business tax ID, payment card, and favicon before setup so account administration does not delay the launch.

Structure campaigns around decisions, not keyword lists

ChatGPT Ads has no keyword targeting, demographic targeting, or conventional in-market audiences. The available controls include geography, uploaded first-party audiences, context hints, and the language used in your ad and landing page. Importing a paid-search keyword spreadsheet unchanged will therefore create the wrong campaign architecture.

The account hierarchy will look familiar:

Campaign: Standard or product-feed type; Reach, Clicks, or Conversions objective; included and excluded locations; included and excluded custom audiences; daily or total budget; optional conversion event; and start and end dates.
Ad group: Bid, default destination URL, and context hints.
Ad: Destination URL, headline, description, and image.

Use that structure to isolate the decision the user is trying to make. A practical build sequence looks like this:

Write the conversational situation as a sentence. Include the problem, important constraint, and decision stage. This is more useful than a list of loosely related search terms.
Keep one intent family in each ad group. The ad, context hints, and destination should all continue the same task. Separate early education from urgent comparison or purchase intent.
Select an objective that matches the next measurable event. Use Reach when qualified exposure is the result, Clicks when the destination page must continue the journey, and Conversions only after the OpenAI pixel and conversion event are working correctly.
Design within the actual creative limits. Headlines have a 50-character maximum, descriptions have a 100-character maximum, and either can be truncated. Put the useful distinction first. The image must be a square PNG or JPG of at least 256 by 256 pixels.
Make the landing page a direct continuation. If the conversation concerns a specific problem, constraint, product, or location, the destination should address it immediately. Do not send every context to a generic homepage.
Validate measurement before optimizing bids. Click campaigns charge per click. Reach campaigns charge per 1,000 impressions. Conversion campaigns require the pixel, still charge per click, and allow a bid cap.

OpenAI uses a relevance-weighted, second-price auction. Bid size matters, but landing-page relevance and ad quality also contribute to selection. When delivery is weak, raising the bid is only one possible response. First inspect whether the context, promise, creative, and destination describe the same user need.

This also changes creative testing. Do not test two ads that target different decisions and then attribute the result to wording. Hold the intent family and destination constant while changing one material element, such as the promise, proof point, or image. The platform is still evolving, so record the configuration and launch date with every result.

Becoming transactable starts outside ChatGPT

A generic conversational interface connects to product, inventory, reservation, payment, and fulfillment systems that support a completed transaction.

The restaurant integration exposes the operational model clearly. Yelp already supplies reviews, ratings, photos, and business details to ChatGPT. It now also supplies Reservations and Waitlist for thousands of restaurants in the United States and Canada. The user can complete the initial action inside ChatGPT but manages or modifies the booking through Yelp.

That means the conversion surface and the system of record may belong to different companies. Your website, business profile, transaction provider, and in-chat experience must still agree on what can be booked and what happens next.

Identify the transaction rail. Determine which booking, commerce, or lead-management provider can actually complete the action for your category. Do not assume a feature available to restaurants is available to every business.
Reconcile business data. Check the name, location, offering, imagery, availability, and customer-facing details on your site against the partner record. Correct contradictions at the system that supplies the action.
Match structured data to visible content. JSON-LD should express the same facts a person sees on the page. Do not use markup to claim an offer, location, availability state, or action that the visible page and transaction system cannot support.
Test the complete action. For a restaurant, that includes finding the business, selecting a time or joining the waitlist, receiving confirmation, and following the route for modification. Test as a customer would, not merely by checking that the listing exists.
Assign post-transaction ownership. Decide who handles changes, failures, and customer questions when the initial action begins in ChatGPT but the record is managed elsewhere.

JSON-LD is valuable because it gives machines a less ambiguous representation of visible facts. It does not create live inventory, a booking connection, payment handling, or customer support. Treat schema as a data-quality layer and the transaction provider as an operational layer. You need both to be accurate, but they solve different problems.

Restaurants using Yelp Guest Manager now have another channel at the point of dining choice. Yelp’s broader position is also instructive: its content and booking capabilities support experiences across ChatGPT, Apple Maps, Alexa+, Microsoft Bing, DuckDuckGo, and Yahoo. Maintaining reliable partner data can therefore improve transaction readiness across more than one discovery surface.

Measure each layer before combining attribution

A single line called ChatGPT traffic will conceal more than it reveals. Maintain three measurement ledgers until you have reliable identifiers that connect them.

Recommendation ledger: Track a stable set of priority questions, whether your brand appears, which facts are accurate, what evidence or citations accompany it, and whether referral visits follow.
Advertising ledger: Record campaign objective, intent family, audience inclusion or exclusion, geography, spend, impressions, clicks, CPC, landing-page conversions, conversion rate, and CPA.
Transaction ledger: Reconcile actions initiated through ChatGPT with confirmed records in the booking or commerce provider, including later modifications where the provider exposes them.

Do not count an in-chat reservation as a website conversion when no website visit occurred. Do not credit a sponsored-click conversion to improved recommendation visibility. If a provider supplies a ChatGPT referral label or another reliable identifier, preserve it in downstream records rather than replacing it with a generic AI category.

For paid campaigns, inspect the sequence rather than one headline metric. Low delivery can reflect eligibility, targeting, bid, or relevance. Strong click-through with weak conversion usually moves the investigation to the promise, landing page, offer, or tracking. Recorded conversions with missing transaction records indicate a measurement or operational problem, not campaign success.

Key takeaways

ChatGPT can support recommendation, paid placement, and an embedded transaction, but a brand does not automatically participate in all three.
ChatGPT Ads reaches eligible adults on Free and Go tiers, including logged-out sessions, rather than every ChatGPT user.
There are no keywords, demographic segments, or conventional in-market audiences, so organize ad groups around conversational decisions.
The current self-service floor is $25 per day, while observed CPCs of $2 to $5 remain early, non-universal benchmarks.
Structured data can clarify an offer, but it cannot replace the provider connection that supplies availability and completes an action.
Recommendation visibility, advertising performance, and partner-managed transactions require separate measurement before attribution can be combined responsibly.

Start with one high-intent customer decision. Choose the commercial surface that should handle it, repair the data and operational handoffs, define one verifiable outcome, and only then launch the smallest campaign or integration test that can answer a real business question.

References

August 10, 2026

Chatbot-Native Agent Ads: How to Prepare Your Business

Your next paid campaign may have to convert a question before it earns a pageview. In the emerging chatbot-native model, an ad click would open a business-specific ChatGPT conversation that can answer questions, surface products and capture leads.

That is a meaningful change, but it is not yet a settled advertising product. The capability appears limited to a small group of advertisers, and the end-user experience has not been widely observed. Your practical move is not to forecast placements or rebuild your media plan. It is to make your business facts, agent rules, live systems and conversion paths ready for a conversation to become the destination.

Key takeaways

A chatbot-native agent ad is not merely an AI-written ad or a chatbot added to a landing page. The conversation itself becomes the post-click experience.
Your website remains important because it can supply the public facts used to construct the business profile. Contradictory or vague pages can therefore become advertising problems.
Use each information layer for the job it handles best: pages for durable public facts, feeds for catalog data, approved tools for live values, instructions for behavior and forms for conversion.
Build each campaign around one completed customer job. A general-purpose agent is harder to control, test and measure.
Optimize for verified outcomes and answer quality, not raw chat volume or conversation length.

The destination changes from a page to a decision

A conventional landing page presents a fixed information architecture. The visitor decides which headline applies, which section to read, which filter to use and whether the form is worth completing. A business agent takes on some of those decisions. It interprets the request, asks for missing information, selects an answer and proposes a next action.

This means the first agent response is not supporting copy. It is the landing experience. If the agent misunderstands the intent, gives an unsupported answer or requests contact details too early, the campaign has already failed even if the ad earned a click.

The distinction also changes ownership. Paid media still owns the promise in the ad, but it cannot own the entire experience. Content teams own the durable facts. Product and operations teams own current availability and other changing values. Sales or service teams define qualification and escalation. Security and legal teams set limits on data collection and actions. Analytics must connect the conversation to a business outcome.

Start with a campaign contract before you write creative. It should answer these questions:

What specific question or task brings the user into the conversation?
What can the agent promise to help the user accomplish?
Which facts must be available for the agent to deliver that help?
Which claims require a live system check rather than a page or prompt?
What action marks successful completion?
What safe fallback is offered when the agent cannot answer or act?

If those answers are vague, more prompt writing will not rescue the campaign. You have an undefined customer journey, not an instruction problem.

Build the context stack before writing the ad

The apparent setup begins by crawling a company’s website to generate a business profile containing common questions, support information and general context. Advertisers can then combine that profile with custom instructions, product feeds, Model Context Protocol tools for live business data and lead-generation forms.

Think of this as a context stack, not a single master prompt. Each layer should have a narrow responsibility and an explicit release check.

Context layer	What it should control	Release check
Website and generated business profile	Durable public facts, policies, support information and common customer questions	Can a reviewer trace each important answer to a current, canonical page?
Custom instructions	Scope, interaction rules, recommendation logic, uncertainty language and escalation behavior	Does the agent behave predictably when required information is missing?
Product feed	Structured catalog records and product attributes supplied by the business	Do identifiers, names and attributes agree with the customer-facing catalog?
Approved MCP tools	Live values and actions from intentionally connected business systems	Does the agent fail safely when a tool returns no result or becomes unavailable?
Lead form	The minimum user information required for the agreed next step	Is every field necessary, explained and requested only when it becomes relevant?

Do not duplicate the same changing fact across all five layers. If availability is live, retrieve it from the approved live system. If an offer attribute belongs in the catalog, maintain it in the feed. Let the instructions explain when the agent should use that information, not what the current value happens to be.

Make the website safe to summarize

A crawl can only work with what you publish. If one page describes a service as available everywhere while another limits it to named locations, the conflict is now more than a conventional content-quality issue. It can affect what an advertising agent represents to a prospective customer.

Audit facts rather than merely auditing pages:

List the facts the agent would need about your identity, offerings, locations, service areas, eligibility, policies, support channels and next steps.
Assign one canonical public location to each durable fact. Supporting pages may restate it, but they should not introduce different conditions.
Find conflicting names, qualifications and policy language across product pages, help content, location pages and forms.
Place the qualifier beside the claim it limits. Do not expect an agent or a customer to combine a broad promise from one section with an exception buried elsewhere.
Separate durable facts from values that can change during a conversation. Changing values belong in a maintained feed or live system when possible.
Give each important fact an internal owner and review trigger. A technically crawlable page can still be operationally stale.

JSON-LD can support this work when it expresses the same entities, offers, locations and relationships visible on the page. Keep identifiers and values aligned between markup and content. Do not add unsupported properties as if they were private instructions to the agent.

There is no demonstrated basis here for treating schema markup as a direct control surface for this ad format. Use structured data to improve consistency and machine readability, not as a guarantee that a business agent will select a particular answer. Likewise, do not relax robots rules or expose protected systems based on guesses about an unnamed crawler. Wait for explicit platform and security requirements before changing access controls.

Write operating rules, not just a brand voice prompt

An instruction such as be helpful, persuasive and on-brand does little when the agent must decide whether it has enough information to recommend a product. The useful instructions are decision rules.

Scope rule: define which questions the campaign agent can answer and which belong with a person, another workflow or a public page.
Information rule: map policies to canonical pages, catalog attributes to the feed and live-dependent claims to approved tools.
Clarification rule: identify the information that must be collected before a recommendation can be made.
Uncertainty rule: require the agent to say when a fact cannot be verified. It should not convert missing data into a plausible guess.
Recommendation rule: explain which user inputs may influence a recommendation and require the reasoning to be stated in plain language.
Lead-capture rule: answer what can be answered before requesting personal information, then explain why each requested detail is needed.
Escalation rule: name the conditions that require a human handoff and specify what useful context may be passed with the user’s knowledge.
Action rule: require confirmation before any tool performs a consequential write action, such as submitting a request or scheduling an appointment.

A strong missing-data rule is simple: if the recommendation depends on current availability and the approved live check cannot confirm it, the agent says that availability is unconfirmed and offers a safe next step. It does not infer availability from an old page, a general description or the absence of an error.

Design every campaign around one completed job

A customer request follows one connected path through a digital assistant, product selection, availability check and completed handoff.

The potential value of the format is not conversation for its own sake. A business agent could answer questions, recommend products, schedule appointments, troubleshoot issues or qualify leads before the user visits a conventional page.

Those are different jobs with different evidence, permissions and success conditions. A product recommendation may require customer preferences and feed attributes. An appointment workflow may require live availability and permission to write to a scheduling system. Lead qualification may require an agreed definition from sales and an approved form. Putting every job into one campaign makes failures harder to diagnose and outcomes harder to attribute.

For each campaign, complete this job card:

The user arrives asking: a single plain-language intent.
The session succeeds when: one verifiable customer or business outcome.
The agent must know: the minimum inputs needed to reach that outcome.
The agent may claim: statements supported by named business data.
The agent must check live: any value that could become stale before the user acts.
The agent must not do: actions or claims outside its permissions and evidence.
The fallback is: a useful page, form, support route or human handoff.

Then design the conversation in the same order a capable employee would resolve the task:

Continue the promise made in the ad. Do not make the user restate why they clicked.
Ask the smallest question that materially narrows the answer. Avoid turning the opening into a disguised intake form.
Answer the user’s question before pushing the conversion, unless the requested detail is genuinely required to produce the answer.
Explain the basis for a recommendation. The user should be able to see how their stated needs affected the result.
Present one primary next step and one fallback. A wall of undifferentiated links simply recreates a weak navigation page inside a chat.
Carry necessary context into the next step when the platform, user permission and privacy design allow it. Do not make the user repeat information without a reason.

Do not hardcode the strategy around an interface that has not been broadly seen. Exact ad appearance and prominence remain unclear. Prepare portable components instead: the opening explanation, required questions, answer rules, calls to action, failure messages and handoff logic. Those components can be adapted once the real placement and controls are documented.

Keep the website in the journey

Replacing the initial landing-page visit does not make the website obsolete. The apparent workflow uses the site to create the business profile, which makes the site part of the agent’s knowledge supply. It also remains a useful route for policy detail, accessible alternatives, complex forms, evidence the user wants to inspect and tasks the agent cannot complete.

For every agent outcome, maintain a page-based fallback that reaches the same destination without requiring the conversation. If linking is supported in the final experience, send users to the canonical page for detailed terms rather than a generic homepage. The better model is not agent versus website. It is agent for interpretation and guided action, with the website serving as governed evidence and a resilient fallback.

Measure solved intent and control the agent’s risk

A business team monitors a digital agent as routine actions proceed through safeguards and an uncertain request is routed to a human specialist.

Click-through rate cannot tell you whether the agent answered correctly, recommended an appropriate option or completed the promised action. Conversation count cannot tell you either. A long session may show useful consideration, repeated misunderstanding or a broken tool. A short session may be an immediate success.

Define an event chain before launch. Your measurement plan should attempt to connect the ad impression, conversation open, identified intent, meaningful progress, action start, confirmed completion, qualified outcome and downstream business result. The platform may not expose every event, so document which steps are directly observed and which are proxies.

Useful campaign measures include:

Intent identification rate: eligible sessions in which the agent obtains enough information to understand the requested job, divided by eligible sessions started.
Intent resolution rate: eligible sessions in which the defined customer job is resolved, divided by eligible sessions.
Verified action completion rate: actions confirmed by the relevant business system, divided by action starts.
Qualified outcome rate: outcomes accepted under the business’s existing qualification standard, divided by eligible sessions. The agent should not invent the qualification standard.
Handoff completion rate: sessions that successfully reach the offered fallback, divided by sessions that require a handoff.
Answer defect rate: reviewed sessions containing an unsupported, stale, contradictory or materially incomplete answer, divided by reviewed sessions.

Set the exact eligibility and resolution definitions before comparing campaigns. Otherwise, a change in what counts as a session can masquerade as improved performance. If the platform exposes campaign or session identifiers and your privacy design permits their use, carry them into the resulting lead, booking or order record so the downstream outcome can be reconciled.

When testing, change one decision variable at a time: the ad promise, opening question, answer structure, recommendation explanation, call to action or timing of lead capture. Keep the intended job stable. Comparing two agents that solve different tasks will not tell you which conversational design performed better.

Review conversations as quality data

Automated outcome tracking needs a human quality loop. Review conversations after instruction, content, feed or tool changes, and classify the failure rather than merely labeling the session bad.

Unsupported claim: the answer has no approved factual basis.
Stale claim: the agent used a durable page where a live check was required.
Premature recommendation: the agent recommended before collecting a necessary input.
Capture failure: the agent requested unnecessary information or asked before delivering value.
Tool failure: an unavailable or ambiguous result was presented as a confirmed value.
Handoff failure: the fallback was missing, irrelevant or forced the user to begin again.
Instruction conflict: two rules pushed the agent toward incompatible behavior.

Assign each defect to the layer that must be corrected. Fix a contradictory policy on the canonical page, not with another prompt exception. Fix changing availability in the live integration, not in website copy. Fix premature capture in the interaction rules, not by hiding a form field while leaving the same conversational pressure in place.

Treat conversation and tool access as customer data systems

Lead forms and transcripts can contain personal or commercially sensitive information. Before enabling capture, document what the agent requests, why it is needed, where it is stored, who can access it, how long it is retained, how deletion works and which notice or consent applies. Sensitive or regulated workflows need review from the appropriate legal, privacy and security specialists before launch.

Give connected tools the least access required for the campaign job. Prefer read-only access when the agent only needs to check a value. For tools that can write, require a clear user confirmation before submission and return a verifiable result afterward. Maintain a way to pause the campaign or disable the affected tool if answers or actions become unreliable.

Use a pass-fail launch gate

A generic readiness score can hide a serious defect behind several easy wins. Use a pass-fail gate based on the actual job the campaign promises to complete.

Truth test: ask the common questions, edge cases and deliberately conflicting questions. Confirm that every material answer can be traced to an approved page, feed or system.
Missing-information test: remove a required input and verify that the agent asks for it or declines to decide. It must not fill the gap with an assumption.
Freshness test: change a live-dependent value in its authoritative system and verify that the agent checks that system instead of repeating an older page value.
Tool-failure test: make the approved integration unavailable or return no usable result. The agent should state the limitation and offer the defined fallback.
Action test: complete the customer task, cancel before confirmation, retry a submission and follow an unavailable path. Confirm that the business system records only the intended action.
Handoff test: move from the agent to the fallback and verify that the user knows what will happen next, what information is transferred and whether anything must be repeated.
Data test: inspect every requested field, stored transcript and access permission. Remove anything that is not required for the declared task or an approved operational need.
Measurement test: reconcile a completed test journey from campaign entry through the business system. If the outcome cannot be observed, label the available metric as a proxy rather than calling it a conversion.

Do not launch while a material answer lacks an approved factual basis, a live-dependent claim can bypass its live check, a consequential action can occur without confirmation, or a failed workflow has no usable fallback. Those are structural defects. More traffic will only expose them to more people.

Choose one high-intent customer job and build its fact map, instruction set, test script and outcome definition now. When chatbot-native inventory becomes available to you, you will be evaluating a media opportunity with a governed business agent behind it, not improvising an automated representative after the campaign is already live.

References

Search Engine Land – OpenAI appears to be building chatbot-native ads that launch AI agents

July 31, 2026

AI Ad Campaign Controls: Automate Without Losing Control

When you switch an AI ad campaign from traffic to conversions, you are not handing the platform a complete strategy. You are giving it a score to maximize. If the conversion event, eligible audience, landing page, or budget rule is wrong, automation can repeat that mistake at scale.

The safest operating principle is simple: you keep control of business constraints, while the system optimizes inside them. That means deciding what counts as success, where ads may appear, which destinations are acceptable, how spend should behave, and which changes require human review before you enable more automation.

Key takeaways

Optimize for a conversion only after you have verified that the event fires correctly, represents real business value, and can be reconciled with your own records.
Treat an average daily budget as a pacing instruction, not a promise that every calendar day will spend the same amount.
Set geographic, brand, URL, product, and audience exclusions before launch. They define where the algorithm is allowed to search.
Keep generated assets, URL expansion, customer matching, and audience estimation under separate review because each creates a different failure mode.
Use bulk tools to deploy reviewed change sets. Do not let bulk creation turn an isolated configuration error into an account-wide problem.

Give the system one objective and explicit boundaries

The useful dividing line is not manual versus automated. It is judgment versus calculation. You should retain the decisions that require knowledge of margins, service areas, customer quality, brand policy, and operational capacity. The platform can handle the repeated calculation of which eligible opportunity appears most likely to produce the event you selected.

Control layer	You decide	The system may optimize	What fails when the control is weak
Outcome	Which event represents valuable demand	Which eligible clicks appear more likely to produce that event	Low-value actions accumulate while reported performance looks healthy
Economics	The spend ceiling and acceptable business return	Bid and delivery allocation within available platform settings	More conversions arrive without acceptable margin or lead quality
Eligibility	Geographies, audiences, brands, products, URLs, and inventory that are allowed	Which eligible opportunities receive delivery	Spend reaches people or destinations the business cannot serve
Creative	Approved claims, assets, product data, and disclosure requirements	Asset generation, selection, or combination where enabled	Ads become inconsistent with the offer or brand policy
Measurement	Which data is valid enough to influence optimization	Learning from the conversion feedback supplied	Tracking defects become bidding instructions

This distinction matters in ChatGPT Ads. Its Conversions objective supports optimized cost-per-click campaigns that favor clicks considered more likely to convert while continuing to charge on a CPC basis. That is conversion-oriented selection, not a guarantee of a conversion, acquisition cost, revenue level, or profit. You still need an economic test outside the bidding label.

Write the objective as a complete sentence before configuring the campaign: “Acquire this type of conversion, from these eligible customers, for this business outcome, within these spending and brand constraints.” If you cannot fill in every part, the campaign is not ready for broader automation.

Do not combine several business goals into one vague instruction. A purchase, qualified sales opportunity, app install, account registration, and page view do not carry equal value. If the platform sees all of them as equivalent success events, it can rationally pursue the easiest one rather than the one that matters most to you.

Fix the measurement loop before optimizing conversions

A glowing signal travels from an abstract ad to a landing page, through a verification checkpoint, and back to an optimization engine in a closed loop.

Conversion automation is a feedback loop. An ad receives a click, a user takes an action, measurement sends that action back, and the campaign looks for more traffic resembling the credited result. A broken signal therefore does more than damage a report. It teaches the system the wrong lesson.

Name the primary event. Choose the action closest to business value that you can measure reliably. Keep softer actions as diagnostic metrics unless you intentionally want the campaign to optimize for them.
Test the complete path. Use the same device and journey a customer would use, then confirm that the event appears in the ad platform and in the system your business treats as authoritative.
Check the event payload. Confirm the event name, value, currency where applicable, destination, and deduplication behavior. A successfully received event can still carry the wrong meaning.
Separate platform credit from business acceptance. For lead generation, compare attributed leads with qualified leads. For commerce, compare purchases with valid orders rather than treating the platform count as the final ledger.
Record the change point. When you alter an event definition, matching method, consent flow, or data source, annotate the date in your campaign log. Otherwise, a measurement change can be misread as a performance change.

ChatGPT Ads has added Automatic Advanced Matching under Tools > Conversions > Data Source. It uses hashed customer data to improve website conversion attribution. Hashing changes how the data is represented; it does not answer whether your organization had permission to collect and use it. Review the applicable consent, privacy, and data-governance requirements before enabling the feature. If that review is incomplete, keep it disabled while you validate ordinary conversion tracking.

For mobile campaigns, AppsFlyer and Adjust integrations can measure installs and in-app events. Use that distinction. An install can show acquisition volume, but a later registration, subscription, purchase, or other valuable in-app event may reveal whether that volume produced useful customers. Do not silently substitute the easier event when the business goal depends on the later one.

Before increasing a budget, ask four questions: Did the intended event fire? Did it fire only once for one action? Did the value arrive correctly? Did your business system accept the outcome as real? A “no” to any one of them is a measurement problem to fix, not a bidding problem to automate around.

Use budgets and exclusions as operating controls

Monitor the budget on the window the platform uses

A daily budget can look like a hard calendar-day cap even when the platform treats it as an average. ChatGPT Ads is shifting to average daily budgets evaluated over a rolling seven-day period, allowing daily spend to move while staying within the broader budget limits. It also paces daily budgets through the day.

That changes how you should investigate apparent variance. Do not declare a pacing failure merely because one day is above or below the displayed average. Review the rolling seven-day spend, the campaign’s total constraints, conversion volume, and your own financial cap together. A single-day screenshot is no longer enough to describe budget behavior.

Write down whether the platform field is a fixed cap, an average, or a target. The label determines what a normal day can look like.
Maintain an internal maximum exposure for the reporting window. Your accounting limit should not depend on a team member remembering how a platform interprets “daily.”
Alert on cumulative spend and material configuration changes, not only on one day’s variance.
Check whether a performance swing coincides with a budget edit, conversion edit, or exclusion edit before changing bids.
Do not raise the budget simply because pacing is slow early in the day. The pacing system is already distributing delivery, and an impulsive edit changes the instruction it is following.

A budget is also not a forecast. It describes the amount the system may use under its rules, not the number of valuable outcomes you will receive. Keep the decision to increase spend tied to reconciled conversion quality and acceptable economics.

Apply exclusions from hardest constraint to weakest signal

Exclusions are not merely cleanup settings. They define the search space. Configure the most defensible constraints first:

Operational impossibility: exclude locations you cannot serve, destinations that cannot fulfill the offer, and products that must not be advertised.
Brand and destination policy: restrict brands, landing pages, and URL expansion paths that could create an off-message or irrelevant journey.
Commercial fit: exclude audiences only when reliable performance or eligibility evidence supports the decision.
Estimated attributes: treat modeled classifications as weaker evidence than an explicit location, product, or URL rule.

ChatGPT Ads now provides campaign-level geographic exclusions. Use them when a location is genuinely ineligible, not as a substitute for diagnosing a regional landing-page, pricing, or measurement problem.

Destination controls deserve the same attention as audience controls. Google Ads Editor 2.13 supports AI Max in Shopping with automated text generation, URL expansion controls, brand lists, and URL exclusions. If URL expansion is enabled, review where the system is allowed to send traffic. A relevant query paired with the wrong page is still a failed campaign decision.

Be more cautious with household-income exclusions in Performance Max. The setting has been observed in a European campaign with brackets from the top 10% through the lower 50%, plus an Unknown segment, but the available evidence does not establish a universal rollout. Check whether the control actually exists in your account before designing a process around it.

If it is available, do not interpret Unknown as an income tier. It means the system has not assigned the user to one of the listed estimates. Excluding it can remove people whose commercial fit is simply unclassified. Compare measured business outcomes by segment before excluding a modeled group, document the rationale, and keep a clear route to reverse the change if reach or customer quality deteriorates.

Scale reviewed changes, not unchecked assumptions

A human analyst inspects a campaign module at a gated review station before approved copies move into a larger distribution network.

Bulk management reduces repetitive work, but it also enlarges the blast radius of a bad field. ChatGPT Ads now supports asynchronous bulk creation and updates for campaigns, ad groups, and ads through its Ads API. Because the work is asynchronous, submitting a job and confirming that every requested change completed are separate steps.

Google Ads Editor 2.13 similarly brings more AI campaign controls into an offline bulk workflow, including AI Max for Shopping, Customer Retention Goals in Performance Max, channel performance reporting, and AI-generated asset attestation controls. The practical gain is not just speed. You can review related settings as one change set before posting them.

Capture the starting state. Export or otherwise record the campaigns and fields you are about to change so you can identify exactly what moved.
Give the change set one purpose. Keep a budget revision separate from a conversion-goal migration, URL expansion change, or audience exclusion. If performance moves, you need to know which instruction caused it.
Validate the dangerous fields. Check campaign status, objective, conversion source, budget interpretation, geography, negative targeting, brands, URLs, product scope, generated-asset settings, and any required attestations.
Review the diff. Look for blank values, inherited defaults, duplicated entities, unintended status changes, and changes outside the intended campaign list.
Start with a limited subset. Use a small, representative group of campaigns when the feature or configuration is new to your team. Confirm behavior before applying the same pattern more widely.
Verify completion. For an asynchronous job, inspect the final job result and failed items. Then spot-check the resulting settings in the campaign interface.
Keep a rollback record. Store the prior value, new value, reason, approver, affected entities, and reversal method in the same campaign log.

After deployment, verify controls in a fixed order: eligibility first, destination second, measurement third, spend fourth, and reported outcomes last. This catches the cause before you react to the symptom. An ad that cannot serve, points to an unintended URL, or reports the wrong event should not be evaluated as a bidding-performance problem.

Your next move is to create a one-page control sheet for one live AI campaign. Record its primary conversion, authoritative business record, budget meaning, eligible geographies, audience exclusions, URL rules, brand rules, generated-asset permissions, owner, and rollback method. Resolve every blank field before adding another automated feature. That small document gives the system room to optimize without giving up the decisions only your business can make.

References

July 24, 2026

Category: Advertising

The ruling separates liability from remedy

Behavioral remedies make measurement more important

A practical plan for publishers, advertisers, and agencies

For publishers and revenue operations teams

For advertisers and agencies

Publish the decision accurately for search and AI systems

Key takeaways

References

Key takeaways

What Begin-to-Render changes in AdSense

Why the dashboard can look better and worse at once

Build a baseline that survives the February change

Turn the post-change gap into a defensible decision

Read the pattern before changing the site

Inspect the download-to-render interval

Optimize the outcome, not the retired counter

References

Treat the expansion as a change to the conversion path

Choose the bottleneck before you choose the feature

Use messaging only when a conversation can move the sale forward

Make travel personalization earn its relevance

Use AI video creation to build a testable asset system

Measure customer quality instead of celebrating new activity

Run a controlled rollout instead of a broad switch-on

Key takeaways

References

Platform targeting controls surfaces, not audiences

Maximize results needs a business constraint outside the algorithm

View-through conversions change the report, not necessarily demand

Keep three measurement questions separate

Use conversion integrations to improve signals, not inflate counts

Use a staged rollout that preserves a readable baseline

Key takeaways

References

What the European expansion actually gives advertisers

Paid placement and AI answer visibility are separate systems

Build the first test before self-service access arrives

Treat 31 European countries as a portfolio, not one market

Measure whether conversational intent becomes business value

Key takeaways

References

Treat 1,000 as a capacity ceiling, not a growth target

Build an account registry before scaling the portfolio

Use internal lifecycle states

Make linking a controlled handoff

Decide whether one agency structure still fits

Scale controls and exception handling with the account count

Key takeaways

References

The reporting flow is now a direct request-response path

Choose the endpoint by workload, not by which API is newer

Design interactive queries that remain useful under pressure

Start with the user’s question, not every available field

Treat 60 seconds as a ceiling, not a target

Do not equate synchronous retrieval with instant measurement

Put a stable adapter between CM360 and the interface

Separate no data, zero, slow, and failed

A low-risk rollout keeps the batch path intact

Campaign Manager 360 reporting API FAQ

Is reportData.query a streaming API?

Does “real-time reporting” mean every metric is instantly current?

Should an existing Reports service integration be migrated completely?

What is the best first use case?

References

ChatGPT now holds three parts of the commercial journey

Run four checks before allocating a ChatGPT Ads budget

Structure campaigns around decisions, not keyword lists

Becoming transactable starts outside ChatGPT

Measure each layer before combining attribution

Key takeaways

References

Key takeaways

The destination changes from a page to a decision

Build the context stack before writing the ad

Make the website safe to summarize

Write operating rules, not just a brand voice prompt

Design every campaign around one completed job

Keep the website in the journey

Measure solved intent and control the agent’s risk