Tag: B2B Marketing

  • How to Manage Ad Targeting and API Updates Without Chaos

    How to Manage Ad Targeting and API Updates Without Chaos

    An advertising-platform release can create two very different jobs. A targeting feature asks whether you can reach a better audience. An API change asks whether your reporting, security checks, stored data, and automation will continue to work. Treat both as features to try, and you can spend budget before measurement is ready or discover a broken data dependency after the damage is done.

    That distinction matters now because Microsoft Advertising has extended LinkedIn profile targeting to connected TV campaigns, while Google Ads API v24.1 adds reporting, creative-control, experiment, authentication, and retention-related changes. You need a release process that protects existing operations first, validates measurement second, and tests growth opportunities third.

    Classify each change before scheduling the work

    The loudest feature should not automatically become the first task. Rank changes by what happens if you ignore them. A new audience may represent an opportunity, but a data-retention limit can permanently narrow the history available to your reporting system.

    Use five practical classes:

    • Continuity changes: retention limits, unsupported requests, client compatibility, and anything else that can interrupt a production workflow.
    • Measurement changes: new segments or metrics that alter how performance can be divided and interpreted.
    • Security changes: fields that help you identify account protections or authentication gaps.
    • Control changes: options that affect how an approved creative is uploaded, transformed, or displayed.
    • Growth changes: new audiences, inventory, campaign types, and experiment surfaces.

    Work through them in that order unless a documented dependency changes the sequence. Continuity comes first because lost history or a failed reporting job can affect every campaign. Measurement comes before growth because you cannot judge a new audience reliably until you know what the reporting can and cannot observe.

    For the current updates, the 37-month Google Ads data-retention boundary belongs in the continuity queue. The mobile-device platform segment belongs in measurement. The passkey field belongs in security. Demand Gen image control belongs in control. LinkedIn-based CTV targeting belongs in growth. That classification gives your team an actionable backlog rather than an undifferentiated list of announcements.

    Test professional CTV targeting as an audience hypothesis

    A media planner runs a small connected TV audience test by selecting one professional audience cluster for comparison.

    Microsoft’s CTV expansion lets advertisers use professional attributes such as industry, job function, company category, and professional identity signals. For a B2B advertiser, that can connect broad streaming exposure with a more relevant professional audience.

    It does not turn a professional attribute into buying intent. A viewer’s job function may indicate fit, but it does not prove that the viewer is researching a purchase. Treat the targeting as a testable audience hypothesis: people matching this professional profile should respond differently from a suitable comparison audience when the message and measurement remain consistent.

    Build the first test in this order:

    1. Choose one buying group. Describe it with the smallest useful combination of industry, function, and company characteristics. If you begin with a heavily stacked audience, you will not know which condition created the result or restricted delivery.
    2. Write down what the attributes mean. Record the exact audience definition, intended buying role, exclusions, eligible markets, and date of activation. Platform labels are not a substitute for an internal audience specification.
    3. Hold avoidable variables steady. Use comparable creative, offers, geography, inventory conditions, and evaluation windows across the audience cells. Otherwise, a creative or delivery difference can masquerade as a targeting effect.
    4. Select an observable outcome before launch. Do not let an easy-to-read delivery metric become the business objective by default. Use the conversion, lift, or qualified-response signal that your measurement stack can support consistently.
    5. Set a decision rule. Define what evidence would justify expanding, revising, or stopping the audience. Making that decision after seeing the result invites selective interpretation.
    6. Review privacy and compliance. Confirm that the proposed professional segmentation, creative, data handling, and market coverage fit your organization’s requirements before the audience begins receiving ads.

    Measurement deserves extra attention. CTV has traditionally operated as a brand-oriented channel with less direct attribution than search or shopping. Professional targeting can improve audience relevance, but it does not automatically resolve that measurement gap. Keep exposure quality, downstream response, and attribution confidence separate in your readout.

    Several implementation details remain uncertain, including market availability, segmentation granularity, measurement capabilities, and privacy considerations. Verify those items in the account and market you intend to use. Do not build a forecast around targeting combinations or reporting dimensions you have not confirmed are available.

    Turn Google Ads API v24.1 into an engineering checklist

    An engineer checks reporting, security, creative, experiment, automation, and data modules before an API workflow reaches production.

    API adoption is not complete when a client library installs successfully. The real work sits downstream: query builders, schemas, dashboards, experiment records, asset workflows, authentication reports, exception handling, and historical storage.

    Start by mapping each v24.1 capability to the system it can affect:

    The retention change deserves a separate migration task. Search your query code, scheduled exports, dashboards, year-over-year reports, model-training inputs, and audit workflows for requests that can reach beyond 37 months. Then verify what history is still queryable and preserve future data at the granularity your business actually needs.

    An archive is useful only if you can interpret and restore it. Store the account identifier, reporting period, timezone, currency context, field definitions, extraction timestamp, and relevant attribution or configuration metadata alongside the metrics. Test a restore into a clean table before relying on the archive. A successful export file is not proof of a recoverable reporting history.

    Update error handling as well. DateRangeError.REQUESTED_DATE_GRANULARITY_NOT_SUPPORTED identifies an unsupported date-range request. Treat a confirmed policy boundary as a query-design problem, not a transient failure to retry indefinitely. Logging the requested dates and granularity will make the remediation far faster.

    Put targeting and API work through one change-control loop

    Marketing and engineering do not need separate definitions of a successful platform update. They need one shared record that distinguishes a business hypothesis from a technical dependency.

    Change typeQuestion to answer firstEvidence requiredSafe response if it fails
    New audienceCan you isolate the audience effect?Documented audience cells, stable measurement, and a predefined decision rulePause the new segment without disturbing the existing campaign structure
    Reporting dimensionCan every downstream system accept and interpret it?Schema validation and reconciled totals against a baselineRemove the new dimension from production queries while preserving the test
    Creative-control fieldDoes the delivered asset match the approved intent?Asset-level quality review and recorded campaign mappingReturn to the previously approved asset path
    Retention boundaryCan analysis continue after platform history expires?External archive plus a successful restore testNo platform rollback exists; repair the archive and shorten unsupported queries
    Authentication-status fieldWho acts when an account lacks the expected protection?Verified field ingestion, ownership, and a remediation queueKeep the current authentication flow while correcting the reporting or rollout process

    Every change ticket should name an owner, impacted accounts, affected queries or campaigns, the validation evidence, a rollback path, and the date when someone will make a keep-or-revert decision. If no one owns that decision, the change is not ready for production.

    Keep the Microsoft audience test and Google API migration separate even if they appear in the same planning cycle. One measures whether professional targeting improves an advertising outcome. The other protects and expands the systems used to report that outcome. Combining them creates two moving parts and a result that is harder to diagnose.

    Key takeaways

    • Prioritize continuity and data-retention work before testing new reach.
    • Treat professional CTV attributes as proxies for audience fit, not proof of current purchase intent.
    • Confirm Microsoft CTV availability, measurement, segmentation, and compliance conditions in the actual account and market before forecasting results.
    • Test every new Google Ads API field through queries, schemas, storage, and dashboards before promoting it to production.
    • Maintain an external, restorable archive if your reporting requires more than 37 months of Google Ads history.
    • Give every rollout a named owner, acceptance evidence, rollback path, and decision date.

    At your next platform-change review, create two queues: one for operational deadlines and one for controlled growth tests. Clear the dependencies that can damage data or reporting, validate the measurement layer, and then give the new audience or creative capability a fair test.

    References

  • How to Measure AI Discovery Traffic for B2B Pipeline Growth

    How to Measure AI Discovery Traffic for B2B Pipeline Growth

    You can see buyers using ChatGPT, Claude and Gemini to research vendors, yet your pipeline report may still reduce the result to organic, referral or direct traffic. If you cannot connect that activity to qualified demand, you cannot tell whether AI discovery deserves more investment or merely produces interesting charts.

    The practical answer is not a single AI metric. Build an evidence chain from visibility, to an identifiable site visit, to an onsite action, to an opportunity. Google Analytics can now cover the middle of that chain more cleanly. Your CRM, LinkedIn activity and measurement rules must cover the rest.

    Measure three layers instead of one AI traffic number

    Three connected translucent layers depict AI visibility signals, a website session and a conversion path leading to business account and opportunity nodes.

    AI discovery is not the same thing as AI referral traffic. A buyer can encounter your brand in an assistant without clicking, visit through an identifiable assistant link, or return later through another channel. Those behaviors create different evidence and should not be combined under one label.

    Measurement layerEvidence you can recordDecision it supports
    Discovery visibilityYour company, product or page appears for a controlled set of buyer questionsWhether assistants associate your brand with the right problem and category
    Identifiable trafficA supported assistant sends a visit that Google Analytics recognizesWhich assistants and cited pages generate site demand
    Business outcomeThe visitor completes a qualified action and the lead or account advancesWhether AI discovery contributes to pipeline, not just sessions

    For visibility, maintain a fixed set of questions that reflect how a buyer researches your category. Record the assistant, exact prompt, date, brands mentioned, cited URLs and whether your brand appears in the answer or only in a citation. Keep the prompt wording and access conditions consistent when you repeat the check. The result is an observation, not a universal ranking, because assistant outputs can vary.

    For traffic, use the native AI classification in Google Analytics. For business outcomes, use your existing definitions of a qualified action, lead, opportunity and revenue. This division prevents a common reporting error: treating a mention, a visit and a sale as interchangeable proof of success.

    Build a GA4 view your revenue team can trust

    Google Analytics now identifies supported assistant referrals automatically. Recognized visits can use the medium ai-assistant, the channel group AI Assistant and the campaign value (ai-assistant). This removes much of the custom filtering previously needed to isolate traffic from supported tools.

    1. Confirm that AI Assistant appears in your acquisition reporting. If it does not, check the date range and whether you have any identifiable assistant referrals before changing channel definitions.
    2. Break the channel down by source and landing page. The channel total tells you the size of the stream; the source shows which supported assistant sent it; the landing page reveals which answers or resources earned the click.
    3. Compare AI Assistant and organic search over the same date range. Use the same qualified actions and conversion definitions for both channels. Otherwise, the comparison answers a reporting question rather than a business question.
    4. Show counts beside rates. A high conversion rate based on a very small number of sessions is useful as an early signal, but it is not yet a dependable forecast.
    5. Keep unidentified traffic unidentified. Do not relabel direct visits as AI traffic merely because AI visibility increased during the same period.

    Your recurring report should include identifiable AI sessions, source, landing page, qualified action count, qualified action rate and any matched opportunities. Add the number of leads that explicitly named an AI assistant even when analytics did not record an AI referral. That last field exposes influence the channel report cannot see without pretending the attribution is certain.

    The pattern matters more than the channel total. If AI traffic is small but converts well, protect the pages earning those visits and expand the buyer questions they answer. If traffic grows while qualified actions remain flat, inspect the landing page promise, offer and next step. More assistant visibility will not repair a page that attracts one intent and presents a call to action for another.

    The AI Assistant channel is a measurement improvement, not complete AI attribution. It covers identifiable referrals from supported assistants. It cannot count an answer that satisfies the buyer without a click, and it cannot automatically recover an AI touch when the buyer returns later through direct traffic, branded search or a different device.

    Connect assistant referrals to leads, accounts and opportunities

    Anonymous referral streams pass through a website gateway and connect in sequence to a lead, a company account and a qualified opportunity.

    B2B attribution becomes difficult after the click because evaluation often continues across sessions and people. Solve that problem with explicit evidence labels rather than a more aggressive attribution claim.

    • Observed AI referral: Google Analytics placed the session in the AI Assistant channel.
    • Self-reported AI discovery: A lead named an assistant when asked how they found the company.
    • AI-influenced opportunity: the account has either form of documented AI evidence before opportunity creation.
    • AI-sourced opportunity: AI discovery met your narrower, written rule for the first known acquisition touch.

    Do not merge these labels. An observed referral has stronger click evidence than an inferred influence, while a self-reported answer can reveal discovery that analytics missed. Both are useful as long as the dashboard preserves the distinction.

    1. Choose the onsite action that represents meaningful intent for your sales motion. It might be a demo request, contact submission, trial start, pricing interaction or another event your team already treats as qualified.
    2. When a visitor becomes a lead, carry permitted acquisition fields into the CRM: original source, current source, landing page, campaign and the date of the qualifying action. Retain the original values rather than overwriting them on every return visit.
    3. Add a short, optional discovery question to the form or sales qualification process. Allow the buyer to name ChatGPT, Claude, Gemini or another route in their own words instead of forcing every answer into a fixed channel list.
    4. Join the evidence at the lead and account levels where your consent and data practices allow it. Account-level reporting matters when one person researches and another submits the form.
    5. Write the attribution rule directly in the dashboard. State which touch qualifies an opportunity as sourced, which touches count only as influenced, and whether the evidence must occur before lead or opportunity creation.

    Track progression as counts and rates: identifiable AI sessions, qualified actions, leads, opportunities and closed revenue. Keep pipeline value beside opportunity count because one large deal can otherwise make a small channel look predictably scalable. For the same reason, do not forecast from conversion rate alone while the denominator remains small.

    This model also gives sales a useful feedback role. When a prospect mentions an assistant, record the assistant, the question they were trying to answer and any page or claim they remember seeing. That information can reveal buyer language, missing content and attribution gaps without turning an anecdote into a performance benchmark.

    Turn LinkedIn activity into a measurable discovery loop

    LinkedIn can strengthen the public evidence around a B2B company, but activity alone is not a growth result. Treat the company page, employee expertise, long-form content and distribution as inputs. Measure assistant visibility, referral traffic and pipeline separately as outputs.

    Remove ambiguity from your company and expert profiles

    Start with factual consistency. Keep the business address, contact details and product descriptions accurate on your website. Update the LinkedIn company page’s About section and services, including relevant industry language. Treat the profiles of executives and active subject-matter experts as extensions of the same entity, with current roles and clear areas of expertise. These are core surfaces for B2B AI discovery work.

    Assign an owner to each surface and update all of them when the company changes a product name, category, service or positioning statement. If your site publishes corresponding organization or product structured data, include it in the same update. Consistency does not guarantee an assistant mention, but it removes avoidable uncertainty about what the company does and who represents it.

    Publish one complete answer for each valuable buyer question

    Use LinkedIn articles and newsletters for questions that require more than a short update. The 800-1,200-word range associated with stronger AEO mentions is a useful starting hypothesis, not a universal ranking requirement. A complete 700-word answer is more useful than 1,000 words padded to satisfy a target.

    Give each long-form asset a specific job:

    • Use the buyer’s question or decision in the headline.
    • Answer it directly near the beginning.
    • Name the product category, intended user and relevant constraints plainly.
    • Explain criteria and tradeoffs that help the buyer make a decision.
    • Link to the corresponding website resource when the reader needs evidence, implementation detail or a next step.
    • Connect the content to an identifiable expert whose profile supports the subject.

    Add campaign parameters to links you control from LinkedIn so you can measure LinkedIn visits accurately. Keep those visits classified as LinkedIn traffic. A tracked LinkedIn click is not an AI referral, even when the content was also designed to improve AI discovery.

    Use engagement thresholds as experiments, not ranking factors

    If your team needs an initial promotion checkpoint, start with at least 10 substantive comments or 60 reactions. These figures can guide a campaign test, but they are not verified causal ranking factors for every LLM. Record them as engagement outcomes, then look independently for changes in assistant mentions, AI Assistant referrals and qualified demand.

    Count comments that contribute a question, example, objection or informed response. A pile of generic replies may increase the visible total without improving the information around the topic. Employee participation, expert partnerships, boosted company updates, Thought Leader Ads and follower ads can expand distribution, but paid and organic exposure should remain separate in your campaign log.

    Test one topic cluster from publication to pipeline

    1. Choose one buyer question tied to a product or service that can create qualified demand.
    2. Record the current website answer, LinkedIn coverage, controlled prompt observations and identifiable AI traffic.
    3. Correct company and expert profile details before publishing, so entity changes and content changes happen in a documented sequence.
    4. Publish the complete website resource and its LinkedIn treatment. Record the URL, author, publication date, distribution method, paid support and engagement.
    5. Watch all three measurement layers through a reporting period appropriate to your traffic volume and sales cycle.
    6. Compare the result with a similar topic cluster you did not change. Treat the difference as directional evidence unless your test design supports a stronger causal conclusion.

    Read breaks in the chain literally. More LinkedIn engagement without more assistant visibility proves distribution, not AI discovery. More assistant visibility without referral growth may mean the answer resolves the question without a click or does not present a useful next step. More AI referrals without qualified actions points to the landing page or intent match. More qualified leads without opportunities points to qualification, offer fit or the sales handoff.

    Key takeaways

    • Measure AI discovery as visibility, identifiable traffic and business outcomes. No single metric covers all three.
    • Use GA4’s AI Assistant channel for recognized referrals from supported assistants, but do not relabel direct traffic to fill attribution gaps.
    • Preserve observed referrals, self-reported discovery, influenced opportunities and sourced opportunities as separate evidence classes.
    • Keep website facts, LinkedIn company details and expert profiles current before trying to scale content distribution.
    • Treat the 800-1,200-word content range and engagement thresholds as test inputs, not universal LLM ranking rules.
    • Scale a topic only after you can follow its path from buyer question to content, assistant visibility, qualified action and pipeline.

    Start with one revenue-relevant buyer question. Establish the baseline, publish a complete answer, track the assistant referral and carry the evidence into your CRM. The first broken link in that chain tells you what to fix next. Repair it before increasing content volume or promotion spend.

    References

  • Performance Max Reporting for B2B: An Optimization Plan

    Performance Max Reporting for B2B: An Optimization Plan

    Your Performance Max campaign can look efficient while your sales team rejects nearly every lead. That isn’t a contradiction. It means the campaign is succeeding against a conversion signal that doesn’t represent the business outcome you actually need.

    You don’t need complete visibility into every automated bid to fix that problem. You need a reporting chain that connects platform activity to qualified pipeline, plus a disciplined way to intervene when the chain breaks. Here is how to build it.

    Start with the business outcome, not the campaign CPL

    Cost per lead is only useful when the word lead has a stable business meaning. A form submission, sales-accepted lead, opportunity and closed deal are not interchangeable outcomes. If PMax counts the first while your team values the third, a falling CPL can hide deteriorating performance.

    Begin with a conversion inventory. List every action available to the campaign, then write down what each action proves. A form submission proves that someone completed a form. It does not prove that the person fits your market, has buying authority or represents a real organization. Treating those facts as equivalent gives automation an easy target and gives you misleading reporting.

    1. Define the funnel stages your team can verify. Use the stages already applied consistently in your CRM, such as inquiry, accepted lead, opportunity and won business. Don’t create a more elaborate taxonomy than sales can maintain.
    2. Choose the deepest dependable optimization signal. The ideal event is close to revenue, recorded consistently and available often enough to guide the campaign. If closed business is too sparse or delayed, use the nearest reliably graded stage rather than pretending a raw form fill is equally valuable.
    3. Keep earlier actions for diagnosis. An inquiry can still reveal landing-page or creative behavior. It simply shouldn’t be allowed to masquerade as qualified demand in your business reporting.
    4. Connect platform records to later CRM outcomes. For B2B campaigns, offline conversion tracking and enhanced conversions for leads help carry information from the initial interaction into the later stages that matter.
    5. Remove obvious form abuse before asking the algorithm to learn. Controls such as reCAPTCHA can reduce low-quality submissions. They don’t replace qualification, but they prevent some worthless activity from being treated as useful training data.

    No tracking configuration can rescue an undefined lead. Sales and marketing must agree on the rule for accepting or rejecting one, and that rule must be applied consistently. Otherwise, imported outcomes encode internal inconsistency rather than buyer quality.

    This also changes how you evaluate cost. A campaign with a higher form-fill CPL may be the better investment if more of those forms become accepted leads or opportunities. Compare cost at the deepest mature stage available, not merely at the fastest stage the ad platform can report.

    Build a reporting chain that answers five different questions

    Five connected transparent chambers show a stream of marketing activity narrowing into leads, qualified prospects, and valuable pipeline outcomes.

    No single PMax report can tell you whether a campaign is working. Placement data explains where ads appeared. Channel data shows how automated delivery was distributed. Intent reports add search context. Asset reporting helps you inspect messages and formats. Your CRM determines whether any of that activity produced business value.

    Reporting layerQuestion it answersEvidence to inspectDecision it can support
    Business outcomeDid the lead progress?CRM qualification, opportunities, won business and imported offline outcomesChange the optimization signal, qualification process or lead controls
    Campaign and channelWhere did automated delivery produce recorded conversions?Campaign results, segmented conversion metrics and account-level channel reportingInvestigate channel mix and decide where a more focused follow-up test belongs
    Publisher placementWhich inventory received spend and recorded conversions?Microsoft’s Website Publisher URL report with spend and conversion dataIdentify inventory worth studying, protect brand safety or add a justified URL exclusion
    Intent and competitionWhat demand patterns surrounded performance?Google search term insights, auction insights, search themes and brand controlsRefine intent guidance, separate branded demand or investigate a competitive change
    Creative assetWhich messages and formats appear to attract response?Asset-level reporting and controlled creative testsRetire weak messages, add qualification or develop a stronger variant

    Microsoft’s PMax reporting makes the placement layer more actionable by adding conversion and spend metrics to the Website Publisher URL report. That is materially better than a list of domains with no economic context. You can see which placements consumed budget and which were associated with recorded conversions.

    But recorded conversions are still only as trustworthy as the conversion definition. A publisher with several form fills is not automatically a strong B2B placement if none of those people survive qualification. Conversely, a publisher with spend and no immediate conversion is not automatically waste if your evaluation window closes before leads mature. Join placement evidence to the CRM before making an efficiency judgment.

    Google’s channel, search-term, auction and asset reporting answers different questions. Channel reporting can expose where reported results originate, while search term insights add context about demand. Auction insights help you notice competitive conditions. Asset reporting shows how creative components are being evaluated. None of these views, by itself, proves incremental revenue.

    The practical rule is simple: use platform reporting to locate a pattern, then use downstream data to decide whether that pattern deserves action. A report is diagnostic evidence, not a verdict.

    Apply PMax controls in the order that reduces uncertainty

    When lead quality is poor, it is tempting to change audience signals, creative, themes and exclusions at once. That creates activity without producing a clear lesson. Apply controls from the bottom of the measurement chain upward.

    1. Repair the conversion signal and form hygiene

    First confirm that legitimate leads can be connected to later CRM stages and that obvious spam is filtered. If the campaign is rewarded for an event your business doesn’t value, every targeting adjustment rests on a faulty objective.

    Inspect conversion metrics separately rather than blending every action into one total. A campaign that produces many shallow actions and few qualified outcomes should not receive the same interpretation as one that advances prospects through the funnel. Segmented conversion reporting and offline outcomes give you the distinction needed to see that difference.

    2. Feed the system a clean first-party audience signal

    A large CRM export is not automatically a useful audience input. It may mix customers, unqualified inquiries, inactive records, students, vendors and prospects at unrelated stages. That teaches the system that all records deserve equal attention.

    Clean and segment the data before using it. Start with groups closest to a verified revenue event, provided each group has a consistent business definition. A list of accepted leads or opportunities usually carries clearer intent than an undifferentiated list of everyone who has ever completed a form. The value comes from the label, not the file size.

    Treat audience signals as guidance to be validated. After launch, compare the resulting leads with the segment characteristics you intended to emphasize. If the campaign finds cheap conversions outside your real customer profile, the CRM outcome should overrule the attractive platform metric.

    3. Use search themes and brand exclusions to clarify intent

    Search themes can guide Google PMax toward the demand you want it to explore. Build them around the problems, use cases and buying situations your qualified prospects actually express. Avoid turning themes into a loose catalogue of every phrase related to your industry.

    Brand exclusions solve a separate problem. If your objective is to assess incremental acquisition, branded demand can make an automated campaign look more efficient than its prospecting work really is. Search themes and brand exclusions provide useful control over those inputs and costs. Decide explicitly whether a campaign should capture existing brand demand or discover new demand, then configure and judge it against that purpose.

    Review search term insights after the campaign has produced meaningful evidence. Look for patterns that indicate the wrong buyer, job seeker, student, consumer use case or research intent. Those patterns should lead to a specific hypothesis about themes, messaging or conversion quality. They shouldn’t trigger an indiscriminate attempt to block anything unfamiliar.

    4. Treat placement exclusions as a precise control

    Microsoft’s placement spend and conversion data can expose publishers that are clearly unsuitable for the brand or economically unproductive after downstream outcomes are considered. High-performing inventory can also inform a separate Audience Ads or remarketing strategy, while unsuitable inventory can be added to an account-level URL exclusion list.

    Account-level exclusions have a wider blast radius than a campaign-specific observation. Before adding one, verify the exact domain, the reason for exclusion and the other campaigns that may rely on it. A clear brand-safety conflict can justify immediate action. An apparent performance problem needs more context: adequate spend relative to your economics, a review window long enough for lead grading and evidence that the recorded conversions did not progress.

    Do not turn the placement report into a manual bidding console. Its best use is to find material exceptions: unsafe environments, obvious mismatch, persistent waste or inventory that deserves a focused follow-up strategy.

    5. Make creative qualify the prospect

    B2B creative should do more than generate attention. It should help the right buyer recognize relevance and help the wrong visitor recognize a mismatch. State the use case, intended role, business context or other genuine qualifier that distinguishes your offer. Vague creative may attract more interactions while making lead quality harder to control.

    Video deserves deliberate treatment because YouTube is an important part of PMax inventory. Google also provides AI-assisted asset creation, creative testing and asset-level reporting. Use those capabilities to test a defined message difference, not merely to produce more variations. A useful test might compare problem-led positioning with outcome-led positioning, or broad language with a clear buyer qualifier.

    Read asset results alongside lead quality. An asset that attracts many conversions but disproportionately weak prospects may be doing its job badly, even if the platform labels it positively. The next variation should address the mismatch in the message rather than simply changing the visual treatment.

    Run a decision loop that sales can audit

    Marketing and sales professionals work at a circular table where campaign controls, lead reviews, feedback, and opportunity markers form a connected loop.

    PMax optimization becomes safer when every change starts with an observed business problem. Use the table below as a diagnostic map. The first column is a symptom, not a conclusion.

    What you noticeWhat to verifyWhat to do next
    Platform conversions rise while accepted leads stay flatWhich conversion actions increased, whether form abuse changed and whether offline outcomes are returning correctlyCorrect the optimization signal or lead-quality controls before changing audience inputs
    Form-fill CPL rises while opportunity creation improvesCost per accepted lead and opportunity for a fully graded cohortJudge the campaign on the deeper outcome rather than cutting it solely because the shallow CPL increased
    A publisher consumes spend without qualified progressionPlacement spend, recorded conversions, CRM outcomes, evaluation lag and brand suitabilityExclude a verified unsafe or persistently wasteful URL; otherwise gather enough context to distinguish delay from failure
    One channel appears to overperformConversion mix and lead quality by channelUse the pattern to design a focused channel or audience test instead of assuming every reported conversion has equal value
    An asset attracts response but weak prospectsThe CRM quality of leads associated with its message and offerAdd a buyer, use-case or business-context qualifier and test the revised message
    Branded demand dominates the visible intent patternWhether the campaign’s job is brand capture or incremental acquisitionUse brand controls where appropriate and report branded and non-branded intent against separate expectations
    Auction conditions change near a performance shiftWhether conversion quality, creative, landing experience or campaign inputs changed at the same timeTreat auction data as context and test the most plausible cause rather than declaring competition the cause automatically

    Make the review window match your buying process. If sales has not yet graded the leads in a cohort, that cohort cannot support a final quality conclusion. Label it incomplete instead of filling the gap with the platform’s faster metrics.

    Keep a short decision log for every material intervention. Record the observed problem, the evidence from each reporting layer, the change made, the downstream metric expected to move and the point at which the affected leads will be mature enough to review. This prevents the team from repeating tests or crediting an unrelated performance swing to the latest edit.

    Change one major layer at a time where practical. If you replace the audience signal, add themes, exclude publishers and rewrite every asset together, you may improve results but learn very little about why. Sequencing changes turns automation from an opaque system into a set of testable business decisions.

    Key takeaways

    • PMax optimizes the conversion definition you provide, so a cheap form submission is not evidence of efficient B2B growth.
    • Use offline outcomes and consistent CRM stages to evaluate cost per qualified result, not just cost per initial lead.
    • Placement, channel, intent, auction and asset reports answer different questions. Join them to downstream outcomes before acting.
    • Clean first-party audience segments, focused search themes and qualifying creative give automation better guidance.
    • Use URL and brand exclusions deliberately. Confirm the scope, business purpose and downstream evidence before restricting delivery.
    • Log each material change and wait until the affected lead cohort is mature enough to judge.

    Start with the latest lead cohort that sales has completely graded. Compare its CRM outcomes with the campaign, channel, intent, placement and asset evidence available on your platform. Find the largest break in that chain and change that layer first. The goal is not to control every automated decision. It is to make sure automation is learning from, and being judged by, the same definition of value your business uses.

    References

  • How to Build a Human-Led B2B Brand and Content Strategy

    How to Build a Human-Led B2B Brand and Content Strategy

    You can have a full content calendar, capable writers, strong subject-matter experts, and an AI workflow that produces drafts in minutes, yet still sound interchangeable with every competitor. The problem usually sits upstream: nobody has made a firm decision about what the market should believe about the brand.

    A human-led strategy fixes that without discarding AI. People retain the decisions with commercial consequences: what the brand should mean, which evidence deserves emphasis, what not to claim, and which trade-offs are acceptable. AI handles bounded work around those decisions, including organization, drafting, transformation, consistency checks, and distribution.

    Brand strategy begins with a decision, not a prompt

    AI can generate dozens of plausible positioning statements. That abundance is useful for exploration, but it is not a strategy. A position becomes strategic when you choose one interpretation of the business, support it, and reject adjacent messages that would weaken it.

    The distinction matters because your preferred position may not be the most obvious conclusion available from the facts. AI can connect known information and propose possible narratives, but it does not carry responsibility for choosing the narrative that serves your company, customers, and long-term direction. A named human must make that choice.

    A practical way to structure the decision is the claim-frame-prove discipline. It separates three elements that teams often collapse into one vague brand statement.

    ElementQuestion it must answerHuman decisionRequired output
    ClaimWhat do we want the market to believe?Choose a specific, defensible proposition instead of a collection of benefits.A sentence that can be tested against evidence.
    FrameWhy does this claim matter, and how should the evidence be interpreted?Select the commercially useful conclusion and the alternative view you are challenging.An explicit logical bridge from accepted facts to the desired association.
    ProofWhy should a buyer or an answer engine believe us?Set the evidence threshold, boundaries, and caveats.Named, accessible support for every material assertion.

    Write the claim so it can succeed or fail

    Statements such as trusted partner, innovative platform, and customer-first company are difficult to disprove, which also makes them difficult to value. Replace them with a proposition that has an identifiable audience, problem, outcome, and reason to believe.

    Use this working structure: For a specific buyer facing a specific decision, the brand represents a defined approach or advantage because named evidence supports it. This matters because the evidence leads to a useful conclusion the buyer may not have considered.

    Do not publish the template itself. Use it to force the internal decision. If the team cannot complete it without broad adjectives, multiple audiences, or unsupported outcomes, the positioning is not ready for production.

    Treat the frame as strategy, not decoration

    A frame is not a clever slogan placed above the same old product copy. It tells the reader what the evidence means. Two companies may have similar capabilities, but the company that explains the consequence of those capabilities can own a more useful association in the buyer’s mind.

    Pressure-test a proposed frame with five questions:

    • Would a relevant competitor be equally comfortable making this claim?
    • Does the proof establish the promised outcome, or merely show that a feature exists?
    • Does the frame add a meaningful conclusion rather than restating the claim?
    • Can a skeptical reader follow the path from evidence to conclusion without filling in a missing step?
    • Have you stated the conditions or use cases in which the claim does not apply?

    If the competitor can copy the entire argument without changing the evidence, you have a category description, not a position. If the conclusion requires a leap that the proof cannot support, you have promotion, not a position. Human judgment is the work of finding the narrow territory between those failures.

    Turn positioning into a content operating system

    A human hand places a central colored block into a connected tabletop system of blank content modules and evidence tokens.

    A positioning document has little value if every writer interprets it differently. Your content system must carry the same claim, frame, and proof into landing pages, executive viewpoints, product education, case material, sales enablement, and answer-focused content without forcing every asset to repeat identical wording.

    Start with a claim ledger rather than a topic calendar. The calendar tells you when something will be published. The ledger tells you what the business is prepared to assert, why it is true, where the evidence lives, and who is accountable for approving it.

    Each ledger entry should contain:

    • Approved claim: the exact proposition content may communicate.
    • Intended audience and decision: who needs the information and what they are trying to decide.
    • Strategic frame: the conclusion the evidence should help the audience reach.
    • Proof: the product fact, operational evidence, customer evidence, expert knowledge, or other support available for the claim.
    • Evidence location: the page, record, or internal owner that can substantiate the assertion.
    • Scope limits: markets, use cases, products, or circumstances the claim does not cover.
    • Approval owner: the person authorized to accept, narrow, or reject the claim.

    A claim without an evidence location or owner is not ready to enter an AI prompt. Marking it as unverified is safer than allowing a drafting system to fill the gap with language that merely sounds credible.

    Brief content around a buyer decision

    Topic-only briefs produce topic-shaped content: broad, informative, and hard to distinguish. A decision brief tells the writer what must change for the reader. It should identify the question that brought the reader to the page, the misconception or uncertainty blocking progress, the approved claim, the frame, the evidence, and the next sensible action.

    Before drafting, require the content owner to finish this sentence: After reading, the intended buyer should be able to decide whether or how to do something specific. If the answer is merely understand the topic, the brief is probably too broad.

    Then assign the page one primary job. It might define a problem, establish a fact, compare approaches, resolve an objection, substantiate a brand claim, or help the buyer act. A page may support secondary jobs, but letting every asset do everything usually produces a long page with no clear purpose.

    Give AI bounded responsibilities

    AI is most useful after the decision architecture exists. Give it approved material and a defined transformation, then require it to expose gaps instead of inventing bridges.

    Suitable AI responsibilities include:

    • Grouping buyer questions by intent or stage.
    • Turning approved interviews and notes into candidate outlines.
    • Producing channel-specific versions of an approved argument.
    • Checking drafts for contradictions against the claim ledger.
    • Finding assertions that lack attached evidence.
    • Suggesting alternative explanations while preserving the approved position.
    • Identifying where the relationship between a claim and its proof remains implicit.

    Keep these responsibilities human:

    • Choosing the market association the brand will pursue.
    • Deciding which audience or use case takes priority.
    • Judging whether the available evidence is strong enough.
    • Resolving disagreements between subject-matter experts.
    • Approving external claims, comparisons, and conclusions.
    • Deciding what the brand will deliberately decline to say.

    The boundary is simple: AI may generate options and transformations, but it does not receive decision rights. Record the human decision before generation begins so the team can distinguish deliberate strategy from wording that appeared during drafting.

    Make the brand legible to buyers and answer engines

    Business buyers and an abstract scanning device examine the same illuminated geometric object and its visible proof components.

    Having evidence somewhere on the website is not the same as communicating an evidence-backed position. A person may infer the connection after visiting several pages. A search or answer system may not make the same connection, and it has no obligation to choose the interpretation most favorable to your brand.

    Brand evidence typically becomes more usable through three levels:

    <!– wp:list {
  • Paid Media Optimization for Long Sales Cycles: A Practical System

    Paid Media Optimization for Long Sales Cycles: A Practical System

    Your paid campaigns can generate leads this week while the resulting revenue takes months to appear. That delay creates an uncomfortable decision: should the ad platform optimize for the form submission it can see quickly, or for the closed sale that reflects the outcome you ultimately care about?

    The answer is not simply “optimize further down the funnel.” In a human-led sales process, a closed deal measures more than media quality. It also reflects rep skill, follow-up speed, capacity, product availability, approval delays, and seasonal behavior. You need a bidding signal that rewards valuable demand without teaching the platform to react to every operational swing.

    Key takeaways for long-cycle campaigns

    • Use the deepest conversion event that is frequent, timely, and operationally stable. A closed sale is not automatically the best bidding signal.
    • For many long sales cycles, the practical optimization boundary is a valued lead at submission: not every form fill receives the same value, but the value is assigned before sales execution changes the outcome.
    • Estimate lead value from conversion probability and typical deal size using information available when the inquiry arrives.
    • Keep downstream revenue in your measurement system even when it is not the primary bidding input. You need it to calibrate lead values and judge business performance.
    • Diagnose media quality and sales operations separately. Stable lead volume and predicted value alongside a falling close rate is not sufficient evidence that targeting has failed.

    Why a closed sale can be the wrong bidding signal

    Identical lead spheres move through different sales-process channels, where workload, delays, approvals, inventory, and other obstacles change which ones reach the final outcome.

    An ad platform sees the conversion outcome, but it does not understand your organization. If a strong sales rep closes more leads than a new rep, the platform can observe the difference in recorded sales. It cannot inherently know that rep assignment caused it.

    Imagine that the same campaigns, keywords, landing pages, and lead profiles continue running while your most effective closer takes leave. A less experienced colleague receives the leads, follow-up slows, and the close rate falls. An automated system optimizing for sales may treat the decline as evidence that those clicks or audiences became less valuable. It can then reduce bids, shift budget, or suppress targeting that was still generating suitable prospects.

    Rep composition is only one source of noise. Close rates can change when workloads increase, response times stretch from days into a week, a competitive product is withdrawn, an approval stalls, or vacation coverage leaves inquiries untouched. Leads from other channels can also consume the sales team’s capacity even though nothing changed inside the paid account.

    Calendar behavior can make the distortion severe. In one observed financial-services pattern, lead-to-sale conversion around the third week of December rose by as much as 150% compared with normal weeks, then fell sharply during the holiday week. The leads and placements had not suddenly become much better and then much worse. Sales urgency, customer availability, bonus incentives, and leave schedules had changed.

    This is the core diagnostic distinction: a sale is a business outcome, but it is not always a clean media-quality label. When you ask an algorithm to bid on it, you are asking the platform to optimize all the forces embedded in that outcome, including forces the campaign cannot control.

    Set the optimization boundary at a stable quality signal

    Your optimization boundary should sit at the latest funnel event that satisfies three conditions: the event happens often enough for automation to learn from it, it arrives soon enough to guide current bidding, and its definition remains stable enough to mean the same thing from one period to the next.

    Direct sales or revenue optimization can be appropriate when conversion volume is sufficient, the reporting delay is short, and the sales process is stable. Long, low-volume, human-dependent sales cycles frequently fail one or more of those tests. In that situation, a quality-adjusted lead is usually more dependable than either a raw form fill or a closed deal.

    • A raw lead count is too shallow when inquiries have materially different probabilities of conversion or deal sizes.
    • A closed sale is too deep when it is rare, delayed, or heavily shaped by sales execution and operational capacity.
    • A valued lead at submission is the middle path when you can estimate commercial potential from information already available at the point of inquiry.

    The phrase “at submission” matters. If you assign the value after seeing which rep handled the lead, whether the buyer answered a follow-up call, or how the opportunity progressed, you have allowed downstream execution back into the bidding label. The model should use attributes known when the lead enters the funnel.

    The optimization boundary is not the reporting boundary. Continue importing final status and realized revenue. Use those outcomes to evaluate the business, recalibrate the lead-value model, and identify sales-process problems. You are separating two jobs: the bidding system needs a timely and stable signal, while management reporting needs the complete commercial outcome.

    Build a lead-value model from matured historical cohorts

    Lead tokens pass through a long time tunnel before matured groups are sorted into illuminated value categories, with a separate path continuing toward eventual revenue.

    A useful lead-value model estimates expected revenue rather than merely labeling a lead “good” or “bad.” Start with historical inquiries that have had enough time to reach a final outcome. A full year is preferable because it captures more operating conditions and seasonality, although six months can be sufficient when that is all the reliable history you have.

    1. Select matured cohorts. Group leads by the date they entered the funnel, then include cohorts old enough that most opportunities have reached a meaningful final status. Mixing fresh, unresolved leads with completed cohorts will make recent traffic appear artificially weak.
    2. Freeze the information available at inquiry. Retain fields the campaign could reasonably influence or attract: requested product, project scope, stated timing, loan characteristics, company size, industry, and other submission-time attributes relevant to your business.
    3. Calculate conversion probability by meaningful segment. Determine which inquiry-time characteristics correspond with different eventual conversion rates. Keep the segments understandable enough that you can explain why a lead received its value.
    4. Measure typical deal value for each segment. A segment that closes frequently is not necessarily the most valuable if its average commercial outcome is small. Conversely, a lower-probability segment may deserve attention when successful deals are much larger.
    5. Assign expected revenue. The basic logic is conversion probability multiplied by typical deal value. The result is a monetary estimate that a value-based bidding system can compare across leads.
    6. Reconcile predictions with realized revenue. Add the predicted values for a matured acquisition cohort and compare that total with the revenue eventually produced by the same cohort. Large or persistent gaps mean the probabilities, deal values, segments, or data quality need adjustment.
    7. Version and revisit the model. Preserve the value assigned at submission and record which model version produced it. Reassess the model quarterly so changes in campaign mix, products, buyer behavior, and operations do not leave old assumptions running indefinitely.

    The most useful segmentation variables depend on the transaction. Financial-services leads may differ by loan value or terms. B2B inquiries may differ by company size or industry. Construction opportunities may differ by scope and immediacy. Choose fields that were genuinely known at inquiry and have a defensible relationship with conversion probability or deal size.

    A practical framework might assign expected values such as $850 to a high-probability lead, $420 to a middle tier, and $120 to a lower-probability lead. Those figures are examples, not benchmarks. Copying them would make the model arbitrary; your values must come from your own conversion rates and deal economics.

    Do not confuse an expected-revenue value with a conventional lead score. A score of 90 may rank above a score of 40, but it does not tell a bidding system whether the first lead is twice as valuable, ten times as valuable, or only marginally better. Monetary values express the size of the difference and allow value-based bidding to make an economically meaningful tradeoff.

    Guard against data leakage as you build the model. Opportunity stage, rep assessment, response behavior, and later qualification calls may predict sales extremely well, but they were not known when the ad produced the inquiry. Using them to label historical leads can create a model that looks accurate in analysis but cannot assign equivalent values consistently at submission.

    Feed values into bidding without losing revenue accountability

    Once the values reconcile reasonably with matured revenue, configure the lead conversion to send its expected value with the event. Value-based bidding, including Google Ads target return on ad spend, can then pursue the mix of inquiries with the highest predicted commercial value rather than the largest number of identical form fills.

    Treat the implementation as a measurement change before treating it as a bidding change. First log the dynamic values while the existing strategy remains in place. Confirm that each valid lead is counted once, the correct value reaches the correct conversion action, and the platform’s aggregate value matches your lead system for the same inquiry dates. Only then should you let a value-based strategy act on the signal.

    Keep a compact acquisition record for every lead. At minimum, preserve the lead identifier, inquiry timestamp, paid-media attribution, value assigned at submission, model version, rep assignment, first-response timing, final status, and realized revenue. This lets you distinguish what the model knew from what happened after the handoff.

    Evaluate performance through two related views:

    • Predicted return compares total expected lead value with the spend that produced those leads. It is available quickly enough to guide campaign management.
    • Realized return compares eventual revenue with spend for the same acquisition cohort. It arrives later but tells you whether the model and the wider commercial process delivered what the early signal implied.

    Keep the cohort alignment intact. Revenue closed this month may have come from leads acquired months ago, so comparing it with this month’s spend can produce a convincing but false trend. Join eventual revenue back to the date and campaign that generated the inquiry. That makes the lag explicit and prevents old pipeline from being credited to current media.

    Roll the bidding change into a controlled part of the account rather than changing every campaign at once. Watch lead counts, predicted value, spend, and the distribution of value tiers. As cohorts mature, compare their predicted totals with realized revenue. A strategy that raises platform-reported value but repeatedly produces less realized revenue is exposing a calibration or tracking problem, not proving business growth.

    Diagnose a performance drop before changing the media

    When sales fall, resist the reflex to rewrite ads or cut audiences immediately. Walk through the funnel in causal order. The goal is to locate the first point where performance changed.

    1. Check inquiry volume. Did the number of valid paid leads change, or did only closed sales change?
    2. Check predicted lead value. Did the mix move toward lower-value tiers even if total lead volume remained stable?
    3. Check media inputs. Look for meaningful changes in targeting, search terms, audience composition, placements, creative, landing-page behavior, budget, or tracking.
    4. Check routing and response time. Determine whether leads reached the right people and whether follow-up slowed.
    5. Check staffing and capacity. Review rep assignment, leave, onboarding, workload, and competing lead sources.
    6. Check the commercial offer. Identify withdrawn products, changed eligibility, approval delays, pricing constraints, or other conditions that made the same lead harder to close.
    7. Check calendar effects. Separate customer availability and sales-team urgency from changes in demand quality.
    8. Change the layer that failed. Adjust campaigns when the deterioration begins in traffic or predicted lead value. Address operations when the early media signal is stable but handoff or close performance worsens.

    This sequence gives you a cleaner interpretation. If lead volume and predicted value remain stable while response times rise and close rates fall, the evidence points downstream. If response times and sales coverage remain stable while the account produces a weaker value mix, the media deserves scrutiny. If both change, treat them as separate problems instead of asking one campaign adjustment to solve both.

    Your first move should be an export of matured lead cohorts, not another bid adjustment. Identify the inquiry-time attributes that separate conversion probability and deal size, assign expected revenue, and reconcile the total against actual revenue. Once that model holds together, use it as the bidding signal and keep closed sales as the accountability signal. That division gives automation something it can learn from without letting every staffing or operational change rewrite your media strategy.

    References


  • Marketo Engage SEO Retirement: A Practical Migration Plan

    Marketo Engage SEO Retirement: A Practical Migration Plan

    If your team depended on the Marketo Engage SEO tile, this is no longer a roadmap item you can leave for later. Adobe scheduled the feature to be discontinued on March 31, 2026, with the tile removed beginning April 1. That deadline has passed.

    Your immediate job is to establish what was preserved, what was lost, and which business process must replace the feature. Do that before buying another platform. A rushed tool purchase can restore a dashboard while quietly breaking historical comparisons, ownership, or reporting definitions.

    Key takeaways

    • Adobe retired the SEO feature within Marketo Engage; this is not evidence that Marketo Engage itself was retired.
    • The scheduled export deadline was March 31, 2026, and removal of the SEO tile was set to begin April 1.
    • If you exported your data, preserve the untouched files, document their coverage, and test whether they can actually be opened and interpreted.
    • If you missed the deadline, search existing business systems and ask Adobe Support about recovery before attempting to reconstruct the history.
    • Select a replacement according to the jobs your team needs to perform, not according to suite familiarity or corporate ownership.
    • Never join old and new metrics into a continuous trend line until you have checked their definitions, filters, date boundaries, and URL treatment.

    Separate the SEO retirement from the rest of Marketo Engage

    The scope matters. Adobe scheduled the retirement of Marketo Engage’s SEO feature and its tile. Nothing in that change establishes that your forms, campaign programs, lead operations, scoring, or the wider Marketo Engage platform must be migrated.

    Keep the response proportional. Remove dependencies on the SEO feature, but don’t turn a feature decommission into an unplanned marketing automation migration unless you already have a separate reason to reconsider the broader platform.

    DecisionWhat is establishedWhat you should do
    Feature scopeThe Marketo Engage SEO feature was scheduled for retirement.Inventory processes that used the SEO tile rather than treating every Marketo workflow as affected.
    Data accessExisting SEO data needed to be exported by March 31, 2026.Treat post-deadline access as unavailable unless Adobe confirms otherwise for your account.
    User interfaceRemoval of the SEO tile was scheduled to begin April 1.Remove tile-specific instructions, bookmarks, screenshots, and training steps from current procedures.
    ReplacementNo automatic replacement, entitlement, or historical transfer was established.Verify licensing, data portability, metric coverage, and implementation separately.

    Adobe’s stated rationale was to redirect resources away from underused functionality. That is a useful warning for your operating model: a feature can be technically available while becoming strategically peripheral. Add vendor roadmap review and export readiness to the ownership of any reporting capability you replace.

    Adobe’s 2025 acquisition of Semrush makes Semrush an obvious candidate for evaluation, but the corporate relationship does not prove that your Adobe agreement includes it, that Marketo SEO history transfers into it, or that its measurements match your old reports. Procurement, migration, and metric continuity remain three separate questions.

    If you exported the data, prove the archive is usable

    An analyst verifies generic digital records as they move from an organized archive through a glowing validation frame.

    Having an export is not the same as having a recoverable reporting asset. A file can exist while its date range, filters, field meanings, or account context have already been forgotten. Preserve the evidence before anyone cleans, renames, or transforms it.

    1. Keep an untouched master copy. Store the original export in a controlled, read-only location. Work from duplicates. If your data-governance process supports checksums, record one so later teams can verify that the master was not altered.
    2. Create an export register. For every file, record its filename, export date, Marketo account or workspace, owner, known reporting period, known filters, file format, and storage location. Mark unknown details as unknown instead of guessing.
    3. Inspect the structure. Confirm that the file opens, headers are intact, characters render correctly, dates parse consistently, URLs have not been converted or truncated, and numeric columns remain numeric. Save a field list beside the archive.
    4. Document metric meanings. Capture any surviving definitions from procedures, dashboard labels, screenshots, or team documentation. A column called visibility, position, traffic, or opportunity has little long-term value unless the calculation and scope are understood.
    5. Locate downstream dependencies. Search recurring reports, dashboards, presentation templates, planning models, tickets, and operating procedures for fields or screenshots drawn from Marketo SEO. Record the owner and business decision associated with each one.
    6. Test restoration. Import a working copy into the system where analysts will actually use it. Check several records against the original, including the earliest and latest dates, blank values, duplicate URLs, and unusually large or small values.
    7. Apply appropriate access controls. Do not assume that a file is safe to distribute merely because it came from an SEO feature. Review its actual contents and follow the controls required by your organization.

    Treat the export as a fixed historical archive, not a live dataset. A new platform can supply future measurements, but that does not make its numbers directly comparable with the archived Marketo SEO values. The tools may use different keyword sets, locations, devices, crawling rules, URL normalization, update schedules, or calculation methods.

    When exact definitions cannot be recovered, label the archive accordingly. An explicit limitation such as “legacy Marketo SEO metric; calculation unavailable” is more honest and more useful than a confident but invented definition.

    If you missed the deadline, recover before you reconstruct

    Do not assume Adobe can restore the data after the scheduled removal, but do not assume it is irretrievable without checking either. Recovery should begin with existing evidence and a narrowly framed support request.

    1. Preserve what remains. Collect filenames, dashboard screenshots, report attachments, procedures, tickets, and presentation slides that show how the feature was used. Record who used it and which decisions depended on it.
    2. Search sanctioned storage. Check shared drives, approved cloud storage, data warehouses, business intelligence systems, reporting folders, ticket attachments, and relevant email attachments. Ask likely users to search their work files within your organization’s retention and security policies.
    3. Open an Adobe Support request. Identify the Marketo account, the retired SEO feature, the required reporting period, and the desired export. Ask whether any account-level recovery or backup route remains. Treat recovery as unconfirmed until Adobe gives you a direct answer.
    4. Map each missing output to an authoritative system. Organic search performance may be recoverable from verified search-engine properties; site behavior may exist in web analytics; conversion outcomes may live in Marketo programs, a CRM, or a warehouse; rankings and technical findings may exist in another SEO platform. Availability depends on what your organization had already configured and retained.
    5. Create a gap log. Record the last date supported by reliable legacy evidence, the first date covered by the replacement, unavailable intervals, changed definitions, and any reconstructed values. Keep this log beside the dashboard rather than in a forgotten migration folder.

    Reconstructed data must be labeled by origin. A chart assembled from search-engine exports, analytics, archived slides, and a new SEO platform is not a recovered Marketo SEO dataset. It is a new analytical record with multiple inputs and potentially different definitions.

    If there is no trustworthy overlap between the retired feature and its replacement, start a new baseline. Leave a visible break in the trend. A gap is inconvenient, but a seamless line made from incompatible measurements can lead stakeholders to act on growth or decline that never occurred.

    Replace the workflow, not just the tile

    A team reroutes connected workflow modules around an obsolete component on a collaborative planning table.

    Start replacement planning with the decisions people need to make. “We need another SEO tool” is too vague to evaluate. “We need page-level search performance for content prioritization” or “we need scheduled technical crawl findings assigned to site owners” gives you something testable.

    • For organic search performance, define the required query, page, country, device, and date dimensions, along with export and retention needs.
    • For technical SEO, define crawl scope, canonical handling, JavaScript requirements, issue ownership, and the evidence required to close a finding.
    • For rank and competitive visibility, specify the tracked keyword set, search location, device, measurement cadence, and treatment of search features before comparing vendors.
    • For marketing attribution, define how landing-page activity connects to conversions, Marketo programs, CRM outcomes, and the attribution model. An SEO dashboard alone does not settle those relationships.
    • For AEO, GEO, or AI visibility, define prompts, markets, models, citations, mentions, and review cadence as a new measurement requirement. Do not rename a traditional ranking metric and present it as AI-search visibility.

    Require each candidate workflow to demonstrate data export, retention, API or connector access where needed, metric documentation, user permissions, scheduled delivery, and ownership. If historical import is important, verify what the platform actually imports and whether imported records remain distinguishable from data it measured itself.

    Use any period of overlapping data as a calibration window, not as proof that the systems are equivalent. Compare the same URLs and dates under the closest available settings. Investigate differences in coverage, time zones, URL variants, keyword sets, update timing, and aggregation. Record accepted differences before the new dashboard becomes the official record.

    The cutover is complete only when the old dependency has an owner-approved disposition. Update recurring reports, procedures, bookmarks, onboarding materials, dashboard annotations, and stakeholder expectations. Mark legacy metrics as retired, name the replacement metric, and retain the definition of each.

    Before your next SEO report goes out, place the export register and gap log beside it. That small control prevents a polished dashboard from presenting two different measurement systems as one continuous history.

    References

  • How to Choose an SEO Agency for an AI Company in 2026

    How to Choose an SEO Agency for an AI Company in 2026

    If you are hiring an SEO agency for an AI company, the hard part is not finding firms that mention AI. It is deciding whether you need category education, technical repair, brand and UX work, conversion testing, launch support, or a coordinated paid-organic program. Those are different jobs, and an impressive client list cannot turn one into another.

    The framework below will help you define the assignment, route it to the right type of partner, test the agency’s proof, and make competing proposals comparable. The goal is not to find an agency that can plausibly do everything. It is to hire the team best equipped to remove the constraint that is holding back qualified discovery and revenue.

    Name the bottleneck before you name an agency

    A team examines an interconnected growth system where geometric signals are backed up at one constricted junction.

    Start with the part of your growth system that is failing. AI companies often bundle several problems under SEO even though each problem calls for different people, deliverables, and measures of success.

    • Discovery is the bottleneck: Buyers already search for the problem or category, but your useful pages are not visible. You likely need technical SEO, search-intent mapping, authoritative content, internal linking, and a defined approach to AI search visibility.
    • Category education is the bottleneck: Prospects do not yet have stable language for the problem, or your positioning sounds interchangeable with every other AI vendor. You need a thought-leadership and content program that connects the emerging category to problems buyers already recognize.
    • Product comprehension is the bottleneck: People reach the site but cannot quickly tell who the product is for, what workflow it changes, or why it is credible. Brand strategy, messaging, information architecture, and UX may matter more than publishing additional articles.
    • Conversion is the bottleneck: Relevant traffic reaches the right pages but does not take the next step. The work shifts toward A/B testing, mobile experience, form design, proof placement, and conversion analysis.
    • Launch trust is the bottleneck: You are introducing a product, entering a new category, or managing a reputation issue. PR, brand mentions, launch messaging, and reputation management need to work alongside SEO.
    • Channel coordination is the bottleneck: Paid search, organic content, social distribution, and short-form video operate as separate campaigns. An integrated performance partner may be more useful than a narrowly focused SEO shop.

    Choose a primary bottleneck and a secondary one. If every objective is equally important, the brief is not ready. An agency facing an undefined assignment will usually respond with a standard service bundle, and you will end up comparing activity counts instead of solutions.

    You can sharpen the diagnosis with a small journey audit. Open the page that should convert your most valuable buyer and check whether it names the buyer, the use case, the operational change, and the supporting proof. Then inspect the search results for the query that buyer would use before knowing your brand. Finally, test a fixed set of relevant questions in the AI interfaces that matter to your audience. Record whether your company is absent, merely mentioned, cited as supporting evidence, or linked. Those are different outcomes.

    Turn the result into one sentence: your company needs a named audience to discover, understand, or choose a specific offer, and the current obstacle is a clearly identified part of that journey. That sentence belongs at the top of every agency brief.

    Route your shortlist by specialist fit

    As of March 12, 2026, seven candidates span several distinct versions of AI-company marketing. The reported team sizes, founding years, and positioning are useful routing signals, but they are not substitutes for checking the people who would actually deliver your account.

    CandidateReported profileShortlist whenClarify before signing
    First Page Sage100-250 people; founded in 2009; SEO, generative engine optimization, thought leadership, and lead generationYour central problem is building search authority and qualified discovery through sustained expert contentAsk for separate evidence covering conventional rankings, AI citations or mentions, qualified leads, and pipeline contribution
    Clay Agency11-50 people; founded in 2016; technology branding and UX/UI designThe product is difficult to explain, the website no longer matches the offer, or a launch requires a stronger interactive experienceEstablish whether ongoing technical SEO and content production are included or whether the engagement is primarily brand and design work
    Marketing Eye11-50 people; founded in 2004; technical SEO for SaaS, audits, keyword analysis, content, and social campaignsYou want a leaner partner to diagnose technical and content issues across a SaaS websiteConfirm who supplies subject-matter depth, who implements technical recommendations, and how social work supports the search objective
    RNO151-100 people; founded in 2018; market research, digital branding, product design, UX/UI, and technical SEOYour search problem is entangled with product research, positioning, or a broader digital experience redesignSeparate the SEO deliverables from the research and design deliverables so each has an owner and an acceptance test
    REQ51-100 people; founded in 2008; branding, PR, reputation management, UX, and supporting SEOYou are launching a product, building category credibility, or need search work coordinated with reputation and media activityAsk how PR outcomes will connect to durable pages, non-branded discovery, and measurable buyer actions
    Optimizely500+ people; founded in 2010; A/B testing, personalization, mobile optimization, and conversion rate optimizationYou already have meaningful traffic and content, but need a stronger experimentation and conversion layerDetermine whether you are buying a platform, implementation support, an experimentation program, or full SEO execution; these are not interchangeable
    Directive Consulting50-249 people; founded in 2014; SEO, paid media, short-form video, and social marketing for technology companiesYour acquisition plan needs paid and organic channels to share audience intelligence, creative, and performance reportingRequire a clear division of budget, deliverables, attribution, and ownership across organic search, paid campaigns, video, and social

    Use the table as a routing tool, not a league table. Clay Agency and RNO1 may be compelling when a site or product experience is the actual constraint. REQ may make more sense around a launch or reputation problem. Optimizely is a different kind of option because its stated strength is experimentation and personalization rather than an assumed replacement for an SEO-led content team. Directive Consulting fits a broader performance remit, while First Page Sage and Marketing Eye align more directly with sustained organic search work.

    Company size and age can help you ask operational questions, but neither proves fit. A larger organization may offer more specialists while placing your account behind more handoffs. A smaller team may give you senior access while having less capacity for simultaneous technical, editorial, design, and analytics work. Ask for the names, roles, availability, and relevant work of the proposed delivery team. Evaluate that team, not the agency’s total headcount.

    Demand proof that survives an AI-company sales cycle

    Translucent evidence tiles move through technical, research, stakeholder, and decision checkpoints, with one tile remaining intact to the end.

    AI-company SEO can produce attractive surface metrics without resolving a commercial problem. More impressions may come from loosely related informational queries. More AI mentions may be unlinked or occur in prompts your buyers never use. More traffic may be branded demand created elsewhere. You need evidence at the query, page, audience, and conversion levels.

    Inspect proof at the query and page level

    Ask each agency to walk through work that resembles your primary bottleneck. A credible walkthrough should identify:

    • The target audience and the problem that audience was trying to solve.
    • The query set or demand theme, including why it mattered commercially.
    • The baseline condition before the work began.
    • The pages created, consolidated, redesigned, or technically repaired.
    • The difference between branded and non-branded discovery.
    • The conversion event used to connect visibility with buyer action.
    • The changes the agency can reasonably connect to its work and the changes it cannot.

    A logo and an upward traffic chart do not answer those questions. Client names can establish market familiarity, but they do not show what the agency owned, whether the work is still live, or whether the result applies to your sales motion. Where confidentiality limits disclosure, ask for an anonymized page-level explanation and a reference from a company with a similar buying process.

    Separate AI visibility from conventional SEO evidence

    An agency offering GEO or AI search optimization should be able to define what it measures. Brand mention, citation, linked citation, recommendation, referral visit, and influenced conversion are separate events. A proposal that collapses them into one visibility score prevents you from seeing what actually changed.

    Ask for a fixed prompt library organized around awareness, problem exploration, comparison, and selection. Each observation should record the prompt, the interface or model, the date, the output, the brand outcome, and any cited page. AI responses can vary, so isolated screenshots are weak evidence. A repeatable observation method is more useful than a dramatic example.

    The agency should also distinguish observation from inference. A linked referral can be observed in analytics. A later branded search may have been influenced by an AI answer, but that relationship is harder to prove. Honest reporting preserves that distinction instead of assigning every downstream action to GEO.

    Test the technical and editorial operating model

    Use one of your real pages during the sales process. Ask the agency to explain what it would inspect, what it would change, and who would do the work. The discussion should cover crawl and index access, rendering, canonical signals, information architecture, internal links, structured data where relevant, page intent, claim support, and the conversion path.

    Then follow the content through its production workflow. Find out who interviews your experts, who drafts, who verifies product claims, who reviews regulated or security-sensitive language, who publishes, and who refreshes pages after the product changes. AI products evolve quickly; a technically optimized page can still become unreliable when its feature descriptions, integrations, model names, or limitations are no longer current.

    Listen for clear limits. A serious team will sometimes say that it needs analytics access, a crawl, a developer’s input, or buyer evidence before reaching a conclusion. Instant certainty from a sales call is not the same as technical fluency.

    Make proposals comparable before the contract gets expensive

    Send every shortlisted agency the same brief. Include the audience, primary bottleneck, product and category, markets served, buying journey, current search and AI visibility, conversion definition, technical constraints, available experts, approval process, existing content, analytics access, and the commercial outcome the program must support.

    Require the proposal to translate that brief into an explicit operating plan. A useful response will show what happens first, which assumptions must be tested, who owns each dependency, what the agency will deliver, what your team must supply, and how decisions will be made when early evidence contradicts the initial plan.

    Decision gateStrong answerPause and clarify
    DiagnosisA specific growth constraint tied to audience behavior, pages, and technical conditionsA generic package that could be sent to any SaaS company
    MeasurementA baseline, defined conversion events, branded and non-branded separation, and a map from leading indicators to business outcomesTraffic, impressions, or one blended visibility score presented as the complete result
    SEO and GEODistinct methods for rankings, citations, mentions, referrals, and influenced demandA claim of AI optimization with no prompt set, observation record, or page-level method
    Delivery teamNamed roles, realistic availability, review responsibilities, and an escalation pathSenior specialists appear during the pitch but the delivery team remains unidentified
    Technical executionImplementation ownership, developer dependencies, staging, validation, and rollback responsibilitiesAn audit ends with recommendations that nobody is assigned to implement
    Editorial qualityExpert input, claim verification, revision ownership, and a refresh processContent volume is promised without explaining accuracy or subject-matter review
    Commercial termsClear deliverables, account access, content ownership, acceptance criteria, change control, and handover termsAmbiguous intellectual-property rights, broad lock-in, or no usable exit process

    Do not grant unrestricted production access simply because an agency has passed procurement. Define who can change templates, tracking, redirects, robots directives, canonical tags, structured data, forms, and published claims. Use backups, staged changes, approval rights, and rollback procedures. A technically plausible edit can still remove indexable content, corrupt measurement, or interrupt lead capture.

    The contract should say who owns written content, design files, dashboards, prompt libraries, analytics configurations, and accounts created during the engagement. It should also define what you receive at handover. If the terms include exclusivity, broad intellectual-property assignments, unusual indemnity, or material data-handling obligations, have qualified counsel review those provisions before you sign; their effects can continue after the campaign ends.

    If confidence is still low, scope an initial diagnostic rather than committing the full program immediately. The diagnostic should produce usable assets: a prioritized technical backlog, a query and page map, an AI-prompt observation method, an editorial workflow, a measurement plan, and an initial delivery sequence. Make those outputs yours under the agreement so the work remains useful even if you choose a different implementation partner.

    Key takeaways for the hiring decision

    • There is no universal best SEO agency for AI companies. The right choice depends on whether discovery, category education, product comprehension, conversion, launch trust, or channel coordination is constraining growth.
    • Route agencies by their actual operating strength. SEO and GEO, brand and UX, PR and reputation, experimentation, and integrated performance marketing solve different problems.
    • Evaluate the named delivery team. Company size, founding year, client logos, and review averages are screening signals, not evidence that the people assigned to you can do the work.
    • Require page-level SEO proof and a repeatable AI-visibility method. Rankings, mentions, citations, referrals, and influenced conversions should not be reported as if they are the same event.
    • Send every candidate the same brief and compare diagnosis, measurement, staffing, implementation, editorial controls, and commercial terms.
    • Protect your access, data, content, accounts, measurement setup, and handover rights before work starts.

    Your next move is to write the one-page brief before booking another sales call. Put the primary bottleneck at the top, define the buyer action that matters, and list the evidence an agency must provide. Send it only to a small, role-matched shortlist. The quality of the answers will tell you far more than another round of polished capability slides.

    References

  • Transforming Client Pressure into Growth: Insights from Andrea Cruz

    Transforming Client Pressure into Growth: Insights from Andrea Cruz

    On episode 341 of PPC Live The Podcast, I had the pleasure of chatting with Andrea Cruz, Head of B2B at Tinuiti. We delved into a challenge that many senior marketers face: the struggle of providing immediate answers when clients press for details without prior notice.

    We explored how missteps in communication can amplify client stress, and how adopting a proactive mindset can turn these challenges into pivotal moments of growth in one’s career.

    As Cruz progressed from a hands-on marketer to leading entire teams, she encountered the challenge of advocating for projects she wasn’t directly managing daily. This shift brought new struggles, especially when clients questioned campaign performance or outcomes.

    In those moments, freezing or delaying responses can damage trust. Cruz realized that senior leaders must offer clear direction, even without knowing every detail, to maintain confidence in discussions.

    Through her experiences and mentorship, Cruz honed a technique for buying time without losing trust: asking thoughtful questions. This strategy not only buys time but also ensures that the responses are precise and address the core of the client’s concerns.

    Her method includes asking clients to clarify expectations, requesting additional context, and confirming their understanding. This approach is crucial, especially in emotionally charged situations, and, for Cruz, it allowed her to manage complex conversations effectively despite being a non-native English speaker.

    At Tinuiti, the focus is on a solutions-driven culture over assigning blame. By addressing ‘Where are we now?’ and ‘How do we get where we want to be?’, teams foster a safe space to discuss errors and learn from them. Cruz believes that leaders should set the standard by openly sharing their own mistakes.

    Cruz advocates for proactive communication, urging teams to address issues before clients notice. Tailoring communication styles to client preferences fosters stronger relationships and transforms agencies into strategic partners.

    Common mistakes in B2B advertising include spreading budgets too thin and underfunding campaigns. Cruz emphasizes that it’s better to focus on fewer channels with adequate resources to avoid ineffective outcomes.

    Regarding AI, Cruz warns against limiting its use to basic tasks and shares how her team is leveraging AI for advanced operations, enhancing strategic execution.

    Cruz’s message is clear: growth requires preparation and a willingness to adapt. By anticipating client needs and embracing experimentation, marketers can turn pressure into golden opportunities.


    Inspired by this post on Search Engine Land.


    crushpress.ai community screenshot
  • SaaS AI Referral Traffic Is Down: A Practical Diagnostic

    SaaS AI Referral Traffic Is Down: A Practical Diagnostic

    Your SaaS dashboard shows fewer visits from AI assistants. Before you rewrite the content roadmap or declare the channel dead, find out exactly which line moved. A fall in standalone-assistant referrals, a shift toward workflow-embedded tools, and poor landing-page routing are three different problems. They require three different responses.

    The goal isn’t to recover every lost session. It is to make your product easy to retrieve at the right moment, send qualified users to a page that resolves their question, and measure whether those visits produce meaningful actions.

    Key takeaways

    • A decline in attributed AI referrals is not the same as a decline in AI visibility. Referral analytics capture recognized visits, not every citation, recommendation, or answer that produces no click.
    • The widely discussed 53% decline applied to standalone AI discovery sessions in one SaaS dataset. It occurred while workflow-embedded Copilot traffic grew by more than 20 times, so the pattern is better read as channel redistribution than universal disappearance.
    • Internal search deserves its own landing-page segment. About 41% of the dataset’s LLM sessions landed on search-result pages, which can reveal that an assistant could not identify a better direct answer.
    • Compare equivalent buying periods. The dataset peaked in July and weakened through Q4, making a simple month-over-month chart especially easy to misread.
    • Prioritize landing-page relevance, qualified actions, referrer mix, and content penetration. Total sessions alone cannot tell you whether your AI search strategy is improving.

    Read the decline as a distribution problem first

    The 53% figure does not establish that every SaaS company lost half its AI audience. It describes a decline in discovery sessions from standalone AI tools within a particular dataset. Between November 2024 and December 2025, that dataset recorded 774,331 sessions attributed to large language models.

    Its referrer mix was highly concentrated: ChatGPT accounted for 82.3% of the sessions. When one platform supplies that much traffic, a change in its usage, interfaces, link behavior, or audience mix can dominate the aggregate chart. A top-line decline can therefore hide growth elsewhere.

    Copilot demonstrates the point. It generated 148 sessions near the end of 2024, grew by more than 20 times by May 2025, and then averaged 3,822 sessions per month from June through December. It had become the second-largest AI referrer by the end of 2025.

    The pattern is consistent with intent moving into the user’s existing workflow. Someone already working in an embedded assistant may ask a product or implementation question without opening a separate discovery tool. That does not settle the larger question of whether agents will replace parts of SaaS. It does tell you that measuring all AI platforms as one homogeneous channel will produce poor decisions.

    Start by classifying the shape of your own decline:

    Pattern in your analyticsWorking interpretationNext check
    Standalone assistants fall while an embedded assistant growsReferrer mix is changingCompare landing pages, intent, and conversion by platform
    AI and other non-paid channels weaken in the same periodDemand or B2B seasonality may be involvedCompare equivalent periods and commercial outcomes
    AI sessions increasingly land on internal searchAssistants may not be resolving a direct destinationInspect the query, result quality, and crawl path
    AI sessions fall but qualified actions hold steadyLost visits may have been lower-value, or attribution may have shiftedReview conversion counts, not only conversion rate
    Sessions hold steady while qualified actions fallLanding-page relevance or intent quality has deterioratedAudit the promise-to-page match for the affected referrers

    These are diagnostic hypotheses, not conclusions. Use them to choose the next report or page inspection rather than to explain the result in advance.

    Audit measurement before changing your content

    A magnifying lens reveals a hidden signal path beside an abstract attribution funnel and tracking nodes on an analyst workstation.

    An analytics tool’s AI channel is a record of identifiable referrals. It is not a complete count of how often an assistant mentions your company, uses your information, recommends your product, or answers a question without sending a visit. Call the metric what it is: attributed AI referral sessions.

    Lock the channel definition

    Export the referrer rules behind your AI segment. Keep the same platform list, source normalization, bot filtering, and session definition throughout the comparison. If you add a newly discovered referrer halfway through the audit, recalculate the earlier period under the same rule set. Otherwise, taxonomy maintenance will look like growth.

    Keep an explicit “unknown or unclassified” bucket. Do not silently assign direct traffic to AI just because a visitor viewed an AI-oriented page. That may be a useful hypothesis for investigation, but it is not referrer evidence.

    Build a platform-by-page-type view

    For each complete month, split AI referrals by platform and landing-page template. At minimum, separate the homepage, product or feature pages, pricing, comparisons, documentation, blog content, and internal search results. Preserve the full landing URL in the underlying export so query parameters do not disappear inside a grouped page report.

    This matrix exposes changes that a channel total conceals. ChatGPT might stop sending exploratory blog visits while Copilot begins sending fewer but more commercial visits to product documentation. Calling that a single traffic decline would erase the useful part of the change.

    Use seasonally comparable periods

    SaaS discovery in the observed dataset peaked in July and declined through Q4, alongside normal B2B work, budget, and holiday cycles. That is not a universal calendar for every SaaS company. It is a warning against treating an autumn-to-December decline as proof of an AI-specific loss.

    Compare the same quarter year over year when you have consistent data. If you do not, compare AI referrals with non-paid search, direct visits, demo activity, and other demand indicators over the same months. A decline shared across channels points toward a different diagnosis than an isolated fall from one AI platform.

    Measure penetration, relevance, and outcomes

    Create a small scorecard with definitions your team can reproduce:

    • Referrer share: each AI platform’s sessions divided by all attributed AI referral sessions. This shows concentration and redistribution.
    • Landing-page relevance rate: AI sessions reaching a page that directly answers the apparent intent divided by all AI sessions. Define the intended destination for each query or intent class before scoring it.
    • Commercial action rate: trials, demos, sign-ups, or another agreed activation event divided by AI sessions. Report the action count beside the rate so a tiny denominator does not mislead you.
    • AI landing-page penetration: eligible product, comparison, pricing, and answer pages receiving at least one attributed AI visit divided by all eligible pages. Use this as an internal coverage metric, not an industry benchmark.
    • Search-result dependency: AI sessions landing on internal search divided by all AI sessions. A rising share deserves a query-level inspection even when total traffic is stable.

    Keep visibility and referral performance as separate columns. If you monitor assistant mentions or citations, compare them with clicks rather than combining them into an invented all-purpose score. Visibility can remain stable while click behavior changes.

    Treat internal search landings as a retrieval clue

    A search beam selects one webpage tile from a floating digital library and connects it to a brightly lit destination doorway.

    Internal search was the largest destination class in the observed traffic. Search-result pages received 320,615 sessions, or about 41% of all LLM referrals, exceeding blog, pricing, and product destinations.

    That does not mean internal search was the best content. A more useful interpretation is that the assistant found a searchable route but not a confident direct answer. Your search interface became a fallback discovery layer.

    Open the top AI-referred search URLs and inspect them as a user and as a crawler:

    • Reproduce the query from the landing URL. Confirm that it returns relevant results rather than an empty state, generic category, or different query after a redirect.
    • Check whether the public result can be fetched without authentication, cookies, or a browser-only interaction. If useful results appear only after client-side execution, provide a crawlable path to the primary answer.
    • Expose the query, result summary, and important destination links in visible HTML. A search shell with no meaningful server response gives an assistant little to interpret.
    • Verify the status code, robots directives, canonical target, and rendering behavior. A result page should not claim to be a successful answer while returning an error, canonicalizing to an unrelated page, or hiding every result from crawlers.
    • Trace each recurring high-intent query to its best permanent destination. If people repeatedly search for pricing, a named integration, a comparison, or a specific capability, create or improve the dedicated page and link it prominently.
    • Make the onward path explicit. A useful result should lead directly to the relevant product, pricing, comparison, documentation, or contact page instead of forcing another search.

    Do not respond by indexing every possible internal-search combination. Unlimited query parameters, spelling variants, and empty result sets can create a large collection of duplicate or low-value URLs. Keep crawlable search states finite and useful. Promote recurring, commercially meaningful questions into governed landing pages with stable URLs, original answers, and intentional internal links.

    Think of public search as an interface an AI system may use, not as a substitute for information architecture. If the same search query repeatedly attracts referrals, the durable fix is usually a direct answer page that no longer requires the fallback.

    Rebuild around moments of intent, then test one cycle

    Workflow-embedded assistants change when discovery happens. The user may already be writing a specification, comparing tools, diagnosing an integration, or preparing a purchase request. Your page has to resolve that immediate task. A broad brand narrative is rarely enough on its own.

    User’s moment of intentBest destinationInformation that must be visible
    “What does it cost?”Pricing or plan pagePricing basis, plan differences, limits, conditions, and the next buying step
    “Can it handle this use case?”Capability or use-case pageDirect answer, supported inputs, prerequisites, limitations, and a relevant example
    “How does it compare?”Comparison pageDecision criteria, material differences, suitability, migration considerations, and current facts
    “How do I complete this task?”Documentation or task pagePrerequisites, ordered steps, expected result, failure points, and the appropriate next action
    “Where is the relevant feature or resource?”Help, navigation, or curated search pageExact destination, concise context, and direct links without another discovery loop

    Make critical facts available in the main page content. Do not leave pricing conditions, compatibility, product limits, or differentiators only inside images, tabs that never render for a crawler, or downloadable collateral. Clear headings, concise answers, comparison tables, and descriptive internal links make the page easier for people and retrieval systems to interpret. The broader SaaS pattern favors transparent, crawlable, comparison-oriented information.

    Use structured data to clarify, not manufacture, the answer

    JSON-LD should describe the content a visitor can verify. Use the most accurate entity types for the page, such as Organization and SoftwareApplication where they genuinely apply. Represent offers only when the visible pricing information is current and complete enough to support them. Use FAQPage only for questions and answers that are actually present for the reader, and BreadcrumbList only when it reflects the real hierarchy.

    Keep names, URLs, product descriptions, and relationships consistent between markup and visible copy. Do not stack loosely related schema types in the hope of earning AI visibility. Structured data can reduce ambiguity; it cannot repair a missing price, an evasive comparison, an inaccessible result, or an unsupported claim.

    Run a controlled repair cycle

    1. Freeze the baseline. Save monthly sessions, referrer share, landing-page type, search-result dependency, qualified actions, and your current channel rules.
    2. Choose pages from three evidence-backed groups: high-intent pages receiving no AI referrals, internal-search URLs receiving AI referrals, and pages that attract visits but fail to resolve the apparent intent.
    3. Repair the answer path. Put decisive facts in visible content, connect recurring searches to permanent destinations, improve internal links, and align JSON-LD with the finished page.
    4. Annotate the publication and crawl dates. Keep unrelated template and attribution changes out of the same evaluation window where practical.
    5. Review one complete reporting period using the frozen definitions. Compare platform mix, relevant landings, action counts, and search dependency before looking at the aggregate traffic line.

    The decision after that cycle should follow the observed failure. If one referrer is shrinking while another is growing, adapt destinations to the growing moment of intent. If search-result dependency is rising, repair retrieval and information architecture. If comparable periods weaken across several acquisition channels, do not blame AI alone. If qualified actions hold while raw visits fall, protect the pages producing those actions before chasing volume.

    Your first move can be small: open a platform-by-page-type report, select the highest-traffic internal-search landing, and follow its path to the page that should have answered the query directly. Repairing that path gives you a measurable change. A generic push to publish more does not.

    References

  • The Medtech Marketing Agency Landscape: A 2026 Guide

    The Medtech Marketing Agency Landscape: A 2026 Guide

    You can waste a substantial budget on a capable medtech marketing agency if it solves the wrong problem. A trade show specialist, brand studio, account-based marketing team, enterprise media firm, and organic authority partner can all make persuasive pitches, but they are built for different jobs.

    Your first decision is therefore not which agency is best. It is which commercial constraint must change next. Once you name that constraint, the medtech agency landscape becomes much easier to navigate.

    Choose the bottleneck before you choose the agency

    Write a one-sentence diagnosis before you schedule discovery calls: “Our immediate constraint is [problem], among [audience], at [stage of the buying journey], and progress means [business outcome].” If your team cannot complete that sentence, an agency will fill the gap with the services it already sells.

    Route your search according to the job that needs to be done:

    • You need sustained discovery and qualified inbound demand. Look for thought leadership, technical content, SEO, and generative engine optimization. The agency should be able to connect visibility with a defined conversion path, not merely publish content.
    • You need paid reach at enterprise scale. Look for media buying, audience data, analytics, creative production, landing-page support, and a clear handoff into your CRM and sales process.
    • Your product is difficult to explain or your company is preparing to raise capital. Start with positioning, message architecture, visual identity, and materials that can be used consistently in customer and investor conversations.
    • A conference or trade show is the immediate commercial event. A booth specialist can solve the physical experience, but your scope also needs lead capture, meeting preparation, and post-event follow-up.
    • Your market consists of a finite group of valuable organizations. Account-based marketing is the natural lane. The agency must show how marketing and sales will coordinate around named accounts and multiple stakeholders.
    • You need a coordinated device launch or brand program across several channels. An integrated medtech agency may reduce handoff friction, provided it has genuine depth in the channels that matter to you.

    Do not treat “full service” as automatically better. Breadth helps when your problem crosses channels. It creates unnecessary cost and management overhead when you only need a specialist intervention.

    Seven agencies occupy distinct positions in the 2026 landscape

    Seven different agency work areas surround a central diagnostic device, with each area represented by tools for a distinct marketing specialty.

    The profiles below reflect a market snapshot updated January 26, 2026. Use them as routing information for a shortlist, not as a substitute for current due diligence. Company size, staffing, client relationships, and service emphasis can change.

    AgencyPrimary laneReported organizational contextWhat you should verify
    First Page SageThought leadership combined with SEO and GEO for lead generationFounder-led; founded in 2009; reported size of 100-250; named work includes Biovia and AltoidaAsk how search visibility, visibility in generative answers, and content engagement connect to qualified lead definitions. Expect a detailed onboarding process and confirm what your subject-matter experts must contribute.
    EpsilonEnterprise, full-service marketing with a concentration in paid advertising and data analyticsNot founder-led; founded in 1969; reported size of 1,000+; named work includes Visionworks and WalgreensClarify the dedicated delivery team, minimum viable scope, data requirements, and total operating cost. Enterprise capacity has little value if your account receives a generic team or more infrastructure than it needs.
    Parker WhiteBrand development and creative marketing for medical and lifestyle brands, including B2C and B2B workFounder-led; founded in 1997; reported size of 11-50; named work includes Orthofix and FUJIFILM SonositeIf pipeline is the goal, ask who owns distribution, conversion, and measurement after the brand work is finished. A strong identity is not automatically a demand-generation system.
    Distill HealthBrand strategy and visual identity for medtech companies preparing for fundingFounder-led; founded in 2018; reported size of 1-10; named work includes Theragen and NuvaraConfirm capacity, access to senior staff, the customer or investor validation process, and who executes the brand after fundraising preparation. No marketing agency can promise that branding will secure funding.
    ExponentsTrade show booth design, manufacturing, and installationNot founder-led; founded in 1985; reported size of 11-50; named work includes HealthGridDefine the boundary between booth delivery and campaign delivery. Assign responsibility for pre-event outreach, appointments, lead qualification, data capture, and follow-up to Exponents, another partner, or your internal team.
    The ABM AgencyOmnichannel account-based marketing for high-value organizational buyersFounder-led; founded in 2007; reported size of 11-50; named work includes MedPost and Care SpotAsk how accounts are selected, how buying-committee roles are mapped, what sales must do, and how engaged accounts become opportunities. Also clarify cost before assuming ABM is efficient for your market.
    IcovyIntegrated branding, multimedia, and traditional marketing for medical device companiesFounder-led; founded in 2019; reported size of 11-50; named work includes Poba Medical and Kaneka MedicalIdentify the named specialist for every channel in your scope. Determine what is delivered in-house, what is subcontracted, and who owns integration, reporting, and corrective decisions.

    These firms are not interchangeable entries in a league table. Epsilon’s enterprise scale does not make it the natural choice for a startup that needs investor-ready positioning. Distill Health’s funding-oriented brand work does not make it the default choice for a mature manufacturer seeking paid media at scale. Exponents may be highly relevant to a conference deadline while remaining intentionally narrow outside the trade show itself.

    Founder involvement, company age, and headcount are context rather than outcomes. A founder-led specialist may offer direct senior attention, but you still need to know who will perform the weekly work. A large firm may provide broader capabilities and resilience, but you still need a dedicated team with relevant experience.

    Turn agency credentials into evidence of fit

    Two people evaluate unbranded project samples, process materials, and a medical device prototype on a conference table.

    For initial market screening, notable clients carry 35% of the evaluation, founder status and leadership experience 20%, company age and employee tenure 15%, marketing approach 15%, reviews 10%, and media references 5%. Those inputs are useful, but your buying decision should test what each signal actually means for your assignment.

    • Client names establish adjacency, not success. Ask what the agency delivered, which audience it addressed, how long the work ran, and what changed. A recognizable logo can represent a small project that bears little resemblance to your scope.
    • Relevant similarity is multidimensional. Product category alone is not enough. Compare the buyer, sales motion, company stage, geographic scope, channel, and internal review process. A consumer campaign and a hospital-enterprise sale can require very different work even when both sit under the medtech label.
    • Leadership experience matters only if it reaches delivery. Ask who joins the pitch, who designs the strategy, who manages the account, and who creates the work. Get those roles into the scope. Do not assume the founder or senior strategist in discovery will remain involved.
    • Tenure is a continuity clue. Within this group, reported median employee tenure ranges from 1.7 years at The ABM Agency to 4.6 years at Epsilon. That does not prove quality, but it gives you a reason to ask about turnover, backup coverage, and knowledge transfer.
    • Reviews require context. Look for comments about the type of work you are buying, responsiveness when a campaign underperforms, and the quality of project oversight. A high average without detail cannot tell you whether the agency can solve your problem.
    • Media references indicate visibility, not operational competence. They can support an authority assessment, but they do not replace current work samples, named team members, a delivery plan, or access to reporting.

    Ask every shortlisted agency to walk through a documented engagement that resembles your situation. Have it explain the starting constraint, its exact scope, the client responsibilities, the approval path, the deliverables, and the business result. If the answer skips from a client logo directly to an outcome, the missing middle is where delivery risk usually sits.

    Medtech work also needs an explicit claims-review workflow. Your internal medical, legal, regulatory, or quality reviewers may own approval, but the agency must know when review occurs, how revisions are tracked, and which version is cleared for each channel. If this process remains vague, timelines and budgets can deteriorate after production begins.

    Write a scope that matches the agency lane

    A useful brief does more than list services. Use this structure: “Help [audience] move from [current state] to [conversion or commercial outcome] by producing [deliverables], distributing them through [channels], and reporting [business and diagnostic measures].” Add your approval roles, required systems, ownership terms, dependencies, and exclusions.

    For SEO, thought leadership, and GEO

    Name the technical themes, buyer questions, priority audiences, conversion events, subject-matter experts, and owned properties in scope. Require the agency to distinguish traditional search performance from observed brand inclusion or citation in generative answers. Both can contribute to discovery, but they are not the same measurement.

    Qualified organic inquiries, target-account visits, completed demo or consultation requests, coverage of problem-led searches, and observed AI-answer visibility are more useful together than traffic alone. Traffic remains a diagnostic measure. It is not proof that the right buyer understood the product or entered a sales conversation.

    For paid media and integrated campaigns

    Specify the audience data, media channels, creative formats, landing pages, tracking, CRM handoff, and approval workflow. Decide who owns media accounts, analytics access, campaign data, source files, and website changes. Your organization should retain administrative access to the systems and assets it is paying to build; losing access can make a future agency transition expensive and slow.

    Make qualified opportunities and pipeline the commercial measures when your sales cycle supports them. Use accepted leads, qualified conversations, landing-page conversion, and acquisition cost as operating indicators. Click-through rate and impressions can diagnose a campaign, but they should not become substitutes for business progress.

    For account-based marketing

    Define how target accounts enter the program, which stakeholder roles matter, what sales will do, which messages vary by role, and how engagement is recorded. ABM fails quietly when marketing runs account-targeted ads while sales follows an unrelated list and neither side owns the handoff.

    Track meaningful engagement across the buying group, meetings with relevant roles, account progression, opportunities, and pipeline. Raw account impressions are not enough. Your agency should also explain what evidence causes it to intensify, change, or stop work on an account.

    For branding, fundraising preparation, and trade shows

    A brand scope should name the positioning decision, message architecture, visual system, required customer or investor materials, validation method, and internal approvers. Define how the system will reach the website, sales materials, presentations, and campaigns. Otherwise, you can finish with an attractive identity that the commercial team cannot apply consistently.

    A trade show scope should connect the physical booth with pre-event outreach, meeting booking, on-site data capture, lead qualification, CRM entry, and follow-up. If the booth provider does not offer those services, assign them elsewhere before the event. Booth traffic is an incomplete result; qualified conversations and subsequent opportunities are the commercial test.

    In every lane, separate agency deliverables from client dependencies. Technical interviews, product access, approved claims, customer references, CRM configuration, and executive sign-off can all sit with your team. Put each dependency beside an owner and approval path so neither side can hide a preventable delay inside a status report.

    Key takeaways: use the pitch to expose delivery risk

    • State the bottleneck first: What precise commercial constraint will this engagement change, and which business outcome will show that it changed?
    • Interrogate the closest example: Which past engagement most closely matches your buyer, product stage, sales motion, and channel? What did the agency itself deliver?
    • Name the working team: Who owns strategy, account management, content or creative production, media, analytics, and claims coordination after the pitch?
    • Expose outside dependencies: Which services are subcontracted, which require another partner, and which depend on your internal experts or systems?
    • Map the approval process: When do technical and claims reviews happen, who resolves conflicting feedback, and how are approved versions controlled?
    • Protect ownership: Who owns the ad accounts, analytics properties, audience data, CRM records, domains, website access, source files, and finished assets?
    • Demand decision-grade reporting: Which measures represent commercial outcomes, which are leading indicators, and which merely diagnose activity?
    • Set correction rules: What evidence will cause the agency to change the message, channel, audience, budget allocation, or scope?

    Send the same written brief to every agency on your shortlist and insist that each response addresses the same outcome, responsibilities, evidence, and ownership terms. That makes proposals comparable and prevents a polished pitch from redefining your problem around an agency’s preferred services.

    Choose the partner whose lane matches your immediate constraint, whose relevant work survives detailed questioning, and whose named team can explain how delivery becomes a measurable business result. That is a stronger basis for a decision than rank, reputation, or breadth alone.

    References