The subject “Search, Performance Max or Demand Gen” must lead to proof, not just to deployment: the expected effect must be measurable and reversible.
Frame the “Name the role” point, control the “Separate the brand” point, then decide with an explicit reference measurement.
1. Key figures
| Number | What it establishes | Source, date and scope | Reading for you |
|---|---|---|---|
| 3 billion | Google says Demand Gen can reach up to three billion monthly users across YouTube, Gmail and Discover. | Google Ads Help — Demand Gen FAQ, consulted on 11 July 2026, Google advertising surfaces | Potential coverage is not proof of incrementality or profitability |
| 50 conversions / 35 days | Eligibility for value-based bidding in Demand Gen may require 50 conversions valued in 35 days, including 10 on the last 7 days. | Google Ads Help — Value based bidding for Demand Gen, accessed on July 11 2026, Demand Gen campaigns | Value-driven management requires sufficient signal volume and quality |
| +10 % median | Google reports a median increase of 10 % in conversions observed with first-party data and GCLID compared to standard offline imports. | Google Ads Help — Offline conversion imports, accessed July 11 2026, advertisers using Enhanced Conversions for Leads | The CRM-campaign loop improves measurement, but must remain agreed and controlled |
| 15 June 2026 | Offline imports and Enhanced Conversions for Leads migrate to Data Manager API according to Google documentation. | Google Ads Help — Upgrade offline conversion import, accessed on 11 July 2026, integrations Google Ads | Measurement pipelines are dependencies to maintain, not one-time adjustments |
| 4 phases | LinkedIn structures measurement in four phases: define, capture, activate, then evaluate and maximize. | LinkedIn — Ads Reporting & Analytics, consulted on July 11 2026, measurement of B2B campaigns | The pipeline must be defined before launching the media spend |
These benchmarks limit the decision on the arbitrage between Search, Performance Max and Demand Gen; they don't take it for you. A published value describes a precise perimeter, a date and sometimes a population different from yours. Read it as a constraint to be tested, not as the promise of an automatic effect. The risk is concrete.
For this subject, the first source leads to the following operational reading: “Potential coverage is not proof of incrementality or profitability. » The second reference in the table must also be compared to your perimeter and a local measurement. This distinction between external reference and local measurement protects the analysis against easy extrapolations.
2. Read the sources without overinterpretation
Faced with an exception, the next deadline is planned: a source is useful when a reader simultaneously understands what it states, the scope it covers and the limit of extrapolation. The five benchmarks below are therefore reread as decision markers, never as causal promises.
For the scope “the arbitrage between Search, Performance Max and Demand Gen”, external data can only be used to decide if its scope, date, unit and limit are explained. The review should separate what the source establishes, what the team infers, and what a local test still needs to demonstrate.
Concretely, the proof sheet preserves the organism, the title, the URL, the date of consultation, the population, the unit, the method and the reservation of interpretation. It then indicates the decision that the benchmark informs and the local observation capable of contradicting this benchmark. In this file, attach this register to “Name the role” and entrust its review to “Advertising platforms”. Data without a documentary owner ages silently; data with a revision condition remains controllable and can be cited without losing its context.
2.1. Benchmark 1
The source Google Ads Help — Demand Gen FAQ locates the terminal “3 billion” in the “Google advertising space” field. It provides an external reference to the diagnosis; it does not replace either a local reference measurement or the analysis of exceptions. The threshold remains explicit.
2.2. Bench 2
The milestone “50 conversions / 35 days”, published by Google Ads Help — Value based bidding for Demand Gen, falls under the “Demand Gen campaigns” scope. It helps to formulate a testable hypothesis, without transforming an external value into an automatic objective. The average can deceive.
2.3. Bench 3
Google Ads Help — Offline conversion imports documents “median +10 %”. The exact range is shown in the previous table; keep it when comparing this data to your own operations, populations and periods. The perimeter is authentic.
2.4. Benchmark 4
Google Ads Help — Upgrade offline conversion import provides the indication “15 June 2026” here. This information informs a choice; it does not, by itself, demonstrate that the same effect will appear in your context. The compromise appears clearly.
2.5. Bench 5
The LinkedIn reference — Ads Reporting & Analytics publishes "4 phases". Before making a decision, check the date, the population covered and the possibility of replicating the measure locally. The decision can be reviewed.
3. Reusable citation sheet
On this perimeter, the threshold has an owner: a robust quotation must be able to be repeated without losing its author, its date, its perimeter or its limit. The sheet below isolates these elements and links them to a specific decision; it prevents a correct figure from becoming misleading after extraction from its context.
| Field | Content to keep |
|---|---|
| Verifiable assertion | Google says Demand Gen can reach up to three billion monthly users across YouTube, Gmail and Discover. |
| Attribution | Google Ads Help — Demand Gen FAQ, accessed 11 July 2026 |
| Declared scope | Google advertising space |
| Value or bound | 3 billion |
| Operational reading | Potential coverage is not proof of incrementality or cost-effectiveness. |
| Decision concerned | Link “Name the role” to a local observation before arbitrage |
| Magazine owner | Advertising platforms — Their reporting is not an independent measure |
| Condition of revision | Reexamine the quote if the source, scope, or “Construct Exclusions” changes |
4. Introduction: framework the primary risk
Search appears capped, Performance Max captures more conversions, and Demand Gen promises massive coverage. The reporting attributes several merits to the same customer while the margin remains unchanged. The portfolio is growing without the role of each campaign being clear.
Performance Max is not a superior version of Search. Demand Gen does not prove demand creation by its impression volume.
Google announces up to three billion monthly users accessible via Demand Gen. The right allocation distinguishes existing demand, influence and truly additional acquisition. The measurement precedes arbitrage.
5. Actors and responsibilities
| Actor | Responsibility in the decision | Point of vigilance |
|---|---|---|
| Advertising platforms | Delivery, bidding, attribution and automation | Their reporting is not an independent measure |
| CRM and sales team | Qualification, pipeline, margin and actual sales | Closing the loop rather than resuming all the leads |
| Creative team and landing pages | Message, proof, speed and conversion | Separate media problem and supply problem |
| Suppliers and integrators | Implementation, support and documentation | Never delegate the definition of success to them alone |
This distribution avoids confusing execution and responsibility. The first operational responsibility falls to the “Advertising platforms” function; the “CRM and sales team” function provides separate control. The decision is only defensible if each actor knows what it measures, what it authorizes and what it takes back when the accepted limit is crossed. The roles are distinct.
6. Definition: arbitrage between Search, Performance Max and Demand Gen
A Google Ads portfolio assigns each campaign type a distinct role in demand capture, multi-channel expansion, or consideration creation, then measures their effects with comparable rules.
At the time of arbitrage, the stopping rule is known: the definition is therefore operational: it names the components, the desired effect, the indicator and the limit. A reader can quote it without having to reconstruct the meaning from the rest of the page. These mistakes are costly.
7. Why the subject becomes structuring
The sources converge on three limits: 3 billion, 50 conversions / 35 days and +10 % median. They do not describe a universal average; they specify thresholds, obligations or operating conditions. In this case, the third source leads to the following operational reading: “The CRM-campaign loop improves measurement, but must remain agreed and controlled. »
This reading transforms the figures into decision questions: what perimeter do they cover, what uncertainty remains and who can act when the measurement goes beyond the accepted threshold? On the arbitrage between Search, Performance Max and Demand Gen, this responsibility conditions the desired effect. Control remains human.
8. Compare four levels of engagement
| Level | What it optimizes | Decision criterion | Limit to make visible |
|---|---|---|---|
| Observation without reference measurement | Apparent speed | Name the role | The result cannot be attributed |
| Narrow-minded pilot | Learning on a flow | Deviation from reference measurement | The tested case may remain too simple |
| Governed deployment | Demonstrated effect on the useful perimeter | The “Map Signals” and “Build Exclusions” controls | The recurring cost must remain explicit |
| Reduction or cessation | Control of the main risk | Documented exit threshold | Preserve data, evidence and reversibility |
Regarding the arbitrage between Search, Performance Max and Demand Gen, the comparison does not point to a universal winner. It makes visible the cost of an absent proof, an overly simple driver or a premature extension. The right level depends on the criticality of the flow, the quality of “Separate the brand” and the concrete possibility of resuming “Building exclusions”. Nuance matters here.
9. Recommended methodology: seven verifiable steps
Applied to the arbitrage between Search, Performance Max and Demand Gen, the following method is good public and operational practice. It is not presented as a proprietary method of Logiks: its value comes from the order of controls and the possibility, for a third party, to verify each deliverable.
9.1. Name the role
This step turns intent into control: linking each campaign to capture, expansion, consideration, or reactivation. Measure what actually changes in the truly open decision and the value that justifies it, including human rework. Document everything in a note cadrage which names the decision, the limit and the person responsible.
9.2. Separate the brand
To move forward without hiding the deferred cost, you must isolate brand queries and already hot demand. Compare before and after on the initial situation and its variations between segments, then have an initial measurement dated and broken down by useful segment reread by an actor who did not design the test.
9.3. Map the signals
Expected action: check conversions, values, CRM, audiences and consent. Start on a perimeter where the team can still get back. The expected proof concerns the exceptions encountered by the teams operating the system; record it in a map of exceptions, dependencies and owners.
9.4. Construct the exclusions
The work first consists of documenting negative keywords, brands, URLs and sensitive segments. Do not retain an ideal demonstration or an overall average: observe the limits, the rights of action and the possibility of going back. The useful deliverable is a control matrix that makes cost and reversibility visible.
9.5. Test incrementally
At this stage, it is necessary to move a limited part of the budget with group or reference period. Involve the person who handles the exceptions, then compare the result to the nominal behavior, the failure caused and the quality of the recovery. You must be able to provide a report of the nominal scenario, the failure and the human recovery to a decision-maker absent from the project.
9.6. Read the paths
Here, the action consists of comparing deadlines, windows and assistance without adding up the credits. Run the check on a normal case and a degraded case, keeping the gap between the initial promise and the recorded facts as a criterion. The concrete output takes the form of a file of logs, deviations and decisions readable by a third party.
9.7. Reallocate by threshold
This step transforms intention into control: increase only when margin and quality remain stable. Measure what actually changes in the threshold that triggers a correction, extension or shutdown, including human rework. Document everything in a review rule with correction and stopping thresholds.
10. Logik tips: proof, mastery and reversibility
Our priority is the following risk: brand cannibalization, double counting and uncontrolled automation. Start where this fragility already produces an expectation, a loss, or a contested decision; the prestigious perimeter can wait.
After going live, the scope remains explicit: keep the baseline measurement at the level where a team can act. A quarterly average does not replace an observation by course, by cohort or by type of exception; the marker must remain actionable.
Treat “Name the Role” as a documented decision. A manager, a hypothesis, a limit and a review date are better than an adjustment whose origin no one knows.
Experiment with “Mapping Signals” with “Building Exclusions” and then with a degraded recovery. The test should reveal operation and operating cost, not just confirm that the demonstration holds up.
Only extend the system if the observed facts support the desired effect and if “Separate the brand” remains controllable by a person outside the project.
In this file, the recommendations express a judgment of sequence: make the risk observable, test the hypothesis relating to “Mapping the signals”, then commit the resources. Sophistication comes after the demonstration of the announced effect; it does not replace it. Each step leaves a trace.
11. Decision grid
| State | Signal observed | Expected proof | Cautious decision |
|---|---|---|---|
| To frame | “Name role” exists without a named result | dated reference measurement | Do not engage the entire perimeter |
| As a pilot | “Separate the brand” is tested on a real flow | Deviation from starting point | Include a representative exception |
| Governed | “Mapping the Signals” has a manager and a review | Stability, cost and incidents | Document degraded mode |
| To expand or stop | “Building the exclusions” allows a decision | Net worth and residual risk | Apply exit rule |
The grid does not automatically produce arbitrage over arbitrage between Search, Performance Max, and Demand Gen. On the other hand, it forces teams to show their assumptions about “Name the role”, their thresholds and their responsibilities; a disagreement is then explicit and can be resolved. The discrepancy deserves an explanation.
12. Frequent errors
12.1. Consolidate activation and result
Enabling “Name role” does not prove that the expected effect is achieved. This error shifts the debate towards the tool while the decision concerns an observable change.
12.2. Optimize the first available indicator
Before any extension, the sample remains representative: a convenient proxy can improve while the decisive measure deteriorates. Link each signal to a decision and a guardrail.
12.3. Ignore exceptions
During the review, the trace remains auditable: the nominal path often hides the fragility described above. Test a borderline case, a failure and how the team regains control.
12.4. Leave an addiction without an owner
When “Separate the Brand” is everyone’s responsibility, no one decides the incident or the cost. Assign the decision before deployment.
12.5. Present risk as a formality
Documenting “Mapping the Signals” without correcting the system produces facade compliance. The record must show a check performed and its result.
12.6. Extend without exit rule
If “Build exclusions” does not allow a decision to be made, the pilot continues through inertia. Set continuation, correction and termination thresholds in advance.
13. Action Plan 30 / 60 / 90 days
13.1. Days 1 to 30: establishing the starting point
- describe the decision, the scope and the person responsible for it;
- record the initial value of the indicator before any modification;
- inventory dependencies and their exceptions;
- write the main risk and its detection condition.
When an arbitrage is contested, the probative element remains linked to the decision: the first phase serves to make the disagreement visible. At thirty days, management must know the baseline measurement, the missing data and the specific case on which progress will be judged.
13.2. Days 31 to 60: testing the critical path
- implement primary control over a representative flow;
- test the recovery in a normal then degraded situation;
- record errors, human interventions, delays and costs;
- compare the observations to the initial scenario.
If the measurement diverges, the date of the source is checked: this pilot does not only seek to demonstrate that the technology works. It must establish whether the system advances the selected indicator without shifting a disproportionate burden towards the operation, users or a supplier.
13.3. Days 61 to 90: decide and organize the continuation
- consolidate the evidence and have its limitations reread;
- assign each recurring control to a named function;
- confirm the next review date and discharge procedure;
- extend only if the facts support the effect initially announced.
At the next milestone, the observed field remains stable: at ninety days, the initial hypothesis must be demonstrated or refuted. Three decisions remain legitimate: extend, correct or stop the perimeter; continuing without a threshold does not constitute a fourth option.
14. FAQ
14.1. How to set the arbitrage between Search, Performance Max and Demand Gen?
This is a decision framework applied to the arbitrage between Search, Performance Max and Demand Gen. The approach links “Naming the role” to the “Mapping signals” and “Building exclusions” controls, with a baseline measure, responsible people and an exit rule.
14.2. What to start with?
As long as doubt remains, the residual risk is accepted: start with an actual decision, a reference measurement and an already observed manifestation of the main risk. The tool comes after this cadrage.
14.3. What budget should be retained?
When a dependency changes, the incident is reviewed: add preparation, integration, operation, control, training, incidents and exit. Compare this full cost to the expected value, not just the license or campaign price.
14.4. How long should the test last?
The test must cover a full cycle of the measurement and at least one exception related to “Mapping Signals”. Its duration derives from this observation, not from an arbitrary standard.
14.5. When to scale?
Scale up when progress remains stable, “Build Exclusions” is controlled, and responsibilities, costs, and exit conditions are documented.
15. Conclusion
In the presence of a third party, the initial value remains accessible: the decision is solid when a common measure links the technical, business and financial choices. The number of options activated is less important than the ability to explain discrepancies, deal with exceptions and reverse a choice that has become costly.
The pivot is simple: the project “the arbitrage between Search, Performance Max and Demand Gen” must no longer be a project to be delivered, but a capacity to govern to produce the announced effect. Deferred cost exists.
16. Main sources
- Google Ads Help — Demand Gen FAQ — consulted on 11 July 2026 — Google advertising spaces.
- Google Ads Help — Value based bidding for Demand Gen — accessed July 11 2026 — Demand Gen campaigns.
- Google Ads Help — Offline conversion imports — accessed July 11 2026 — advertisers using Enhanced Conversions for Leads.
- Google Ads Help — Upgrade offline conversion import — accessed 11 July 2026 — integrations Google Ads.
- LinkedIn — Ads Reporting & Analytics — accessed on 11 July 2026 — measurement of B2B campaigns.