Categorías
Blog post

ChatGPT Ads Are Self-Serve in Spain: Should a B2B SaaS or a D2C Brand Test Them?

Paid Media · New Channel

Since 31 August 2026, anyone with a Spanish company and a credit card can open OpenAI’s Ads Manager and buy ads inside ChatGPT. No sales team, no agency partner, no minimum spend. Self-service went live across 31 European markets at once — Spain, Germany, France, Italy, the Netherlands, the Nordics — six months after the US pilot started in February.

I have spent the last two weeks reading the actual documentation rather than the hot takes, and the honest summary is this: ChatGPT Ads is a real channel with real measurement plumbing, and it is also a channel where most of the people who see your ad are on the free tier, in a conversation you cannot see, being matched by a system you cannot audit. Both things are true. The question for a Spanish B2B SaaS or a D2C brand is not «is this the future», it is «what would a €1,500 test have to prove before I put it in the media plan».

This is how I would set that test up, what I would instrument first, and where I expect it to overlap with the Google Search budget you already run.

What actually went live in Spain on 31 August — and what did not

OpenAI’s timeline, from its own announcements: US test on 9 February 2026, logged-in adults on the Free and Go tiers only. Canada, Australia and New Zealand in spring. UK, Mexico, Brazil, Japan and South Korea on 11 August. Then the European announcement on 18 August, with self-serve access through Ads Manager confirmed on 31 August. On 31 August OpenAI also reported the platform had passed a $1 billion annualised run rate in under 200 days — which tells you the US advertisers who got in early did not leave.

What you get in the account today, per the developer docs and the September product email: CPM and CPC bidding plus a conversion-optimised objective; geo-targeting and custom audiences built from hashed emails, phones or mobile ad IDs; a JavaScript measurement pixel, a no-JS image tag and a server-side Conversions API; product-feed campaigns for retailers, which serve in a multi-product carousel; total-budget pacing; and — new on 4 September — an Ads Manager plugin that lets you build and edit campaigns from inside ChatGPT itself.

What you do not get: any view of the conversation your ad appeared in. Advertisers receive aggregate views and clicks, nothing else. That is a deliberate design choice, stated in every OpenAI ads document since February, and it is the single biggest difference between this and a search-terms report.

Recency check: a lot of September coverage recycles the February pilot as if it were new. The dates that matter for a Spanish advertiser are 18 August (announcement) and 31 August (self-serve live). Anything describing «coming soon to Europe» is stale.

Who actually sees a ChatGPT ad, and why it changes your forecast

Ads are only shown to users on the Free and Go plans. Plus, Pro, Business, Enterprise and Education accounts never see them, and Free users can opt out of ads in exchange for fewer daily messages. Ads are not served to anyone under 18 or predicted to be, and they are not eligible near health, mental health or political topics.

Read that as a media planner and three things follow. First, the audience skews away from the people who pay for software — the CFO of a mid-market company evaluating a finance tool is more likely on a Business seat than on Free. Second, the exclusions are broad enough that entire categories (supplements with any health claim, for instance) will find inventory thin or unpredictable. Third, ad selection is driven by the topic of the current conversation, the user’s past chats and their past ad interactions. Your ad appears when someone is talking about your category, which is a stronger intent signal than a display impression and a weaker one than a typed search with commercial modifiers.

So the right mental model is not «Google Search but in ChatGPT». It is closer to an intent-matched mid-funnel placement with a free-tier skew. That is not a criticism; it is what you should be pricing when you set a target CPA for the test.

How to instrument it before you spend a euro

Every failed channel test I have seen failed at measurement, not at the channel. ChatGPT Ads gives you three tracking paths that all report to one Pixel ID, and the order you set them up in matters.

Before launch Why it matters
Measurement Pixel via GTM with the standard events you already fire for Meta and Google Conversion-optimised bidding needs a conversion signal. Launch on CPC without the pixel and you have a traffic campaign, not a test.
Conversions API from the backend (or via your HubSpot / Shopify server events) with hashed email and phone Browser-side matching alone will under-report, exactly as it does on Meta. September added more matching fields (name, region, postal code, GAID); use them.
A dedicated UTM source (utm_source=chatgpt&utm_medium=paid) and a custom channel group in GA4 Without it, ChatGPT traffic lands in Referral or Unassigned and you will never see it against the rest of the mix.
A landing page that answers the conversation, not the keyword The user arrives mid-comparison. A page that opens with «why choose us over X» outperforms a generic homepage every time.
A holdout in the CRM: a flag on every ChatGPT-sourced contact Platform-reported conversions will not tell you whether the leads closed. Your pipeline report will, eight weeks later.

One more thing the docs are explicit about: a view-through conversion model is «coming soon», billed on impressions and optimised on both clicks and views. When it arrives, keep it out of the test. A first test needs a clean click-based read; view-through attribution is where new channels go to look better than they are.

A €1,500 test that proves something: B2B SaaS versus D2C

The two kinds of clients I run paid media for need different tests, because the channel treats them differently.

For a B2B SaaS — say a finance-automation tool selling to founders and CFOs — the honest hypothesis is not «ChatGPT will produce demos at a lower CPA than Google». It is «people who ask ChatGPT how to structure their company’s cash-flow reporting are in our ICP, and we can reach them before they type a branded search». So: one campaign, conversion-optimised toward a soft conversion (guide download or pricing page view, not demo booked), custom audience exclusion built from current customers, geo Spain plus your two best EU markets, three ads that each answer one specific question. Success at €1,500 is not a demo. It is a cost per qualified contact within 1.5× of your LinkedIn Ads number and a CRM flag you can follow for two months.

For a D2C brand — a daily nutritional beverage, a coffee subscription — the channel is closer to Shopping than to Search, and the product feed is not optional: since early September, product-level results in ChatGPT come from brands that submit a feed, and feed campaigns serve in the carousel unit with per-card impression and click reporting. The test is a feed campaign on conversion optimisation with the Pixel plus Shopify server events, a custom audience of past purchasers for exclusion, and a hard rule on claims: anything that reads as a health benefit risks being ineligible near health topics, so lead with taste, ritual and convenience. Success is a blended ROAS you would accept from a Meta prospecting campaign, on a channel where the comparison is happening in the chat instead of on your PDP.

The key idea: ChatGPT Ads rewards advertisers who know which question their customer asks right before they buy. If you cannot write that question down, you are not ready to test the channel — and no bid strategy will fix it.
Want a second opinion before you open the account? I am setting these tests up for clients this quarter — pixel, CAPI, UTM structure and the CRM flag included — so the read at the end is one you can actually trust. Tell me what you sell and I will tell you whether a test is worth it yet.

Where it cannibalises Google Search, and where it does not

The uncomfortable part of any new channel is that it rarely brings new demand; it usually moves existing demand somewhere you now have to pay for. Two checks tell you which is happening here.

Watch branded search volume. If ChatGPT exposures push people to Google your brand, your Search campaign gets the conversion and ChatGPT looks like it did nothing. The ChatGPT-sourced CRM flag plus a look at brand impressions in the two weeks after launch will catch this. It is the same pattern we described when Smart Bidding started absorbing cross-channel signals: the platform that closes claims the credit.

Watch the non-brand long tail. Search queries have been getting longer for eighteen months, and the people typing five-word questions into Google are the same people asking ChatGPT. If your Google non-brand conversions dip in the test geo while ChatGPT-sourced contacts appear, you are paying twice for the same person. That is not a reason to stop; it is a reason to set the ChatGPT target CPA at what a Google long-tail conversion costs you, not at what a display click costs.

And a caveat on the organic side: paid presence in ChatGPT does nothing for whether ChatGPT cites you in an answer. Ads are labelled, separated, and do not influence responses. If being cited is the goal, that is a content and structure problem — the same one Google AI Mode created — and the ad budget will not buy it.

Questions I keep getting asked

Can a company in Spain advertise on ChatGPT right now?

Yes. Self-service access through OpenAI’s Ads Manager has been live in Spain and 30 other European markets since 31 August 2026. You sign up at ads.openai.com; there is no agency requirement and no published minimum spend.

Who sees ads in ChatGPT?

Only logged-in adult users on the Free and Go plans. Plus, Pro, Business, Enterprise and Education users never see ads. Ads are not shown near health, mental health or political topics, and Free users can opt out in exchange for fewer daily messages.

How is a ChatGPT ad targeted?

Ads are matched to the topic of the current conversation, the user’s past chats and their past ad interactions. Advertisers can add geo-targeting and custom audiences (hashed email, phone, mobile ad IDs), but never see the conversation itself — only aggregate views and clicks.

Do ChatGPT Ads help my brand get cited in ChatGPT answers?

No. OpenAI states that ads do not influence answers and are always labelled and visually separated. Being cited organically depends on your content, structure and authority, not on ad spend.

Test it like a channel, not like a headline

