Estate enumeration
Accounts, sub-accounts, groups, pages, domains, on demand, the inventory that never existed in a document.
Unbounce connector
Unbounce MCP Connector – Page Performance in Plain English
Unbounce accounts accumulate history: pages from campaigns past, page groups from reorganizations past, sub-accounts from clients past. Somewhere in there, today's campaigns are converting. Saying exactly where, and how well, usually means an afternoon nobody schedules.
The Unbounce connector makes the estate legible. It links the AI you already use, like Claude, ChatGPT, or Copilot, to your Unbounce accounts through Mad Fish Elements, reading accounts and sub-accounts, pages and page groups, domains, leads, and the form fields behind them. This is a read connector, and this page treats that as the feature it is: total visibility, zero risk to the pages doing the converting.
See it
What Your AI Can See
Connect your accounts, and your AI reads the whole structure: every account and sub-account, the page groups organizing work, every page with its state, the domains pages publish to, the leads captured, and the form fields defining what capture means.
Estate questions become sentences; "List all pages in the main account by lead volume this quarter" ranks the working layer. "Which pages captured nothing in 90 days?" finds the archive-in-waiting. "What domains do we publish to, and which pages sit on each?" maps the estate. "Show the form fields on our top converting pages" reads what the winners actually ask for. And the cross-checks run through the Gateway: spend pointed at silent pages, and captured leads verified into the CRM.
Do it
What Your AI Can Do
Honesty first, as on every page: this connector reads. What that enables is worth the page:
Production ranking
Leads by page over any window, so the working layer is known, not assumed.
Silence detection
Published pages capturing nothing, surfaced on schedule, the candidates for cleanup you perform in Unbounce with the list in hand.
Handoff verification
Leads read here, checked into HubSpot or Salesforce on the same Gateway, so the capture-to-CRM pipe is provably whole.
Form intelligence
What your best pages ask, versus what your quiet pages ask, read side by side.
Changes to pages happen in Unbounce's builder, by your team, with the connector's findings in hand. When the page said "read," it meant it.
A working session
The Inherited Account, Mapped
In practiceThe session agencies know: a new client hands over an Unbounce account with six years of history. You ask, "Map the account: sub-accounts, page groups, and page counts, with lead volume by group this year." Your AI returns the map. Two groups produce everything; four are museum wings. You ask, "Which published pages captured zero leads this year, and does any spend point at them?" Eleven pages; the Gateway finds spend still touching two. The kickoff deck writes itself: here is your working layer, here is your waste, here is the cleanup list. The audit that justifies the engagement took the first afternoon, not the first month.
The return
What You Get Back
An inventory that exists
The estate mapped on demand, for the first time since it grew.
The working layer, named
Which pages earn the traffic, ranked by what they capture.
Waste, found
Silent pages and the spend still touching them, in one pass.
A provably whole pipeline
Leads verified from page to CRM, leaks located.
Use cases
One Conversation, Real Account Work
"Map our Unbounce account: groups, pages, and lead volume by group."Unbounce
The estate inventory as a visual report.
"Rank pages by leads captured this quarter."Unbounce
The production board for the conversion layer.
"Which published pages captured nothing in 90 days?"Unbounce
The cleanup list for the next builder session.
"Is ad spend still pointing at any of those silent pages?"Unbounce · Google Ads · Meta
The waste check across the estate and the platforms.
"Did this month's Unbounce leads all arrive in Salesforce?"Unbounce · Salesforce
The handoff verified end to end.
For in-house teams
Close the expectation gap
The account stops being a mystery inherited from previous campaigns. The working layer is known, the silent layer is listed, and cleanup happens from evidence.
For marketing teamsFor agencies
Run the whole book
Inherited accounts become mapped accounts by end of week one. Read every client estate from one connection with per-client permission walls, and make the audit, the waste check, and the handoff verification standing deliverables.
For agenciesReports worth sharing
From Live Account to Clear Story
Ask in chat and share the dashboard without building exports or taking screenshots.
Estate Map
Accounts, groups, pages, domains. Built for onboarding and audits.
Page Production Board
Leads by page and group, ranked. Built for the monthly review.
Waste and Handoff Report
Silent pages, touching spend, and CRM arrival checks. Built for the cleanup cycle.
The charts stay practical: table-first for the map, bar for production ranking. And when your team or clients want these anytime, the Data Visualization add-on turns your reports into always-current dashboards they open from a link. Ask in chat; share the dashboard.
The useful signals
The Numbers That Matter
A legible estate rests on five figures. Pages by lead volume: the working layer, ranked. Silent published pages: the archive-in-waiting, listed. Spend touching silence: the waste number that funds the cleanup. Handoff arrival rate: captured leads confirmed in the CRM, the pipe proven whole. And form profile: what the winning pages ask for, versus what the quiet ones demand. Read production monthly and the rest quarterly, plus the waste check whenever campaigns change. A read connector earns its keep by making these five effortless. Everything a builder session should fix arrives as a list, and every list is current, because it came from the account, not from memory.
A practical start
Your First Week
Day one: connect the accounts and draw the map. "Sub-accounts, groups, pages, with lead volume by group." Day two: rank the workers. "Pages by leads captured this quarter." Day three: list the silent. "Published pages with nothing in 90 days." Day four: run the two checks that pay for the week. "Any spend pointing at silent pages?" and "Did this month's leads reach the CRM?" Day five: schedule the rhythm. "Monthly, send the estate map and production board." By Friday, an account that resisted summary has one: working layer named, waste listed, pipeline verified. Cleanup happens in Unbounce with the lists in hand, and the next audit is a calendar event instead of an archaeology project.
Works best with
Build the Connected View
Pair Unbounce with Google Ads and Meta for the silent-page waste check, and with Salesforce or HubSpot to prove the capture-to-CRM pipe. Reading well beats guessing everywhere, and nowhere more than the layer where clicks become leads.
And the compounding effect deserves a line. The first estate map is a revelation; the second is a diff. By the third, the account simply stays known: new pages join the map on arrival, silence gets caught in a quarter, and no client ever again hands you a mystery. Reading well is a habit, and habits are what schedules are for. This connector turns the habit on and leaves it running.
Clear limits
What This Connector Will Not Do
It will not edit, publish, or unpublish pages; it is a read connector, and it says so rather than implying otherwise. It will not invent conversion data; leads and states are the account's own. It will not move your leads anywhere; it verifies the pipes your integrations already run. And it will not read accounts you did not connect.
Governance
Governed Access Your Whole Org Can Live With
Access is set per person, not per account, so Read seats see everything and change nothing while Write seats create and edit with your approval flow in front of every change. Delete access goes only to people you trust to clean up, and many teams start read-only, check answers against the platform, then widen access as the audit trail earns it.
You choose the level of human review and can change it at any time, while every action records what changed, when, and who approved it. Per-user access means Elements never stores your Unbounce password, and your data is never harvested or resold.
Per-user accessRead / write / delete per seatFull audit trailApproval flow on every change
Setup
Setup Takes Minutes
- Start your trialCreate your Elements account and connect it to your AI.
- Link UnbounceSign in through the secure connection screen and choose what to connect. No code and no engineers.
- Set permissionsDecide who can Read, who can Write, and who can Delete. Start conservative and widen as trust builds.
- Ask your first question"How did we do last month?" is a complete instruction.
Plans, account limits, and the multi-client Agency plan are on the pricing page .
FAQ
Unbounce Connector Questions
Why connect a read-only tool?
Because the estate's biggest cost is invisibility: unknown inventories, silent pages, unverified handoffs. Reading well fixes all three, and it cannot break a converting page while doing it.
Does it cover sub-accounts?
Yes: accounts and sub-accounts, with page groups and pages beneath them, which is what makes it fit agency structures cleanly.
Where do changes happen?
In Unbounce's builder, by your team, with the connector's lists and rankings in hand. Findings here, craft there.
Will my AI change things without asking me?
No. Your AI acts only with the permissions you set, and changes follow the review level you choose. Read-only seats cannot change anything, because the approval flow is the product working as designed.
Which AI assistants can our team use?
Your team can use Claude, ChatGPT, and Microsoft Copilot, while other AI tools can likely connect when they support MCP, the open standard for linking AI assistants to outside tools.
Is my data used to train anything?
No. Your data stays yours, so nothing is harvested and nothing is resold.
Focus on the Strategy, Delegate the Launch
The teams winning with AI are not handing their accounts to a black box; they keep the strategy and delegate the hands-on-keyboard work, while approvals and an audit trail make it safe to move fast. Connect the account you already have through the Gateway and ask the question you would normally build a report to answer.
Your first 14 days are free. Add your card to start, and cancel before the trial ends to pay nothing.