Estate reads on demand
Workspaces, pages, states, domains, and leads, enumerated and ranked in conversation.
Instapage connector
Instapage MCP Connector – Experiments and Leads in One Question
Instapage is where the conversion work happens: the pages, the experiments, the leads that justify the ad spend upstream. And like every conversion layer, it grows opaque with success: more workspaces, more pages, more tests, and less certainty about what is live, what is winning, and what is quietly stale.
The Instapage connector restores the sightline. It links the AI you already use, like Claude, ChatGPT, or Copilot, to your Instapage workspaces through Mad Fish Elements, reading pages with their publication state, the experiments running on them, the leads they capture, and the domains they publish to. The layer that proves your marketing works becomes easy to see working.
See it
What Your AI Can See
Connect your workspaces, and your AI reads the conversion estate the way Instapage organizes it: workspace by workspace, page by page, with publication state, the experiments attached, lead capture, and domain publication.
The questions that keep the layer honest become sentences. "What is published in the campaigns workspace, and what does each page capture?" "Which experiments are running right now, and how long have they run?" That second one matters more than teams admit: tests that should have been called weeks ago keep splitting traffic long after the answer arrived. "Which pages stopped producing?" finds the stale layer. And the parity question runs through the Gateway: ads on one side, pages on the other, verified against each other before and during flight.
Do it
What Your AI Can Do
The Instapage connector is visibility-first, and the page says so plainly:
Experiment watching
What is testing, for how long, on which pages, surfaced on schedule so tests get called instead of forgotten.
Lead flow checks
Capture read per page, and verified downstream on the same Gateway: did the leads reach the CRM, or did the handoff leak?
Launch verification
The campaign's pages confirmed published on the right domains before spend starts.
Page design and experiment decisions stay in Instapage with your CRO flow. The connector makes the layer visible; your team makes it better.
A working session
The Test That Finally Got Called
In practiceThe session CRO teams recognize: you ask, "List running experiments with their start dates." Your AI returns four. One has run eleven weeks on a page whose traffic could decide it in three. You ask, "What is that page capturing, and is spend still pointed at it?" The Gateway answers both: steady leads, live spend from two campaigns. The test gets called in Instapage that afternoon, the winner takes all the traffic, and the conversion rate the ads pay for stops being diluted by a decided question. The connector did not run the test; it made sure someone remembered to end it.
The return
What You Get Back
Tests that conclude
Experiments watched on schedule, so decided questions stop splitting traffic.
An estate you can enumerate
Workspaces and pages, states and production, on demand.
Handoffs that hold
Leads verified from page to CRM, leaks found while small.
Flight-day certainty
Pages confirmed live on the right domains before the ads start paying.
Use cases
One Conversation, Real Account Work
"List running experiments with start dates and the pages they test."Instapage
The test inventory nobody was keeping.
"What is published in the fall-campaign workspace?"Instapage
The live estate for the flight, enumerated.
"Which pages captured leads this month, ranked?"Instapage
The production board for the conversion layer.
"Did this week's page leads arrive in HubSpot?"Instapage · HubSpot
The handoff verified end to end.
"Before launch, confirm the three campaign pages are live on the right domains."Instapage
The pre-flight check as a sentence.
For in-house teams
Close the expectation gap
The CRO program gets a memory: what is testing, what concluded, what produces. The team spends its time designing better pages instead of auditing old ones.
For marketing teamsFor agencies
Run the whole book
Client conversion layers are where campaign promises land. Watch every client's workspaces from one connection with per-client permission walls, call the overdue tests, and report page production beside the spend that fills them.
For agenciesReports worth sharing
From Live Account to Clear Story
Ask in chat and share the dashboard without building exports or taking screenshots.
Experiment Board
Running tests, ages, and the pages under test. Built for the weekly CRO review.
Page Production Report
Leads by page, ranked. Built for the monthly conversion review.
Launch Readiness Check
Campaign pages verified live. Built for flight mornings.
The charts stay practical: table-first for inventories, bar for page production, line for capture trends. 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
The conversion layer reads on a short list. Leads by page: production, ranked. Experiment age: how long each test has run, the number that calls overdue tests. Pages live by workspace: the flight inventory, verified. Handoff integrity: page leads confirmed into the CRM. And coverage: which live campaigns land on which pages, so nothing points nowhere. The habit: experiments weekly, production monthly, coverage and parity at every launch. Tests that conclude, pages that account for themselves, and handoffs that provably hold: that is a healthy conversion layer, and every part of it is a sentence here. The craft stays in the builder. The accountability just stopped depending on memory.
A practical start
Your First Week
Day one: connect the workspaces and list what is live. "Published pages by workspace." Day two: inventory the tests. "Running experiments with start dates." Note anything old enough to vote; day three: call one. Take the overdue test into Instapage and end it with the findings in hand. Day four: verify the handoff; "Did this week's leads arrive in the CRM?" Day five: schedule the rhythm. "Weekly, send the experiment board; before launches, the readiness check." By Friday, the conversion layer has a memory and a calendar: tests conclude, pages account for themselves, and flights start verified. Nothing about the craft changed. The visibility around the craft did, and that is usually what was missing.
Works best with
Build the Connected View
Pair Instapage with Google Ads and Meta so the pages and the spend that fills them stay in one view. Add HubSpot for the lead handoff check. A conversion layer is only as good as what reaches it and what leaves it; both live on this Gateway.
One more habit worth the calendar slot: the post-flight review. When a campaign ends, ask what its pages produced, which experiment settled, and what the winner taught. Ten minutes, three questions; the conversion layer gets smarter every flight, because the lessons stop evaporating between campaigns. Visibility during the flight, memory after it; both were always possible; now both are cheap.
Clear limits
What This Connector Will Not Do
It will not design pages or decide experiments; the craft and the calls stay with your CRO flow in Instapage. It will not fabricate test results; what it surfaces is the account's own state. It will not push traffic anywhere; it reads the layer the ads already fill. And it will not reach workspaces 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 Instapage 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 InstapageSign 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
Instapage Connector Questions
Is this read-focused on purpose?
Yes; the conversion layer's biggest operational failure is invisibility: forgotten tests, stale pages, leaking handoffs. Visibility on schedule fixes most of it, and the page claims exactly what the connector does.
How does workspace scoping work?
The connector reads the workspaces your connection authorizes, and Elements' per-person permissions decide who can ask. Agencies map client walls to workspaces cleanly.
Can it tell me which experiment variant is winning?
It surfaces the experiments and their pages so the overdue ones get attention; reading the results and making the call happens in Instapage, where your CRO team already judges them.
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.