The temptation with anything that has «ChatGPT» in the name is to either dismiss it or to announce it. Neither is a media decision. The platform has shipped the pieces a serious advertiser needs — conversion bidding, server-side measurement, audience matching, feed support, an API — faster than any ad network I can remember. It has also, by design, given you less visibility into why an ad served than any channel you currently buy.

So run it the way you would run any unproven placement: instrument first, cap the budget, define the success metric before launch, flag every contact in the CRM, and read the result against your Google long-tail and your LinkedIn or Meta prospecting numbers rather than against zero. If it earns a line in the 2027 plan on those terms, it earned it. If it does not, you have spent €1,500 to know something most of your competitors are still guessing about.

Want the test run properly?

I set up ChatGPT Ads pilots end to end for B2B SaaS and D2C brands in Spain: account and Pixel/CAPI instrumentation, UTM and GA4 channel setup, audience exclusions, three-ad creative brief, CRM flagging, and a written read-out at the end of the budget that tells you whether to scale or stop.

Book a ChatGPT Ads pilot

Nacho Hernandez

Nacho HernandezMarketing & Business Consultant · Studio IdeagoLinkedIn →
Categorías
Blog post

Your Lifecycle Stages Aren’t the Problem. Your Exit Criteria Are.

CRM · RevOps

Every stalled CRM implementation I have been called into had a lifecycle stage model. Usually a good one. Subscriber, Lead, MQL, SQL, Opportunity, Customer — the same six words, sitting in the same dropdown, in HubSpot or Salesforce or whatever else.

The stages were never the problem. What was missing, every single time, was the boring part underneath: who decides a contact has left this stage, on what evidence, and what happens the moment they do. Without that, a lifecycle stage is a label someone types in when they remember. Reporting built on it is fiction, and everybody in the room quietly knows it.

This is the model I actually implement, and the four questions I make a team answer per stage before we touch a single property in the CRM.

Lifecycle stage and lead status answer different questions

Start here, because conflating these two fields causes more damage than any other CRM mistake I see, and it is completely free to fix.

Lifecycle stage answers: how far into the relationship is this person? It moves forward, it is owned by the business as a whole, and it is what you report the funnel on. Lead status answers: what is happening in the work right now? New, attempting contact, connected, unresponsive, unqualified. It bounces around, it is owned by whoever is working the record, and it is what a rep looks at on Monday morning.

When teams collapse the two, you get lifecycle stages like «Attempting to contact» and «Nurture» sitting in the same dropdown as MQL and Customer. The funnel report then counts a stalled call attempt as a funnel position, conversion rates between stages become uninterpretable, and nobody can answer the only question the model exists to answer: of the people who reached this point, how many reached the next one, and how long did it take?

The tell: if your lifecycle dropdown has more than seven options, or if any of them is a verb, you have work statuses living in a funnel field. Split them before you do anything else on this list.

Every stage needs four things, and most have one

Most implementations define what a stage means and stop there. A stage is only operational when all four of these exist in writing:

What it needs The question it answers
A definition What is true about a person who is here? Written so two people in different teams classify the same record identically.
An exit criterion What specific, observable event moves them out? Not «shows interest» — a form, a threshold, a meeting held, a stage change on a deal.
An owner Who is accountable while the record sits here, and who is accountable for the transition itself? Those can be two different people.
A timestamp A date property written when the record enters. Without it you cannot measure stage velocity, and velocity is where the actual diagnosis lives.

The exit criterion is the one that does the work. «MQL means a marketing-qualified lead» is a tautology. «MQL means fit score is 60 or above and the contact has either requested a demo or hit 3 pricing-page views in 14 days» is a rule a workflow can execute and a sales director can argue with — which is exactly what you want, because the argument happens once, in a room, instead of every week in the pipeline review.

The timestamp is the one everybody skips and later wishes they had. Entry dates per stage are what let you say «MQL to SQL takes 19 days and 40% never make it» instead of «the funnel feels slow». They cost nothing to add on day one and cannot be reconstructed retroactively.

Fit and intent are two scores, not one

The single most common scoring failure: one number, built by adding points for job title to points for email opens. A CFO at a perfect-fit company who has visited twice scores the same as a student who downloaded four PDFs. The model cannot tell you which one to call, because the two inputs mean opposite things.

Fit is who they are — industry, size, role, geography, tech stack. It is slow-moving and mostly firmographic. Intent is what they are doing — pricing page, demo request, repeat sessions, reply to a sequence. It is fast-moving and it decays. Keep them as two properties and the routing logic writes itself:

High fit · high intentSales, now. This is the only quadrant that should trigger an SLA.
High fit · low intentMarketing nurture, and the highest-value list you own. Do not let sales burn it with cold sequences.
Low fit · high intentSelf-serve, community, or politely nothing. The quadrant that quietly consumes the most rep hours.
Low fit · low intentDatabase. Measure it, do not work it.

Two more rules that save scoring models from themselves. Intent must decay — a pricing visit from March should not still be inflating a score in September, and a model without decay slowly promotes your entire database. And negative scoring should be structural, not behavioural: subtract for a competitor domain, a student email, a country you do not sell into. Subtracting points because someone did not open an email punishes the email, not the lead.

The key idea: a lifecycle model is not a taxonomy, it is a set of agreements about who acts when. If a stage has no exit criterion and no owner, it is not a stage — it is a folder.
A test you can run this afternoon: ask your head of sales and your head of marketing, separately, to write down what makes a lead an MQL. If the two answers differ — and they almost always do — you have found the reason your funnel report is not trusted. That gap is the whole project. Talk it through with me if you want a second pair of eyes on it.

Three rules that keep the model clean once it is live

1. Lifecycle only moves forward. A customer who fills in a top-of-funnel form does not become a Lead again. Most CRMs will happily let a workflow demote them, and once that starts your customer count drifts down every month for reasons nobody can trace. Guard every stage-setting workflow with a condition that checks the current stage first. Movement backwards, when it is genuinely needed, is a deliberate manual act with a reason logged — not an automation side effect.

2. One owner per transition. Two workflows that can both set a contact to MQL will eventually fight, and the winner is decided by execution order rather than intent. Every transition gets exactly one mechanism: one workflow, or one manual action, never both. Write the list of transitions down; if a transition has two possible causes, one of them is a bug you have not hit yet.

3. Recycling is a defined path, not a graveyard. Roughly two-thirds of leads sales rejects are still viable later, and the default handling — mark unqualified, forget forever — is where most B2B pipeline quietly dies. Define the return route: rejection reason is mandatory, timing rejections go back to nurture with a re-entry rule, fit rejections are suppressed permanently. A rejection reason field that is optional will be empty within a month, and then you have no idea whether your leads are bad or your timing is.

The five-day pass I would run on your CRM

This is not a quarter-long project. On a normal mid-market setup it is a week, and most of the week is conversation rather than configuration.

Day 1 — Audit. Export contacts by lifecycle stage. Count how many sit in each, how long they have been there, and how many were last touched by a human. The distribution alone tells you which stages are real and which are storage. Day 2 — Definitions. Both teams in one room, one page per stage, four boxes each: definition, exit criterion, owner, timestamp. Nobody leaves until the MQL row is agreed. Day 3 — Split the scores. Fit and intent as separate properties, decay on intent, structural negatives only.

Day 4 — Build and guard. One workflow per transition, forward-only conditions, entry-date stamps on every stage, mandatory rejection reason. Day 5 — The report you could not build before. Volume, conversion rate and median days per stage, plus recycled-lead outcomes. That report is the deliverable. The configuration was just what made it possible.

One dependency worth naming: none of this survives dirty data. Duplicate contacts split a person’s history across two records and both of them score wrong — which is why the hygiene layer comes first, and why we ended up building a deduplication bot on top of the HubSpot API rather than trusting native tooling alone. Fix the records, then fix the model.

Questions that come up every time

What is the difference between lifecycle stage and lead status?

Lifecycle stage records how far a contact has progressed in the overall relationship and moves forward only — it is what funnel reporting is built on. Lead status records what is happening in the work right now (new, attempting, connected, unresponsive) and changes freely. Keep them in separate properties: mixing them makes conversion rates meaningless.

How many lifecycle stages should a B2B company have?

Five to seven. Fewer and the funnel hides its own bottlenecks; more and the extra stages are almost always work statuses or segments wearing a costume. Add a stage only when a different team owns the record after the transition.

Should lifecycle stages ever move backwards?

Not automatically. Guard every stage-setting workflow so it cannot demote a record. When a genuine reset is needed — a churned customer re-entering evaluation, for example — make it a deliberate manual action with a logged reason, so the funnel history stays interpretable.

Do we still need lead scoring if we have AI in the CRM?

Yes, and arguably more. A predictive or AI-assisted score is only as good as the definitions and outcomes it learns from — if your MQL label is applied inconsistently, the model learns the inconsistency. Get the human-legible model right first, then let automation run on top of it.

The model is an agreement, and agreements need maintenance

