Webflow’s launch post for Campaigns, published October 20, describes a problem every demand gen marketer knows by heart. The brief goes to the web team and waits for a sprint. The ad creative goes to brand, or to an agency. Weeks pass, sales flags a pipeline gap, and the campaign meant to close it still is not live. Campaigns is Webflow’s answer: one tool that takes you from brief to landing page to ads to pipeline reporting without filing a ticket.
Most of that holds up in the documentation. The page side is careful work. The weak point sits at the exact spot the pitch leans on hardest. Webflow sells “message-matched ads,” and its product page says you can push to Google Ads “with ad copy already matched to the page.” Its own help center says the headlines, long headlines and descriptions in that Google Ads campaign are “generated by Google, not Webflow.” Webflow matches the page and the picture. Google writes the words, and by default Google can also choose a different landing page. Plan for that before the first push.
A note on evidence. This is a primary-source review. I have not used Webflow Campaigns. It is built from Webflow’s launch post, its product update, the product page, the pricing page, twelve Campaigns help center articles, the AI credits page and Google’s own Performance Max documentation, all read on October 21. The only independent coverage I found was a CMSWire news piece that largely restates the announcement, so treat the vendor’s framing as the vendor’s.
What it is
Campaigns is a standalone product, separate from your website. Your main site can run on Webflow, WordPress or anything else, because Campaigns has no connection to your CMS. Campaign pages live in a campaign hub, which the hub guide describes as a big folder with one brand and one domain. Two business units means two hubs.
The flow runs in five steps. You give it a live URL and AI agents extract your brand: colors, typography and voice, stored in DESIGN.md, an open plain-text format for describing a design system to AI agents. You describe the campaign and pick a type (lead gen, gated content, meetup, webinar or product feature), and an agent drafts a brief you edit. Once you approve the brief, it generates an editable page in a few minutes. From that base page you spin out variations for personas, industries or named accounts, each with its own URL. Then you connect a HubSpot or Marketo form, generate ad images, push a Performance Max campaign to Google Ads, and read sessions, form fills and pipeline in the same place.
Teams that live in Claude or ChatGPT can also drive it through the Webflow MCP server.
What changed on October 20
Webflow first showed Campaigns at Webflow Conf. On October 20 it became available for purchase, sold through sales, with the pricing page listing it at “Starting at $2k/mo.” It is built for demand gen, growth and performance teams, and the launch customer quote is a fair description of the old way: a mockup in Lovable, rebuilt by hand in WordPress, with reporting stitched together afterward.
What works
The brief comes first. Campaigns will not generate a page until you approve a brief, and the MCP guide says your AI tool needs a confirmed brief before it can create a campaign. A tool that forces someone to write down audience, offer and conversion goal before it builds anything is already doing a job most campaign intake processes skip.
Variations are built to be reviewed. Each page variation starts unpublished and has its own publish status, so generating twelve account pages does not put twelve pages live. A content table shows every variation side by side with a column per personalized field, which is how a human actually checks twelve versions of a headline.
It admits when it is guessing. The page guide warns that a thin brief produces placeholders, such as a to-do note where a statistic should go. That beats an invented statistic, as long as someone looks before publishing.
Forms stay in your stack. HubSpot and Marketo forms embed as a component that takes your brand styling, one form reused across pages, and you pull field changes from the source app instead of rebuilding.
The pipeline math is written down. The reporting guide explains exactly how “pipeline influenced” is calculated. More on why that matters below, but documenting it at all is better than most tools manage.
The MCP limits are honest. Webflow lists what its MCP server cannot do: no ad creation, no brand extraction, and publishing still happens in Campaigns. So the publish button stays with a person.
What breaks or is missing
Google writes the ad text. The Google Ads launch guide is plain about it. When you continue to Google Ads, each selected page becomes an asset group. Campaigns fills in the final URL and sends your ad images in each size. Headlines, long headlines and descriptions are “generated by Google, not Webflow.” Your message match covers the image and the page. The words a searcher reads first come from Google. That is a sharp gap against product page copy promising ad copy “already matched to the page,” and it is the first thing to raise on a demo call.
Google may also swap the page. Google’s own Final URL expansion documentation says the feature is on by default for Performance Max and lets a campaign replace your final URL with a page from the same domain it judges more relevant, and with text customization on, write matching text for it. Webflow’s guide does not mention the setting. If you built a variation for healthcare buyers with its own URL, a default PMax campaign is allowed to send some of that traffic elsewhere on the domain. Google’s FAQ gives the fix for exactly this case: when one specific page is the only path to conversion, turn Final URL expansion off and point the asset group at that page.
Google is the only door. Performance Max is the only campaign type the integration supports, and the ads guide says Google Ads is the only partner you can launch to. LinkedIn, Meta, Reddit and 6sense sizes are generated, but you download and upload them yourself. For a B2B team whose budget sits in LinkedIn, the matched ad stops at your downloads folder.
Reporting starts dark. Tracking is off by default for every new hub. Turn it on and the default consent mode is “Always track visitors.” The two other modes need a consent management tool or, per the tracking guide, they will not function properly. Form tracking is a separate switch inside the HubSpot or Marketo app, HubSpot’s form connection and CRM connection are two separate connections, and every tracking change needs a republish. Miss one and the first week of a launch reports nothing.
Pipeline influenced is generous. A form submission counts toward pipeline influenced when it connects to an opportunity “last updated in your CRM after the form submission happened.” That includes deals already open when the form was filled. A late-stage deal whose champion registers for your webinar, then gets a routine stage update, counts toward the webinar. That is a defensible definition of influence. It is not sourced pipeline, and it will flatter every campaign that reaches existing customers and open accounts. Engaged accounts, meanwhile, only counts form submitters.
The credit meter has no rate card. Campaigns consumes Webflow AI credits for brand extraction, page generation, variations, ads and the Google push, and the same credits are spent when you generate through MCP. The credits page says usage is dynamic, there is “no fixed rate per action,” and Webflow does not publish a rate card. A request that starts with a positive balance is allowed to finish and push the workspace negative, settled from the next allotment. Credits are pooled across the whole workspace, so your Campaigns pilot and the web team’s AI copy work draw from one bucket.
Small traps in the creative flow. Other ad sizes are reframed from the base image, and the ads guide warns that later edits to the base will not carry over to sizes already generated. Changing a creative set’s source images resets the whole set, including variations and edits. Brand extraction struggles with gradients, low-contrast palettes and custom display fonts, which fall back to web-safe equivalents. Published campaigns cannot be deleted, only archived, and a published variation must be unpublished first. Marketo users get form-to-pipeline linking, but Smart List sync and audience targeting live in Webflow Optimize, a separate product.
Who it is for right now
B2B demand gen and growth teams on HubSpot or Salesforce, with Google Performance Max in the plan, and a web team queue that is a real constraint on launches. If you ship several webinar, ABM or comparison pages a month and each one waits weeks, a few thousand dollars a month to cut that out is easy math.
It is a weaker fit for teams whose paid budget is mostly LinkedIn or Meta, for anyone who runs Search campaigns with tightly written ads, for ecommerce brands (the campaign types and the CRM reporting are built around leads and opportunities), and for teams with heavy EU traffic and no consent tool in place.
Pricing and limits
The pricing page lists Campaigns at “Starting at $2k/mo,” sold through sales. The public pages do not say what that includes, how many hubs or pages it covers, or how many AI credits come with it. For reference, Webflow’s self-serve workspace plans include 200 to 400 credits a month, the Team plan includes 100,000 a year, and self-serve add-on packs are 2,000 credits for $25 a month or $20 a month billed annually. Webflow says credit rates may change as AI costs move, with advance notice.
Other limits: one brand and one domain per hub, PMax only, Google sign-in required every time you open the integration, Site manager or Designer permission to install the Google Ads, HubSpot and Marketo apps, and the embedded form component works only with new HubSpot forms, not legacy ones.
What to do this week
Send five questions before the demo. What does the starting price include in credits, hubs and pages? Roughly how many credits does a typical campaign with five variations and one creative set use? Will Webflow write the PMax text assets, or only Google? Can pipeline influenced be limited to opportunities created after the submission? Can the integration launch with Final URL expansion off?
Pilot one campaign, not a program. Pick a webinar or a single ABM tier with a deadline. Put the hub on a campaign subdomain you control and run the pilot next to your current process, so you have a real time-to-launch comparison instead of a vendor’s.
Fix the Google settings in Google. After the push, turn off Final URL expansion for any variation-specific asset group, then read every Google-written headline and description against the page it points to before you hit launch.
Decide tracking before the first publish. Pick the consent mode with whoever owns privacy, confirm your consent tool works with it, switch on form tracking in the HubSpot or Marketo app, connect both HubSpot connections, then republish.
Report pipeline influenced next to your own numbers. Put it beside sourced pipeline from your CRM and label it. Do not let it replace that number in the board deck.
Watch the meter by feature. Open Workspace settings, then Usage, after every build step in the pilot, and finalize the base ad image before generating any other size.
Campaigns takes the web team queue out of the landing page problem, and on paper it does that well. It does not take Google out of the ad. Treat the push to Google Ads as a handoff that needs its own review, and the pilot will tell you whether the speed is worth $2k a month.
