CrushPress.AI

Tag: Ad Regulations

  • Google’s EU Ad-Tech Remedies: A Publisher and Buyer Playbook

    Google’s EU Ad-Tech Remedies: A Publisher and Buyer Playbook

    If you operate programmatic campaigns or publisher inventory in Europe, the wrong move is to treat Google’s EU ad-tech case as either business as usual or an imminent breakup. The practical question is narrower: which parts of your auction setup, measurement, and vendor dependencies could change if the proposed remedies are accepted?

    Google has submitted a compliance plan rather than agreeing to structural separation. That plan is not yet a settled operating model. You can still prepare without guessing the regulatory outcome: establish an auction baseline, locate single-vendor dependencies, and design tests that are easy to reverse.

    What Google has proposed – and what remains unresolved

    The proposal centers on two product-level remedies:

    • Publishers would be able to set different minimum prices for different bidders in Google Ad Manager.
    • Google’s advertising tools would work more readily with competing tools, giving publishers and advertisers more flexibility in how they assemble their ad-tech stacks.

    Those remedies target different kinds of control. Bidder-specific minimum prices change the rules governing participation in individual auctions. Greater interoperability changes how inventory, demand, workflows, and reporting can move across tool boundaries. Neither remedy, by itself, separates the ownership of Google’s integrated ad-tech operations.

    Google’s position is that technical changes can address the European Commission’s concerns without the disruption of a breakup. Critics question whether product adjustments can change the underlying power relationships while the integrated business remains intact. The Commission still has to decide whether the proposed changes are sufficient or whether a structural remedy should remain on the table.

    That uncertainty matters operationally. Do not plan as though bidder-level floors are already available in their final form, interoperability has a settled technical definition, or a breakup has been ordered. Treat each as a separate scenario with its own trigger.

    Bidder-specific price floors need controlled testing

    Two transparent auction test chambers use adjustable gates to evaluate identical streams of colored bid tokens under controlled conditions.

    A price floor is the minimum bid a publisher will accept for an impression. A bid below the applicable floor cannot win. If publishers can assign different floors to different bidders, a single pricing control becomes a bidder-level policy.

    That creates more control, but it does not guarantee more revenue. Raising one bidder’s floor can increase the price of the impressions that bidder wins while also reducing the number of eligible bids. The resulting loss of competition or fill can outweigh the higher price on the remaining wins. Average clearing price, viewed alone, can therefore make a poor change look successful.

    If the proposed control becomes available, use this test sequence:

    1. Preserve the existing state. Export or record current floors, bidder configuration, inventory groupings, and relevant auction settings before changing anything.
    2. Write one testable hypothesis. State which bidder, inventory class, format, and market the rule covers, as well as the behavior you expect to change. Avoid a stack-wide policy based only on a bidder’s brand or market reputation.
    3. Keep a comparable holdout. Leave similar inventory on the existing rule. Without a control, changes in demand, campaign mix, or seasonality can be mistaken for a floor effect.
    4. Measure the whole auction outcome. Track bid rate, win rate, fill, revenue per thousand ad requests, average clearing price, buyer concentration, and latency. The remedy is useful only if the combined result improves the publisher’s objective.
    5. Define stop conditions before launch. Decide which movement in fill, total revenue, latency, or demand diversity requires a rollback. Use thresholds based on your own established baseline rather than an unsupported industry benchmark.
    6. Record every change. Store the rule, affected inventory, start and end points, owner, rationale, and result in the same change log used for campaign and platform changes.

    Because bidder-specific rules treat demand sources differently, they can also create contractual and competition-law questions. Do not turn a pending regulatory proposal into a new pricing policy without checking existing agreements. Where a rule could create legal exposure in an EU market, have qualified competition counsel review it before it is scaled.

    What media buyers should monitor

    Advertisers will not control a publisher’s price floors, but they may see the effects in delivery. Segment reporting by exchange or supply path, publisher, market, device, and format. Watch for changes in win rate, eligible reach, delivery pace, cost, and the concentration of spend among supply paths.

    Do not diagnose a floor change from a higher CPM alone. A cost increase can also come from demand pressure, inventory mix, targeting, campaign edits, or a change in the route used to reach the impression. Compare cost with placement quality and campaign outcomes, then check whether the same inventory remains reachable through alternative authorized paths.

    Interoperability must be tested as a workflow, not a promise

    A modular workbench links publisher inventory, auction, buyer, delivery, and measurement stations through removable adapters and fallback routes.

    Greater interoperability between Google and competing ad-tech tools could expand choice for publishers and advertisers. Its actual value will depend on implementation details. A connector, export, or documented interface is not automatically equivalent to a complete working alternative.

    Turn the broad word interoperability into acceptance criteria your team can verify:

    • Scope: Identify the inventory, auction objects, campaign controls, and reports that can cross the boundary. List exclusions explicitly.
    • Direction: Determine whether the competing tool can only read information, can write or update settings, or can support a complete transaction workflow.
    • Field parity: Compare the fields, dimensions, controls, and levels of detail available through the integrated workflow with those available inside Google’s own tools.
    • Timing: Establish whether the exchange is real time, delayed, or batch-based. A delay that is harmless for reporting may make an auction or optimization workflow unusable.
    • Access: Document permissions, account relationships, authentication requirements, and any commercial conditions that determine who can use the connection.
    • Reconciliation: Verify whether requests, bids, impressions, costs, revenue, and adjustments can be reconciled across both systems.
    • Failure behavior: Test what happens when the connection times out, returns incomplete data, or becomes unavailable. A workable integration needs an observable error state and a safe fallback.

    Build a repeatable acceptance test before evaluating any implementation. Route a defined sample of eligible activity through the competing workflow. Confirm that inventory is available, bidder participation is visible, required controls work, reports reconcile, and failures can be detected. Keep the original route as a control until the replacement has passed those checks.

    This distinction prevents a common procurement error: counting the existence of an integration as evidence of effective choice. The operational question is not whether two products can connect. It is whether your team can complete the required workflow without losing material control, visibility, performance, or the ability to recover from a failure.

    Build one readiness file for every regulatory outcome

    You do not need to predict the Commission’s decision. You need a compact evidence package that lets you respond when a decision or documented product change creates an operational trigger.

    1. Map the stack. Record the ad server, exchanges, supply-side and demand-side platforms, buying interfaces, reporting systems, and the direction in which data or auction activity moves between them.
    2. Mark Google-dependent workflows. Identify where a Google product is required for setup, demand access, auction execution, optimization, reporting, or reconciliation. Distinguish a preference from a genuine technical dependency.
    3. Capture performance baselines. Preserve publisher auction metrics and buyer delivery metrics at the level needed to detect a change. Aggregated account totals can hide a material shift in one market, format, bidder, or supply path.
    4. Review portability and exit terms. Locate contract renewal dates, notice periods, data-export provisions, integration ownership, and any switching costs. Do not terminate or rewrite agreements merely because a remedy has been proposed.
    5. Assign decision owners. Name the person responsible for legal interpretation, platform configuration, measurement, vendor communication, and rollback. A regulatory update should not trigger an uncoordinated production change.

    Use three planning branches rather than one forecast:

    Possible outcomeImmediate actionWhat to avoid
    Product remedies are accepted substantially as proposedRead the final platform requirements, validate access, and run controlled floor or interoperability tests.Assuming the new controls improve yield or competition before measuring them.
    Stronger or structural remedies are requiredUpdate the dependency map, test continuity options, and review migration sequencing when operational terms are known.Rushing into an irreversible stack migration based on a headline rather than an enforceable plan.
    The proposal is changed, delayed, or remains under reviewKeep baselines, contracts, and vendor-path documentation current while continuing normal optimization.Freezing useful work while waiting for a regulatory outcome with no settled implementation.

    The event that should release a production change is not speculation about the case. It is a documented requirement, enforceable decision, contract change, or platform capability that your legal and technical owners have reviewed.

    Key takeaways for your next planning cycle

    • Google’s compliance plan is a proposal. The European Commission still has to determine whether product-level changes resolve its concerns.
    • Bidder-specific price floors affect auction participation as well as price. Evaluate net revenue, fill, competition, and latency instead of optimizing for clearing price alone.
    • Advertisers should monitor delivery by supply path and inventory segment because aggregate CPM and spend cannot identify the cause of an auction change.
    • Interoperability is useful only when the complete workflow preserves necessary access, controls, reporting, reconciliation, and failure recovery.
    • A dependency map, configuration record, performance baseline, and named rollback owner are useful under every regulatory scenario.

    Your most useful next step is a one-page readiness file. Put your current floors, bidder and vendor paths, baseline metrics, contract checkpoints, decision owners, and release triggers in one place. When the Commission decides or the products change, you will be able to test the actual remedy against evidence instead of rebuilding your operating picture under pressure.

    References

  • Google Ads Image Carousels and Phone Number Fraud Controls

    Google Ads Image Carousels and Phone Number Fraud Controls

    Google Ads now puts two very different jobs on the same campaign manager’s desk. The mobile Images tab can carry horizontally scrollable ads built from images, headlines and links, creating another route into visual discovery. But a phone number associated with fraud or earlier policy violations can cause an ad to be disapproved under Destination requirements. One change expands your reach; the other can shut it down.

    If you manage paid search, do not leave compliance until after the creative is ready. Treat the query, image, headline, destination and phone number as one chain. Your practical goal is not merely to activate a new format. You need to know that the ad is relevant, the contact identity is defensible and a delivery problem will not be mistaken for a performance problem.

    Key takeaways

    • Use an image carousel when the visual answers a real customer question. A decorative image may fill the format without helping someone choose.
    • AI-driven matching can connect visuals with searches beyond traditional shopping categories, but it cannot make an unclear offer useful.
    • Manage every advertised phone number as an identity asset. Its history can matter even when your current ad and landing page look compliant.
    • Confirm approval and delivery before judging performance. A disapproved ad tells you nothing about whether its creative would have worked.
    • When possible, do not change the phone number and the main creative idea in the same test. Staging those changes makes the cause of a failure much easier to identify.

    Design the carousel around a visual decision

    A designer arranges five coordinated image cards in a horizontal sequence beside a smartphone on a dark worktable.

    The Images tab serves people who are already exploring through visuals. The carousel format can put your brand in front of someone while they compare and investigate options, before their behavior narrows to a conventional text-ad click. That makes the placement useful for discovery, but only when the image carries information.

    Google’s matching technology can align an ad’s visuals with a search and can surface the format outside retail shopping, including categories such as law and insurance. That expanded availability is not proof that every advertiser needs an image campaign. A generic courthouse, handshake or office photo may signal a category, but it rarely explains why the searcher should choose one result over another.

    Write a four-part creative brief

    Before anyone selects an image, require the brief to answer four questions:

    1. What is the searcher trying to see? Name the visual question, not merely the keyword. The person may need to recognize a product, compare alternatives, understand a process or verify a visible attribute.
    2. What does the image resolve? State what someone should understand before reading the headline. If the answer is only that your company exists, the asset is probably too generic.
    3. What context must the headline add? Use the headline for the qualification, distinction or next step that the visual cannot communicate reliably. Repeating the image wastes limited attention.
    4. Does the destination continue the same thought? The linked page should immediately confirm the subject and promise shown in the carousel. A visually relevant ad that opens an unrelated or overly broad page creates a broken handoff.

    Keep those answers together in the campaign record. If AI matching places the visual beside a relevant search, you can then inspect the whole path rather than debating the image in isolation.

    Test a decision, not a decoration

    Organize creative variants around different reasons a person might choose. One version might demonstrate the offering itself; another might make a comparison easier; a third might explain a process visually. Changing only the crop, background color or ornamental treatment may produce a different-looking ad without testing a meaningful customer question.

    • Give each variant a one-sentence hypothesis: what the image should help the searcher understand or decide.
    • Keep the destination aligned with that hypothesis. Do not send every visual idea to the same generic page merely because the URL is convenient.
    • Change one major idea at a time when learning matters. If the subject, headline, destination and contact method all change together, the result will be difficult to interpret.
    • Define the intended action before launch, such as a qualified visit, call or lead. Increased visual exposure is not automatically business value.

    AI matching is distribution logic, not your creative strategy. Google can decide that a visual corresponds to a search; you still have to decide whether the match expresses the right promise and attracts the right person.

    Audit the phone number as a campaign identity

    A magnifying lens examines a telephone handset token in a connected campaign chain with clean green and tangled red pathways.

    Google set December 10, 2025 as the effective date for rejecting phone numbers tied to fraud or previous policy violations, with enforcement scheduled to increase over roughly the following eight weeks. That ramp described how enforcement would be introduced; it was not a guaranteed grace period for every account. Your campaign controls should already treat the rule as a baseline.

    Do not misclassify this as click-fraud prevention. The change sits under Google’s Destination requirements and concerns the reputation and policy history associated with a phone number. It is not a measurement of invalid traffic. A clean-looking ad or landing page therefore does not neutralize a flagged contact number.

    A phone number is more than a line of copy. It connects the ad to the identity, routing and history of the business presented to the user. Treat it like a governed asset by maintaining a simple registry for every number placed in an ad or ad asset. If the same number appears on the destination, record that placement as well so the complete contact path remains traceable.

    Registry fieldWhat to recordDecision it supports
    Exact phone numberThe complete number as it appears in the campaignPrevents formatting variants or duplicates from escaping review
    Campaign placementEvery ad, asset or destination where your team uses itShows the likely scope if the number is rejected
    Owner and providerThe business owner, vendor or partner responsible for the numberIdentifies who can investigate its use and history
    Provenance checkWhether the number is dedicated, shared or reassigned, plus what the provider can confirm about prior useExposes uncertainty before the number reaches a campaign
    Routing checkThe business, team or call flow that answers the numberConfirms that the contact experience matches the advertiser represented
    Review stateVerified, pending investigation or rejected, with the review dateStops an old assumption from being treated as a current check

    Pay particular attention to numbers supplied by agencies, tracking vendors, franchises, call centers or other partners. The fact that your team did not create a number’s history does not remove the operational risk when Google evaluates its association with fraud or past policy breaches. Ask who controls it, whether it has been shared or reassigned, and who can investigate a flag. Those answers do not guarantee Google’s approval, but they give you a responsible escalation path.

    Do not respond to uncertainty by cycling through unverified numbers until one is accepted. That destroys traceability and preserves the same control gap. A replacement should have a known owner, correct routing and documented provenance before it enters another campaign.

    Separate policy eligibility from creative performance

    A campaign can fail before the audience ever evaluates it. If you treat that failure as weak demand, you may discard a sound visual idea. The safer release sequence has two stages: establish eligibility first, then measure performance.

    Stage one: prove that the campaign can serve

    1. Freeze the proposed package: image, headline, destination and any advertised phone number. Give each item a clear owner.
    2. Confirm that the visual answers the intended search task and that the linked page continues the same promise.
    3. Check every included phone number against your registry. Resolve unknown ownership, routing or provider history before launch.
    4. After submission, verify approval and delivery status before increasing exposure or interpreting performance.
    5. If a phone-related disapproval appears, record the exact notice, number and affected placements. Stop adding that number to new ads while it is being investigated.
    6. Verify the number with its owner or provider, then follow the remediation route supplied in the disapproval notice and Google’s Help Center. Replace the number only with another contact that has passed your ownership, routing and provenance checks.
    7. Once the issue is resolved, review other campaigns that use the same number. Fixing a single rejected ad does not remove the shared dependency elsewhere.

    Avoid rewriting unrelated headlines or swapping landing pages while investigating a phone-specific rejection unless the notice identifies those elements too. Unrelated changes create more possible causes and make the final resolution harder to document.

    Stage two: prove that the creative earns its place

    Once the campaign is eligible to serve, evaluate the visual hypothesis against the action you defined. Keep the approved phone number and destination stable while comparing major image ideas whenever possible. This separates three conditions that are often blurred together:

    • Low or interrupted delivery: first check eligibility and policy status. There may not be enough audience exposure to judge the creative.
    • Exposure without useful engagement: inspect whether the image answers a meaningful question or only signals the category.
    • Engagement without the intended action: inspect the handoff among the image, headline, destination and contact path. The ad may attract attention while promising something the next step does not confirm.

    An approved ad can still be irrelevant, and an AI-matched visual can still be weak. A disapproved ad, however, cannot prove or disprove the creative idea. Keeping those judgments separate prevents you from abandoning useful visual direction because a contact asset blocked delivery, or scaling an attractive ad while its phone-number governance remains unresolved.

    Before your next image-carousel test, require two approvals. The creative owner should confirm the image, headline and destination in one sentence. The operational owner should identify the exact phone number, its controller and its review state just as quickly. If either owner cannot answer, the campaign is not ready to scale.

    References