The reason lifecycle models decay is not technical. They decay because the agreement behind them was made once, by people who have since changed roles, about a product that has since changed shape. The definitions stay in the CRM long after they stopped describing the business.

So put a date on it. Once a quarter, take the four-box page for each stage and ask whether the exit criteria still match how deals actually happen. It is a forty-minute meeting and it is the difference between a CRM that reflects the business and one that reflects the business as it was two years ago.

And before you hand any of this to automation, make sure the rules exist in writing first — the same argument applies to giving an AI write access to your CRM. Automation is very good at executing a model consistently. It is very bad at noticing that the model was never agreed.

Want this run on your CRM?

I rebuild lifecycle and scoring models for B2B teams on HubSpot: stage audit, definitions workshop with sales and marketing in the room, split fit/intent scoring, guarded workflows, and the funnel report at the end of it. A week of work, and you keep the documentation.

Book a lifecycle audit

Nacho Hernandez

Nacho HernandezMarketing & Business Consultant · Studio IdeagoLinkedIn →
Categorías
Blog post

The EU AI Act’s Transparency Rules Are Live: What Marketing Teams Have to Change

Compliance · Marketing Ops

For three years the EU AI Act was a thing your legal team would deal with later. Later arrived on 2 August 2026.

That is the date Article 50 — the transparency chapter — started to apply, and the date the Commission’s AI Office and national market surveillance authorities began enforcing it. In plain terms: chatbots have to tell people they are chatbots, AI-generated or manipulated content has to carry machine-readable marks, and deepfakes have to be labelled. Breaches of these obligations sit in the penalty band that reaches EUR 15 million or 3% of worldwide annual turnover.

Almost everything written about this has been written by law firms, for law firms. This is the operator’s version: which of your assets are actually in scope, who carries the obligation, and what to change in your stack this month.

What actually changed on 2 August 2026?

Article 50 covers four situations, and it is worth reading them as four different products rather than one rule: AI systems that interact directly with people, AI systems that generate synthetic audio, image, video or text, emotion recognition and biometric categorisation, and deepfakes plus AI-generated text published to inform the public on matters of public interest.

The mental model that helps most: this is not a consent regime, it is a disclosure regime. GDPR asks whether you are allowed to process someone’s data. Article 50 asks whether the person understands what they are looking at. You can keep using every AI tool you use today. You cannot keep being ambiguous about it.

The timing detail people miss: the disclosure has to reach the person at the latest at the time of the first interaction or exposure, in a clear and distinguishable manner, and it has to meet accessibility requirements. A note in your terms of service is not a disclosure. A grey 10px line under the chat window that a screen reader skips is not one either.

The compliance shortcut: the Commission published its Article 50 guidelines on 29 July 2026 alongside a Code of Practice on Transparency of AI-generated Content, and more than 180 organisations signed at launch. Adhering to that code is the recognised way to demonstrate compliance with the marking and labelling duties. Providers and deployers who choose not to sign have to demonstrate compliance through alternative, equivalently adequate means — which is a polite way of saying you will have to invent and defend your own method.

Are you the provider or the deployer?

This single distinction decides how much work you have. A provider develops an AI system and places it on the market under its own name. A deployer uses one under its own authority in a professional capacity. If you run marketing on HubSpot, Meta and an off-the-shelf chatbot, you are a deployer of all three.

The obligations split accordingly. Informing people that they are talking to an AI, and marking generated content in a machine-readable format, are drafted at the provider — your vendors. Disclosing emotion recognition and biometric categorisation, and disclosing deepfakes, are drafted at the deployer — you.

Which sounds like most of it is someone else’s problem. It is not, for two reasons. First, the provider ships the capability but you configure the surface: if you rename the assistant, replace the vendor’s default disclosure with your own copy, or design a widget where the notice is invisible on mobile, the ambiguity is yours. Second, the exemption everyone reaches for — disclosure is not required where the AI is obvious — is measured from the point of view of a reasonably well-informed, observant and circumspect person, in context. An assistant with a human first name, a headshot and a typing indicator is engineered to defeat exactly that test.

The four places marketing teams actually get caught

1. The website and WhatsApp chatbot

The most common failure is not a missing disclosure — it is a disclosure that was there and got designed away. Check the vendor default is still on, that it appears in the first message rather than in a collapsed panel, and that it survives on mobile. If your bot hands off to a human, say when that happens too. The person’s understanding is the thing being regulated, not the checkbox in the admin panel.

2. AI ad creative that looks real

A deepfake, in the Act’s definition, is AI-generated or manipulated image, audio or video content that resembles existing persons, objects, places, entities or events and would falsely appear authentic. Read that again with your last creative batch in mind. A photoreal AI product shot staged in a place that looks like a real place, an AI-generated spokesperson, a synthetic customer testimonial: all candidates. Native generation inside ad platforms made this a volume problem rather than an occasional one — we covered that shift when Meta put its own image model inside the ad tools. Platform auto-labelling helps, but the disclosure duty for deployers is yours, and platform labels are not a defence you control.

3. AI-written content — read the carve-out before you panic

This is where most teams over-comply. The deployer duty on AI-generated text applies to text published to inform the public on matters of public interest, and it does not apply where the content has undergone human review or editorial control and a natural or legal person holds editorial responsibility for the publication. Separately, the marking obligation does not apply where the system performs an assistive function for standard editing or does not substantially alter the input. Your product page is not a matter of public interest, and a drafted-then-edited article with a named accountable author is exactly the case the carve-out describes. The fix here is editorial governance, not a banner on every post.

4. Emotion and biometric tooling

If you run emotion inference on faces or voices — video ad testing panels, sentiment scoring on recorded sales calls from the audio itself — you are a deployer of an emotion recognition system, you must inform the people exposed to it, and you process that data under GDPR. Worth being precise, because most people over-apply this one: sentiment analysis on the text of support tickets is not biometric, and it is not what this paragraph covers.

The key idea: Article 50 does not ask you to use less AI. It asks you to stop being ambiguous about it. The teams that will struggle are not the heavy AI users — they are the teams that cannot produce a list of where AI touches a customer.
A five-minute test: name every customer-facing surface where AI speaks, writes or generates. Bot, SDR sequences, ad creative, on-site personalisation, review replies. If that list does not exist in writing, building it is the work. The legal review is the easy part afterwards.

A 30-day compliance pass for your marketing stack

Not a legal project. A week of inventory, a week of copy and configuration, and a standing owner. Here is the pass I would run on any client stack.

Surface What to do this month
Chatbots and AI assistants Disclosure in the first message, visible on mobile, readable by a screen reader. Say when a human takes over.
AI voice and outbound Disclose at the opening of the call or message, not after qualification. Store the exact wording used.
Paid social and display creative Tag every synthetic asset at production time. Keep platform AI labelling switched on. Disclose photoreal generations of people or places.
Content and SEO Named author with editorial responsibility, documented review step. That is the carve-out — make it real rather than assumed.
Research and call analytics Any emotion or biometric inference: notify participants, confirm the GDPR basis, and ask whether you need the feature at all.
Vendors Two questions per vendor: are you a signatory to the Code of Practice, and do your outputs carry machine-readable marks?
The register One sheet: system, vendor, your role, disclosure wording, owner, last reviewed. This is the artefact clients and auditors ask for.

That last row is the one worth doing even if nothing else gets done. The register is what turns a vague anxiety into a five-minute answer, and it is the same inventory the AI literacy obligations have been quietly asking organisations to produce since early 2025. It also happens to be the document that makes the governance conversation possible internally — the same reason we argued for writing rules down before switching on AI write access to a CRM.

Questions people keep asking

Does this apply if my company is not based in the EU?

The Act reaches systems and outputs used in the Union, not only companies established in it. If you run campaigns, chatbots or generated creative aimed at people in the EU, the working assumption should be yes — and the specific analysis belongs with your counsel.

Do I have to label every blog post I drafted with AI?

No. The deployer duty on text is limited to publications informing the public on matters of public interest, and it falls away where there was human review or editorial control with someone holding editorial responsibility. Assistive editing that does not substantially alter the input is outside the marking obligation as well.

Who enforces this, and what is the exposure?

National market surveillance authorities, the AI Office for systems under its supervision, and the European Data Protection Supervisor where EU institutions are involved. Breaches of the transparency obligations sit in the band reaching EUR 15 million or 3% of worldwide annual turnover.

Disclosure is a trust asset, not a tax

The instinct in most marketing teams is that saying this is AI costs conversion. In practice the opposite has been true wherever it has been tested properly: people disengage when they suspect they are being handled by a machine that is pretending otherwise, not when they are told plainly and then given a fast, useful answer. The disclosure is not the friction. The discovery is.

Which is the practical case for treating this as an operations project rather than a legal one. The inventory, the wording, the ownership, the review cadence — these are the same habits that make an AI-heavy marketing function reviewable at all. The regulation just set a date on them.

One caveat, stated plainly: this is an operator’s reading of the rules, not legal advice. The classification of a specific system, and anything close to the line, is a conversation for your counsel — go into it with your register in hand and it will take an hour instead of a month.

Want the register built for you?

I run AI disclosure audits for marketing teams: full inventory of AI touchpoints across web, ads, CRM and content, provider-versus-deployer mapping, disclosure copy that does not kill conversion, and an owner and review cadence you can actually keep. Typically a week of work.

Book an AI disclosure audit

Nacho Hernandez

Nacho HernandezMarketing & Business Consultant · Studio IdeagoLinkedIn →
Categorías
Blog post

Should You Let AI Write to Your CRM? What HubSpot’s Claude Connector Changes

CRM · AI Governance

Your CRM has always had one quiet safety property: a human had to type the change. Someone opened the record, picked the stage, saved it. Slow, but auditable by design.

That assumption no longer holds. The HubSpot connector for Claude can create contacts and deals, log calls and notes, and move a deal to Closed Won from a chat window, in one sentence, with no form in between. Write access shipped as a public beta alongside general availability for engagement history, and it works about as well as you would expect: fast, literal, and completely untroubled by whether the change was a good idea.

So the interesting question for anyone who actually runs a CRM is not whether it works. It is what you should let it touch, and what you need to have in place first. Here is the operator view.

What can the HubSpot connector for Claude actually write?

More than most people assume, and less than the marketing implies. On the read side, the connector reaches contacts, companies, deals, tickets, line items and engagement records. On the write side, in public beta, it can create and update contacts, companies, deals, tickets and line items, and log activities: calls, meetings, notes and tasks.

The engagement piece is the part people underestimate. Claude can read your full history of emails, calls, meetings, tasks and notes on a record, which means it is no longer summarising a CRM snapshot. It is summarising the actual conversation and then acting on it in the same breath: read six months of email with an account, draft the follow-up task, create it.

Three limits are worth writing down before you plan anything around it:

  • Bulk is capped at ten records per request. This is a deliberate guardrail, not a temporary beta limit to route around.
  • Portals with sensitive data enabled lose engagement access entirely. If your HubSpot account has sensitive data turned on, the connector sees no engagement data at all. Build a process that assumes email context and it will simply fail for you.
  • It requires a paid Claude plan. Available across all HubSpot tiers, but each user needs their own paid subscription, and existing connections must be disconnected and reauthenticated to pick up write access.
Recency check: this is not a brand-new August launch, whatever the roundup posts say. HubSpot announced write access and engagement history on its developer changelog in November 2025. Write is still labelled public beta, which is exactly why the governance conversation is worth having now rather than after it goes GA and spreads.

Who controls access, and what does the audit log really record?

The permission model is better than the average integration, and it is worth understanding precisely because it will carry more weight than your internal policy document.

A Super Admin has to opt the account into the product update before anyone can use write access. The first connection has to be made by a Super Admin or a user with App Marketplace permissions, and that person selects which permissions the connector gets. Only then can other users connect. From there, the connector inherits each user permission set from HubSpot itself: a sales rep working through Claude sees exactly the pipeline they would see in the UI, no more.

The audit trail is the part I would build your review process around. Every create and update made through the connector is attributed in the HubSpot Audit Log to both the user and the Claude connector. That is a genuinely useful design decision: you can filter for connector-made changes and see them as a distinct population rather than as anonymous edits mixed in with everything else.

Here is the gap, though, and it is the same gap every permissions system has. Permissions tell you who was allowed to change something. They do not tell you whether the change was correct. A rep with legitimate access to a deal can move it to Closed Won by typing one sentence, and every control in the chain will approve. The log will record it faithfully. Nothing in the system knows the deal has not actually closed.

Where does write access break down in practice?

Not in the places people worry about. The failure modes are boring, structural and entirely predictable from the state of your portal.

1. Ambiguous property definitions

Update the deal to Closed Won is unambiguous. Mark this contact as qualified is not, if your portal carries a Lifecycle Stage of MQL, a separate Lead Status of Sales Qualified, and a custom Qualified checkbox somebody built in 2023. A human hesitates and asks. The model picks the most plausible one and moves on. Property sprawl was already a reporting problem; write access turns it into a data-entry problem.

2. Stage changes are not edits, they are triggers

A deal stage change fires workflows, internal notifications, forecast recalculations and, in plenty of portals, an invoicing or onboarding sequence. In a chat window a stage change looks like a sentence. In your portal it is the first domino. This is the single most important thing to keep out of casual prompting until you have mapped what each stage actually sets off.

3. Creates without lookups become duplicates

Create a new contact for Maria at Acme is a create instruction, not an upsert. Ask for it ten times across a sales team and you have reintroduced exactly the duplicate problem most portals spend a quarter cleaning up. We wrote about building an automated cleanup for this in our CRM data-hygiene bot post, and the lesson transfers directly: dedupe logic belongs in code, not in a prompt.

4. Bulk work in the wrong tool

The ten-record cap tells you where the boundary sits. Anything larger belongs in a script with a dry run and a diff you can read before it commits, or in a HubSpot workflow you can test in a sandbox. Chat is for the record in front of you. It is not a migration tool.

5. AI-written notes look exactly like human ones

Six months later, nobody reading a record can tell which notes were summarised from an email thread and which were written by the person who was on the call. That matters when the note is the evidence for a renewal decision. Standardise a prefix or a property flag now, not after the archaeology starts.

The key idea: AI write access does not create CRM problems. It accelerates the ones you already have. A portal with clean properties and tight lifecycle definitions gets faster. A portal with property sprawl gets wrong faster, and now with an audit log full of changes nobody can explain.
A quick test before you connect anything: ask two people on your team what Qualified means in your portal. If you get two different answers, that is the work. Not the connector.

What rules should you set before you turn it on?

This is the part no changelog covers, because it is operating policy rather than product. Seven rules I would put in place on any portal before enabling write access for more than a couple of people.

Rule Why it matters
Start with ops, not sales Give write access to the two or three people who already own data quality. Expand once you have a month of audit log to look at.
Fix property definitions first One meaning per property, documented. Retire the duplicates. This is the highest-leverage hour you will spend.
Keep stage transitions out of chat Until you have mapped what each stage triggers, move deals in the UI where the consequences are visible.
Review the audit log weekly Filter for connector-attributed changes. Fifteen minutes. It is the only feedback loop you get.
Bulk goes to code Anything above the ten-record cap runs as a script with a dry run, or a sandboxed workflow. No exceptions.
Flag AI-authored activity A prefix on notes or a boolean property. Cheap now, priceless in a year.
Write a short prompt SOP Approved phrasings for the five things people will actually do. Ambiguous prompts produce ambiguous data.

None of this is exotic. It is the same discipline that makes any integration safe, applied to an interface that happens to accept plain English. If you have been mapping the wider connector landscape, this sits alongside the read-side tooling we covered in the marketing MCP connector landscape, with one difference that changes everything: reads are reversible and writes are not.

The real question is not whether AI should write to your CRM

It is whether your CRM is defined well enough that a fast, literal, tireless operator cannot do damage with it. That is a question about your data model, your lifecycle definitions and your automation map, and it was worth answering long before anyone connected a chat window to it.

Answer it and write access is real leverage: the admin work that used to eat a Friday afternoon collapses into a conversation. Skip it and you get the same portal you had, degrading faster, with a very well-documented record of how.

The connector is not the risk. The undefined portal underneath it always was.

Not sure your portal is ready for write access?

I run CRM readiness reviews for B2B teams on HubSpot: property and lifecycle audit, automation map, permissions model and a governance policy you can actually enforce. Usually a week of work that saves a quarter of cleanup.

Book a CRM readiness review

Nacho Hernandez

Nacho HernandezMarketing & Business Consultant · Studio IdeagoLinkedIn →
Categorías
Blog post

Search Console Isn’t a Website Tool Anymore: How to Measure AI and Social Visibility in 2026

For fifteen years, Search Console answered exactly one question: how is my website doing in Google? That is no longer what it is. In the space of eight months Google has bolted on a report for your visibility inside AI Overviews and AI Mode, and a whole new property type that tracks how your Instagram, TikTok, X and YouTube posts perform in Search — a property you can verify without owning a website at all. Most teams haven’t opened either. Here is what actually shipped, what the data does and doesn’t tell you, and what it should change in your monthly reporting.

SEO · Measurement

What Actually Changed in Search Console This Year?

Two things matter, and they arrived two months apart. On 3 June 2026, Google introduced Search Generative AI performance reports — dedicated views showing where your pages surface inside generative AI features on Search, such as AI Overviews and AI Mode, plus the equivalent surfaces in Discover. On 29 July 2026, Google completed the global rollout of platform properties, a new property type covering Instagram, TikTok, X and YouTube, and published a guide for analysing that data. The social rollout had been creeping out since 7 July; the experiment behind it first appeared inside Search Console Insights back in December 2025.

Read on their own, each looks like a modest feature release. Read together with everything else Google has quietly added to the tool — query groups, a branded-queries filter, custom annotations, weekly and monthly views, AI-assisted report configuration — the direction is unmistakable. Search Console is being rebuilt from a webmaster diagnostic into a visibility measurement layer that spans your site, your presence inside AI answers, and your social content. The tool changed category. Most reporting templates haven’t noticed.

Why this matters more than a normal feature drop:
Google is the one publishing the numbers now. Until this year, any claim about your visibility inside AI answers or about social content ranking in Search came from a third-party estimator. Now there is a first-party source — incomplete, but first-party. That changes which arguments you can actually win in a client meeting.

What Do the Generative AI Reports Actually Tell You — and What Don’t They?

Set expectations before you open it, because the gap between what people assume this report contains and what it contains is wide. At launch it gives you impressions only, broken down by page, country, device and date. There are no clicks, no CTR, and no query data. You can see that a page appeared inside an AI feature; you cannot see whether anyone clicked through, or what someone asked to trigger it. Google has said more metrics will follow, without committing to a date. Access also started as a subset of properties, with the UK first — so if the report isn’t in your account yet, that is expected, not a misconfiguration.

That sounds like a thin dataset, and it is. It is also the most useful thin dataset you’ve been given in years, because it answers the question everyone has been guessing at: is my content being used to build AI answers at all? A page with heavy AI impressions and flat organic clicks is being read and summarised without being visited — the zero-click pattern, now with a number attached. A page with no AI impressions is invisible to the surface that increasingly sits above the classic ten links. Those are two completely different problems, and until June you couldn’t tell them apart. If you want the strategic side of that — how to earn the citation rather than just measure it — that is the argument in Google AI Mode is the default now.

The honest caveat: an impression is not a business outcome, and nobody should be reporting AI impressions as a KPI to a CFO. Treat it as a diagnostic signal, not a result — the same way you treat impressions in the classic performance report. The mistake to avoid is building a dashboard around it before Google has finished the metric set, then having to explain a step-change in the chart when clicks eventually get added.

The Takeaway

Search Console stopped measuring your website and started measuring your presence in Google — across pages, AI answers and social posts. Those are three different visibility problems that used to need three different tools and a lot of guessing.

The data is incomplete. It is still the only first-party data that exists.

How Do Platform Properties Work for Instagram, TikTok, X and YouTube?

This is the genuinely new one, and the part almost nobody has set up. A platform property is the first Search Console property you can verify without owning a domain — you connect a social or video account instead. Once connected, you get a Performance report showing clicks, impressions, average CTR and average position for that account’s content, spanning Google Search, Discover and Google News. Not engagement inside Instagram. Not TikTok’s own analytics. How your posts perform as search results.

Access comes two ways. Large accounts are enrolled automatically through a Search profile — the published thresholds are roughly 100,000 followers on YouTube, Instagram or X, or 300,000 on TikTok. Below that you connect the account manually. Google’s own guide walks through five ways to use the data: reading search intent through query groups, catching trending content with a 24-hour filter, exporting to compare platforms side by side, using annotations to tie changes to content edits, and comparing formats — short-form against full-length, playlists against standalone videos.

The strategic consequence is bigger than the feature. Your social content has been competing in Google search results for years, and you have been running social and SEO as separate disciplines with separate reports and, usually, separate people. This connects them with shared metrics. A Reel that ranks for a commercial query is doing SEO work, and now you can prove it, name the query, and decide deliberately whether to answer that query with a post, a page, or both. That is a planning conversation you couldn’t have with evidence a month ago.

Is your reporting still measuring 2023’s version of Google?

I help B2B teams and consultants rebuild their measurement setup around how discovery actually works now — organic, AI surfaces and social in one framework, with numbers you can defend.

Review my measurement setup →

What Should You Change in Your Reporting Now?

Four things, in order of effort. First, connect the platform properties this week. Historical data only accumulates from the moment you connect, so every week you wait is a week of baseline you will wish you had when someone asks whether the social push moved search visibility. This is a fifteen-minute task with a compounding cost for delay.

Second, check whether the generative AI report exists in your properties and, if it does, take a manual snapshot now. Note which pages carry AI impressions and which don’t, before the metric set changes underneath you. Third, separate the two failure modes in your analysis: pages losing clicks while gaining AI impressions need better citation-worthiness and a rethink of what the click was worth; pages with neither need the classic work. Same drop in traffic, opposite prescriptions.

Fourth, stop reporting organic and social as separate universes. If a client’s TikTok is pulling Search impressions for queries their landing pages should own, that is one finding, not two channel reports that never meet. The unified view is the actual product here — the individual reports are just the plumbing. It is the same discipline as choosing the right measurement method for the right question, which is the case made in MMM vs attribution vs incrementality.

One closing caution: none of this is a reason to rebuild your dashboards this quarter. The AI report is deliberately incomplete and will change; platform properties are new enough that best practice doesn’t exist yet. The right move now is to turn everything on, start collecting, and stay boring about the conclusions until there is enough history to say something defensible. The teams that will look prescient in six months are simply the ones who connected the accounts today.

Want a measurement setup that reflects how people actually find you?

I work with consultants, agencies and B2B teams to connect the right properties, build reporting that covers organic, AI surfaces and social together, and turn it into decisions instead of another dashboard nobody opens.

Let’s talk →

Nacho Hernández

Nacho Hernández
Marketing & Business Consultant · Studio Ideago
LinkedIn →
Categorías
Blog post

We Built a CRM Data-Hygiene Bot with the HubSpot API + GitHub Actions. Here’s What We Learned.

Every CRM rots. Contacts change jobs, forms get filled with junk, the same company lands in your database three times under three spellings, and six months later your reports quietly stop meaning anything. Most teams treat this as a chore — a quarterly cleanup someone dreads, or a paid SaaS tool bolted on to paper over the mess. For a B2B client of ours, we did something different: we built a small data-hygiene bot on top of the HubSpot API and GitHub Actions that runs on its own, every night, for essentially the cost of nothing. Here’s what it does, why we built instead of bought, and where that line actually falls in 2026.

RevOps · Data Hygiene

Why Does CRM Data Hygiene Keep Breaking?

Because dirty data is not an event — it’s a constant leak. Every new lead, every integration, every manual edit is a chance for a duplicate, a malformed email, an empty lifecycle stage, or a country field that says «USA», «U.S.» and «United States» in the same list. The damage is quiet but expensive: sales chases the same account twice, automation fires on the wrong segment, and the dashboards leadership trusts are built on sand.

The instinct is to lean on the CRM’s built-in tools, and they help — up to a point. HubSpot auto-deduplicates contacts by email and companies by domain, and its Manage Duplicates tool surfaces likely matches. But the native tool is capped — roughly 2,000 suggestions on Professional, 5,000 on Operations Hub Pro, 10,000 on Enterprise — and, critically, companies created through the API are not deduplicated by domain at all. So the moment you have real volume, or any integration writing records in, the native cleanup is structurally behind. That gap is exactly where a paid deduplication SaaS steps in — and where the build-versus-buy question gets interesting.

Build or Buy? The 2026 Line Has Moved

For years the answer was obvious: buy. Building internal tooling meant hiring developers, standing up infrastructure, and owning maintenance forever — not worth it to merge duplicate contacts. But two things changed. Natural-language coding collapsed the cost of writing and maintaining a focused script, and connector APIs plus free automation runners removed the infrastructure entirely. The line between build and buy moved, and a lot of ops teams are still drawing it where it sat in 2022.

The useful way to decide is a simple 2×2: impact on revenue against effort to build and maintain. Keep buying where the vendor’s value is proprietary — your core CRM, email deliverability, third-party intent and contact data. You are not going to out-build HubSpot. But for configurable workflow — the rules that decide what «a duplicate» means for your business, which fields to standardise, when to flag a stale record — the buy case is shrinking fast, because those rules are specific to you and cheap to encode. Deduplication logic is the textbook example: high enough impact to matter, low enough effort to own. We’ve made the same argument about owning your integration layer through the marketing connector landscape and your customer data through first-party data infrastructure — a hygiene bot is the same principle applied to data quality.

The honest test before you build anything:
Could a well-configured native feature or a $50/month tool solve 90% of it? If yes, buy it. Build only when your rules are genuinely yours, the volume breaks the native caps, or you need it running unattended on a schedule no SaaS plan gives you. «We can code it now» is not the same as «we should.»

How We Built It: HubSpot API + GitHub Actions

The architecture is deliberately boring, which is the point. There is no server, no hosting bill, and nothing to babysit. The whole thing is a script in a private GitHub repository that runs on a schedule through GitHub Actions — the same free CI runner developers use to test code, repurposed as a nightly cron job. Every night it wakes up, talks to HubSpot through the CRM API, does its work, and goes back to sleep.

Concretely, the bot does four jobs on each run. First, deduplication: it pulls records in batches, groups them by normalised email and domain (plus fuzzy matching on name and company for the cases HubSpot’s exact-match logic misses), and merges or flags the collisions using its own rules — not the native cap. Second, standardisation: it rewrites the messy free-text fields into a controlled vocabulary — country, job title, lifecycle stage, industry — so segmentation stops leaking. Third, validation: it flags malformed emails, missing required properties, and records that have gone stale past a threshold. Fourth, reporting: it posts a short summary — how many merged, standardised, flagged — to a Slack channel, so the team sees the CRM getting cleaner instead of wondering if anything happened.

Two engineering choices made it safe enough to run unattended. It respects the API rate limits and runs in batches, so it never hammers the portal. And every destructive action — every merge — is logged and, in the early weeks, ran in a dry-run mode that only reported what it would do, so we could tune the matching rules against real data before letting it write. A hygiene bot that merges the wrong records is worse than dirty data; the guardrails matter more than the clever part.

The Takeaway

A nightly script on an API and a free CI runner now does what used to require a paid SaaS subscription — because the value was never the infrastructure, it was the rules that define clean data for your business.

You own those rules. That’s the part worth building.

Is your CRM data quietly breaking your reporting?

I help B2B teams audit their CRM, fix the data model, and automate the hygiene — whether that’s the right native setup, the right tool, or a custom bot like this one. The goal is the same: reports you can trust.

Audit my CRM →

What We Learned — and When Not to Build This

The bot works, the client’s reports are trustworthy again, and the running cost rounds to zero. But the more useful lessons are the caveats. Start in dry-run and stay there longer than feels necessary — the matching rules are where all the risk lives, and real data always surprises you. Log everything and make merges reversible where you can; a good audit trail is what lets you sleep. And solve the model, not just the symptom — if bad data keeps arriving, fix the forms and integrations creating it, or the bot just becomes a permanent mop.

Just as important: know when not to build. If your volume sits comfortably under the native caps, use HubSpot’s tools and move on. If a maintained app solves it for a few dollars a month and you have no unusual rules, buy it — owning code you don’t need is its own kind of debt. Build only when the impact is real, the rules are genuinely yours, and you have someone who can maintain it. For this client all three were true, so a bot was the right call. For the next one it might not be, and saying so is the consulting.

The wider shift is the one running under most of what changed this year: AI and open APIs keep making the doing cheap, which moves the advantage to judgement — knowing which problems deserve a custom build and which just need the boring, already-existing fix. A hygiene bot is a small example of a big pattern: the tools to build your own leverage are now within reach of a one-person consultancy, if you know where to point them.

Want clean, trustworthy CRM data without babysitting it?

I help consultants, agencies and B2B teams design the right hygiene setup for their CRM — native configuration, the right tools, or a custom automation like this one — so your data stays clean on autopilot and your reports finally tell the truth.

Let’s talk →

Nacho Hernández

Nacho Hernández
Marketing & Business Consultant · Studio Ideago
LinkedIn →
Categorías
Blog post

Meta Muse Image: Does Meta’s Own AI Model Kill Your Creative Stack?

On July 7, 2026, Meta shipped Muse Image — the first image-generation model out of its Superintelligence Labs — and it’s already live in the Meta AI app and powering creative on Instagram and WhatsApp. The part that matters for anyone spending money on paid social: in the coming weeks it arrives inside advertiser tools through Advantage+ creative, where it can read a full creative brief and spin one idea into dozens of on-brand variations. So the obvious question lands fast: if Meta will generate your ad creative for free, right where you build the campaign, why are you still paying for a separate AI image stack — or a designer? Here’s the honest answer.

Meta Ads · AI Creative

What Is Meta Muse Image, and What Actually Launched?

Muse Image is Meta’s own text-to-image model, built in-house by its Superintelligence Labs rather than licensed from an outside provider. At launch on July 7 it went live in the Meta AI app and started powering image experiences across Instagram and WhatsApp, with Facebook and Messenger following. For advertisers, the headline is the next step Meta has already signalled: Muse Image is coming to advertiser and agency tools through Advantage+ creative in the coming weeks — the same automation layer that already decides how your ads are assembled and delivered.

The claimed leap over earlier ad-creative tools is comprehension. Meta says Muse Image interprets a full creative brief — the intent, the mood, the product, the constraints — instead of stitching together separate keywords. It parses that brief, adjusts individual elements, swaps styles, and produces on-brand variations with fewer round trips. The practical promise: a small advertiser with no production team can turn one idea into many finished executions without opening a design tool. That’s not a new party trick; it’s Meta moving generation inside the ad account.

What Can Muse Image Do That Your Current Process Can’t?

The real edge isn’t image quality — external models have been good enough for a while. It’s proximity and volume. When generation lives natively inside Advantage+ creative, three frictions disappear at once. You skip the export-import shuffle between an outside tool and Ads Manager. You get variations tuned to Meta’s own placements and aspect ratios by default. And Meta’s delivery system can, in principle, generate and test more permutations than any human would bother to brief.

That last point is the strategic one. Paid social has been drifting toward volume-and-signal creative for two years: give the algorithm many variants, let delivery find the winners. We wrote about exactly this shift in why five ad variants now beat one — Muse Image is Meta pushing that logic to its conclusion, where producing the twentieth variation costs essentially nothing. If your creative bottleneck has been «we can only make three versions a week,» that bottleneck is about to move.

The guardrail Meta added alongside it:
Meta also introduced a Restricted Words setting for AI-generated text in Advantage+ campaigns — a list of terms the model must not use. If you turn Muse on, configure this on day one. Free generation without brand guardrails is how off-message creative ends up live in your name.

Does Muse Image Replace Midjourney, Your Designer, or Your Agency?

No — and being clear about what it replaces is how you avoid a costly mistake. Muse Image replaces the commodity middle of creative production: the tenth background variant, the quick resize, the «same ad, five hooks» batch, the throwaway test creative you’d never have paid a designer to make. That work was already migrating to AI. Meta just made it free and moved it inside the platform.

What it doesn’t replace is the two ends of the barbell. It doesn’t replace strategy — the brief, the offer, the angle, the audience insight that makes a creative worth generating in the first place. And it doesn’t replace distinctive brand craft — the hero asset, the art direction, the campaign idea a customer actually remembers. Forbes framed the launch as Meta «competing for ad budgets,» and that’s the tell: Meta wins if you generate more creative on Meta. It has no incentive to make your brand distinctive across channels — only to keep you producing and spending inside its walls. A free model that optimises for Meta’s business is a tool, not a strategy.

There’s also a portability cost. Creative generated inside Advantage+ is tuned for Meta placements and lives in Meta’s account. Lean on it exclusively and your creative library becomes platform-shaped — harder to repurpose for Google, email, or your site. The same discipline we argued for in building a scalable content operation with AI applies here: own your creative system, use the platform’s model as one input, not the whole pipeline.

The Takeaway

Muse Image replaces the commodity middle of ad creative — the variants and resizes — not the strategy above it or the brand craft beside it. Use it to multiply tests, not to outsource your creative judgement to a model that optimises for Meta’s revenue.

Free generation inside the ad account is convenient. Convenient is not the same as strategic.

Want a creative testing system that uses Muse without depending on it?

I help brands and agencies set up Meta creative operations that multiply variants with AI, keep the brand distinctive, and stay portable across channels — instead of getting locked inside one platform’s model.

Build my creative system →

The Bottom Line: How Should You Use Muse Image?

Turn it on when it reaches your account — but use it deliberately. Treat Muse Image as a variant engine sitting under a human brief. You still write the strategy, the offer and the core angle; Muse expands that into the volume of tests Meta’s delivery wants to see. Set your Restricted Words list before the first generation, keep at least one distinctive hero asset made outside the platform, and pull your winning concepts back out so your creative library isn’t trapped in Meta’s shape.

The wider pattern is the one running through everything the platforms shipped this year: AI keeps making the doing cheap, which makes judgement the scarce asset. When anyone can generate a hundred ads for free, the advantage isn’t generation — it’s knowing which idea deserves the hundred variants, and which brand signals to protect while you scale them.

Muse Image will make bad creative faster and good creative cheaper. Which one you get still depends entirely on the brief you bring to it.

Make Meta’s AI creative work for your brand, not the other way around

I help consultants, agencies and B2B teams build Meta ad-creative systems that use Advantage+ and Muse Image to multiply testing — with brand guardrails, distinctive hero assets, and a library you actually own across every channel.

Let’s talk →

Nacho Hernández

Nacho Hernández
Marketing & Business Consultant · Studio Ideago
LinkedIn →
Categorías
Blog post

HubSpot Just Launched Agent Hub: The End of AI Agent Sprawl

Most go-to-market teams didn’t adopt one AI agent this year — they adopted six, from six different tools, with no one owning them and no shared memory between them. On July 23, 2026 HubSpot shipped its answer to that mess: Agent Hub and Agent Builder, now in public beta for every Professional and Enterprise customer. The pitch isn’t «here’s another agent.» It’s «here’s the place to build, run and watch all of them, on one shared record of your customer.» That’s a different — and more interesting — bet. Here’s what actually launched and how to decide whether to turn it on.

HubSpot · AI Agents

What Did HubSpot Just Launch with Agent Hub and Agent Builder?

HubSpot released two connected products in public beta. Agent Hub is the management layer: a single workspace where you discover, activate, monitor and organise every AI agent running across marketing, sales and service. You see live status, recent results, and outcomes grouped by go-to-market goal — building demand, winning deals, delighting customers, scaling growth — instead of a scatter of disconnected bots. Agent Builder is the creation layer: a low-code canvas where non-technical users describe a task in plain language through Breeze Assistant, wire workflows and custom agents together, and trigger them from schedules, record updates, webhooks or third-party integrations.

The unlock underneath both is shared context. Every agent reads and writes to the same HubSpot customer record, so they stop working blind to each other. HubSpot’s own example is the failure mode everyone recognises: a sales prospecting agent emails a warm pitch to an account the same week a service agent is handling that account’s open complaint — neither aware of the other. On a shared record, that collision doesn’t happen. This is the logical next step after last year’s Breeze rollout; if you want the groundwork, our take on what to activate and skip in HubSpot Breeze still holds.

What Problem Does Agent Hub Actually Solve?

The real target is agent sprawl. Over the last eighteen months most teams bolted AI onto their stack tool by tool — a chatbot here, a content agent there, a prospecting agent from a point vendor — and ended up with automation nobody owns, no clear performance visibility, and no shared view of the customer. It feels productive and quietly creates risk: agents duplicating outreach, contradicting each other, or acting on stale data.

Agent Hub attacks that on three fronts. Ownership: one screen shows what’s running, what it’s doing and who’s accountable, so agents stop operating in the dark corners of your ops. Visibility: results are organised by outcome, not by tool, so you can finally ask «is this agent producing pipeline?» and get an answer. Context: because everything sits on the HubSpot record, an agent’s action is informed by the customer’s full history, not just the slice its vendor happened to see.

This is why the launch matters more than a single flashy agent would. The bottleneck for most teams in 2026 isn’t «can we get an agent to do a task» — it’s «can we run ten of them without them stepping on each other and on our customers.» A control tower is a less glamorous product than a magic bot, and a far more useful one.

Agent Builder: Who Is Low-Code Agent Creation Really For?

Agent Builder lowers the floor for making a custom agent. You describe what you want in plain language, connect it to your existing HubSpot workflows and data, and set what fires it. That genuinely helps a RevOps lead or a marketing manager automate a real task — routing, enrichment, follow-up drafting, meeting prep — without waiting on a developer.

But «low-code» is not «no-judgement.» An agent you can build in an afternoon is still an agent acting on live customer data, and the same discipline you’d apply to a human hire applies here: a narrow job, clear guardrails, and a way to check its work. The teams that get burned will be the ones who treat Agent Builder as a toy and let five half-configured agents loose on their database. The teams that win will scope each agent to one job they can measure. It’s the same lesson from our look at what AI agents are actually replacing in B2B marketing — the tool is only as good as the job you give it.

One thing to check before you build:
Custom agents run on HubSpot Credits when they perform configured actions. Credits are included at Professional and Enterprise tiers, but «free to create» is not «free to run» — scope agents to jobs worth the credits they’ll spend.

How Should You Actually Roll This Out?

Treat the beta as a controlled pilot, not a land-grab. A sane rollout in four moves.

1. Inventory what’s already running. Before you add anything, use Agent Hub to see every agent already active in your portal. Most teams are surprised by what’s on. You can’t fix sprawl you can’t see.

2. Start with one high-value, low-risk job. Pick a task with a clear owner and an obvious metric — lead routing, meeting prep, a first-draft follow-up that a human still sends. Avoid anything customer-facing and irreversible until you trust the output.

3. Wire in the shared context deliberately. The value is agents that know what other agents and reps have done. Make sure your data and properties are clean enough that «shared context» means accurate context, not confidently wrong context.

4. Set a review cadence. Check each agent’s results weekly against the outcome it was hired for, and against credit spend. Kill the ones that don’t earn their keep. An agent you never audit is a liability with a login.

The Takeaway

Agent Hub’s real product isn’t another agent — it’s ownership, visibility and shared context for the agents you already run. Adopt it as a control tower, and scope every agent to one measurable job.

Low-code lowers the floor for building. It doesn’t lower the bar for judgement.

Not sure which agents in your portal are actually earning their keep?

I help HubSpot teams audit their agent stack, kill the sprawl, and roll out Agent Hub around jobs you can measure — with the data hygiene that makes «shared context» trustworthy.

Audit my HubSpot agents →

The Bottom Line: Should You Turn On Agent Hub This Week?

If you’re on Professional or Enterprise and you already have more than one agent running, yes — but as an audit tool first, not a build tool. Open Agent Hub, see everything that’s active, and organise it before you create anything new. The single biggest win in the first week is visibility: knowing what your automation is actually doing to your customers.

The wider pattern is the one running through everything the platforms shipped this year. AI made it cheap to do the task; the scarce skill is now orchestration — deciding which jobs to automate, keeping them from colliding, and reading whether they’re working. HubSpot is betting the winning teams won’t be the ones with the most agents, but the ones who manage them like a team instead of a pile of scripts.

Turning on an agent is now trivial. Running a fleet of them well is the actual job. Build the control tower first.

Turn HubSpot’s agent stack into a system you control

I help consultants, agencies and B2B teams roll out HubSpot Agent Hub the right way — an inventory of what’s running, agents scoped to measurable jobs, clean data so shared context is trustworthy, and a review cadence that kills the sprawl before it costs you customers or credits.

Let’s talk →

Nacho Hernández

Nacho Hernández
Marketing & Business Consultant · Studio Ideago
LinkedIn →
Categorías
Blog post

The LinkedIn Ads Creative Shift: Why Five Variants Now Beat One in 2026

For years the standard LinkedIn Ads playbook was to write one tight ad, put real money behind it, and pray. On July 1, 2026 LinkedIn quietly made that playbook obsolete. It shipped a full creative suite inside Campaign Manager — Brand Kit, Draft with AI, Ads Personalization, AI ad variants and Flexible Ad Creation — and paired the launch with a number that should change how you budget: campaigns running five or more ad variants see more than 20% higher click-through rates than campaigns running a single ad. If you’re still shipping one creative per campaign, you’re now leaving measurable performance on the table. Here’s what changed and how to build a LinkedIn creative-testing system around it.

LinkedIn Ads · Creative

What Did LinkedIn Just Change in Campaign Manager?

On July 1, 2026 LinkedIn rolled out a connected set of creative tools that sit directly inside Campaign Manager, so you no longer bounce between a design file, a copy doc and the ad builder. Five pieces matter for advertisers.

Brand Kit lets you store your logos, fonts and colours once and apply them across every ad, so a rushed campaign still looks on-brand. Draft with AI generates ad copy from a short prompt or your landing page, giving you first drafts instead of a blank box. AI ad variants take one approved concept and spin out multiple versions — different headlines, angles, framings — in a few clicks. Ads Personalization tailors elements of the ad to the member seeing it. And Flexible Ad Creation lets you supply a pool of assets that LinkedIn assembles and tests per placement.

LinkedIn also added Auto-targeting and Draft with AI specifically for small and medium businesses, lowering the skill floor for teams without a dedicated media buyer. Read together, the release has one obvious intent: LinkedIn wants you producing and testing more creative, because its own data says volume-of-variants is now a performance lever, not a nice-to-have.

Why Do Five Ad Variants Beat One?

The 20% CTR gap isn’t magic — it’s a function of how LinkedIn’s delivery works. When you give the auction one ad, the system has nothing to optimise between; it shows that ad to everyone in your audience whether the angle lands or not. Give it five, and the algorithm can match the right message to the right member, shifting spend toward whichever variant each segment responds to. More variants means more surface area for the system to find fit.

There’s a second, slower effect: creative fatigue. On LinkedIn’s comparatively small, high-frequency B2B audiences, a single ad burns out fast — the same decision-makers see it repeatedly and stop noticing. A rotation of five keeps the impression fresh for longer, so your CTR degrades more gently over the campaign’s life instead of falling off a cliff in week two.

The catch is that «five variants» only works if they’re genuinely different. Five near-identical headlines don’t give the auction anything to choose between. The point of the new AI tools is to make real variation — distinct hooks, formats and value propositions — cheap enough that producing five is no longer a reason to skip the test.

Variety, not volume, is the real lever:
Five variants beat one because they give the auction and the audience something to choose between. Five copies of the same idea are still, functionally, one ad.

How Do You Build a LinkedIn Creative-Testing System?

Treat the new tools as an assembly line, not a magic button. A repeatable system beats occasional bursts of inspiration.

1. Set the guardrails first. Load your Brand Kit before you touch Draft with AI. If the AI is generating copy and variants, you want brand colours, fonts and logo locked so every machine-made version still looks like you — not a generic template.

2. Test angles, not adjectives. Build your five around genuinely different ideas: one on the core outcome, one on a pain point, one on a proof point or stat, one on the objection your buyers actually raise, one on a contrarian take. That’s how you learn what your market responds to — not by A/B testing two versions of the same sentence.

3. Use AI for the first draft, a human for the final cut. Draft with AI and AI ad variants are excellent at producing volume and breaking blank-page paralysis. They’re mediocre at nuance, positioning and the specific language your niche uses. Generate ten, keep the five that a human would actually approve, and edit them so they don’t read like everyone else’s AI copy.

4. Give the test room to breathe, then read the right metric. Don’t kill a variant after a day. Let LinkedIn’s delivery distribute impressions, then judge on the metric that matches your objective — CTR for awareness and engagement, but cost-per-lead or pipeline for anything down-funnel. A high-CTR ad that produces junk leads isn’t a winner. Which is exactly why your measurement framework has to sit underneath the creative test, not beside it.

The Takeaway

Ship five genuinely different angles per campaign, let AI draft them and a human approve them, and judge each on the metric that matches your goal — not on CTR alone.

The tools removed the excuse. Producing five strong variants is now cheap; running one is now a choice to underperform.

Running LinkedIn Ads with a single creative per campaign?

I help B2B teams build a LinkedIn creative-testing system — a Brand Kit that keeps AI output on-brand, a five-angle testing framework, and the measurement to tell a real winner from a vanity-metric one.

Fix my LinkedIn creative →

The Bottom Line: What Should You Do This Week?

Pick one active campaign and turn its single ad into five distinct angles using the new tools — Brand Kit locked, Draft with AI for the first pass, your own edit for the final cut. Give it two weeks, then compare CTR and cost-per-lead against the single-ad baseline you were running. LinkedIn’s own numbers say you should see the gap; your account will tell you whether it holds for your audience.

The wider pattern is the same one running through everything the platforms shipped this year: AI is making production cheap, which moves the advantage from who can make an ad to who tests and reads results well. The same shift is changing how B2B teams capture leads in the first place. The teams that win won’t be the ones generating the most creative — they’ll be the ones with a system for turning that volume into learning.

Volume is now free. Judgement is the scarce part. Build the system that supplies it.

Turn LinkedIn’s new creative tools into pipeline

I help consultants, agencies and B2B teams set up a LinkedIn Ads creative-testing system that actually moves cost-per-lead — brand guardrails, a five-angle framework, AI-assisted production with a human final cut, and measurement that separates real winners from vanity metrics.

Let’s talk →

Nacho Hernández

Nacho Hernández
Marketing & Business Consultant · Studio Ideago
LinkedIn →
Categorías
Blog post

The Marketing MCP Connector Landscape in 2026: Which Ones Actually Exist, and Which to Use

Two years ago, connecting your ad accounts to anything meant a developer, an API key and a week of your life. In 2026 you can open Claude or ChatGPT and ask, in plain English, «which of my Google Ads campaigns is bleeding budget?» — and get an answer pulled live from the account. The thing making that possible is the MCP connector: a standard way for AI assistants to read from, and increasingly write to, the platforms you already run. The catch is that there are now dozens of them, they are wildly uneven, and some will happily change your live campaigns. Here’s which ones actually exist, which to trust, and how to use them without handing an AI the keys to your client accounts.

Connectors · MCP

What Is an MCP Connector, and Why Should a Marketer Care?

MCP — the Model Context Protocol — is a shared standard that lets an AI assistant talk to an external tool through a small server. Instead of every app inventing its own bespoke plugin, MCP gives Claude, ChatGPT, Gemini, Cursor and the rest one common socket. A «connector» is simply the MCP server for a specific platform: a Google Ads connector, a Meta Ads connector, a HubSpot connector.

For a marketer, the practical payoff is that the reporting and busywork layer collapses. You stop exporting CSVs and rebuilding the same pivot every Monday, and start asking questions: which ad sets dropped below a 2x ROAS last week, which HubSpot deals went quiet, which search terms are wasting spend. The AI queries the account directly and answers. The 2026 shift is that this stopped being a demo and became infrastructure — Meta adopted MCP as the primary integration method for its Ads AI Connectors, and the major platforms now ship official servers rather than leaving it to hobbyists.

Which Marketing MCP Connectors Actually Exist in 2026?

The landscape splits cleanly into two camps: official servers shipped by the platforms themselves, and third-party servers that wrap several platforms or add write actions the official ones withhold. Both have a place.

The official ones (start here). Google open-sourced its own Google Ads MCP server in early 2026 — it’s deliberately read-only, exposing account listing and GAQL queries for diagnostics and analytics. Google also ships an official GA4 server covering 200-plus dimensions and metrics, so you can interrogate traffic, conversions and audiences by conversation. And HubSpot’s remote MCP server went generally available on April 13, 2026: it gives read and write access to core CRM records — contacts, companies, deals, tickets, line items, products — plus activities like calls, emails, notes and tasks, all over an OAuth 2.1 connection that respects each user’s existing permissions. Its honest limits: no custom objects, and if your portal has sensitive-data protection on, activity objects are blocked.

The third-party ones (fill the gaps). Where the official servers stop at read-only, independents add control. Pipeboard’s Meta Ads MCP is the most mature single-platform Meta server, with full read/write for campaigns, ad sets, creatives, targeting and budgets. Unified commercial connectors like Ryze (Google Ads, Meta, GA4 with confirmation-gated writes, ~$89/mo) or Synter (14 ad platforms, from ~$199/mo) trade a subscription for one socket across your whole stack. And Markifact launched a hosted Google Ads MCP on July 13, 2026 that adds write actions to the account — but only with a human approving each change. For pure data pulls across 350-plus sources, a reporting connector like Windsor.ai remains the pragmatic choice.

The one distinction that matters most:
Read-only connectors can only tell you things. Write-enabled connectors can change things — pause a campaign, move a budget, edit a deal. That single line decides how much you should trust a given server, and how much supervision it needs.

Read or Write? How to Choose the Right Connector

Match the connector to the job, not to the hype. For reporting, diagnostics and «what happened last week» questions, a read-only official server is almost always the right call — it cannot break anything, so you can wire it up across every client account without losing sleep. This is where 80% of the day-to-day value lives, and it’s the safest place to start.

Reach for a write-enabled connector only when the workflow genuinely needs to act — bulk-pausing losing ad sets, pushing negative keywords, updating deal stages after a call. When you do, the non-negotiable feature is a human-approval step: the AI proposes the change, you confirm it, then it executes. That’s exactly the model Markifact built its July launch around, and it’s the difference between a co-pilot and an unsupervised intern with your ad budget.

Two more filters before you connect anything to a client account. First, authentication: prefer connectors that use proper OAuth and honour the permissions the user already has, like HubSpot’s official server — avoid anything asking you to paste a long-lived API key into a config file. Second, maintenance: a connector is only as good as its upkeep. A well-maintained open-source server with active commits beats an abandoned one, and a hosted commercial server beats both if you’d rather not babysit updates.

The Rule Of Thumb

Read-only by default, write only with a human in the loop. Start with the platform’s official server; add a third-party one only when you need an action the official one won’t perform.

The best connector isn’t the one with the most tools. It’s the one you can safely point at a client account and forget about.

Not sure which connectors are safe to plug into your stack?

I help teams pick the right MCP connectors for their ad and CRM accounts, wire them into a reporting and optimisation workflow, and set the guardrails so nothing changes without a human saying yes.

Map my connector stack →

The Bottom Line: Which Ones Should You Actually Use?

If you run Google Ads, Meta and a CRM, a sane 2026 starting stack looks like this: Google’s official read-only Google Ads and GA4 servers for reporting and diagnostics, HubSpot’s official server for CRM reads and the occasional supervised write, and a single write-capable ad connector — Pipeboard for Meta-heavy accounts, or a unified commercial server like Ryze or Synter if you want one socket — strictly with human approval switched on. Keep a reporting connector like Windsor.ai for the cross-channel data pulls that don’t fit any one platform.

This is the same thread running through everything platforms shipped this year: the tooling is racing ahead of the guardrails. It’s the reason AI is reshaping how you capture leads, and the same reason automated bidding keeps taking decisions out of your hands. Connectors give some of that control back — if you choose them deliberately.

Don’t connect everything because you can. Connect the few servers that earn their access, keep a human on the write actions, and let the AI do the reporting you were never going to enjoy anyway.

Build an AI-connected marketing stack that’s actually safe

I help consultants, agencies and B2B teams connect their ad platforms and CRM to AI assistants the right way — official servers first, write access gated behind human approval, and a reporting layer that finally runs itself. No abandoned open-source gambles, no keys handed to an unsupervised bot.

Let’s talk →

Nacho Hernández

Nacho Hernández
Marketing & Business Consultant · Studio Ideago
LinkedIn →