Funnel behaviour analytics + retargeting
RetaFunnel records how people move through your landing pages, quizzes and VSLs: scroll depth, seconds of video, quiz answers, clicks, forms. Then it turns that behaviour into audiences and conversion events for Meta and Google, server-side.
01 How it works
No tag manager, no event plan, no data layer. The tracker infers the funnel from the page: videos, quiz steps, forms and buttons are picked up automatically or marked with one attribute.
Paste one script tag, or give your agent the connect link. It adds the tag, marks every CTA, video and form, and verifies each event in test mode.
<!-- that is the whole install -->
<script src="https://t.retafunnel.com/rf.js"
data-site="SITE_KEY" defer></script>Scroll depth, seconds watched on HTML5, Vimeo and YouTube players, quiz steps and answers, clicks, active time, forms, bookings and purchases, per session and per person.
-- one wide row per session
max_scroll_pct 75
max_video_pct 58
quiz_last_step 4 / 7
clicked cta_hero, cta_pricing
is_lead falseDescribe a segment in behaviour terms. RetaFunnel syncs it to Meta and Google as an audience or conversion event, and ties later sales back to the ad that started it.
-- segment rule
all: [ max_video_pct >= 50,
is_lead = false ]
sync: meta.capi Seg_VSL50_NoLead
google.customer_match02 Product
Built for landing pages, quizzes, VSLs and lead forms, where the question is never "how many pageviews" but "who watched enough to be worth a second ad".
Scroll milestones, video milestones on HTML5, Vimeo and YouTube, quiz steps and answers, clicks, active time, form start and submit, Calendly bookings, purchases.
Any combination of what people did, over sessions, visitors or identified persons. Templates for the usual suspects: VSL 25/50/75% non-leads, quiz abandoners by step, high-intent non-converters.
Each segment becomes a Conversions API event for anonymous visitors and a Custom Audience or Customer Match list for identified people. Standard Lead, Schedule and Purchase events go server-side too.
Campaign, ad set and ad, with the names pulled from Meta and Google, next to spend, cost per lead, ROAS and the behaviour metrics for the traffic each one sent.
Hidden fields carry the visitor id into your CRM. Sales come back by webhook (Stripe, Calendly, any CRM or Zapier), CSV import or by hand. First-touch, last-touch and linear models over windows up to 180 days, with a touch timeline per lead.
A variant from the URL, the script tag or one call. Every report filters by variant; the experiment page shows lead rate, revenue, uplift and a two-proportion p-value.
Reach per 5% band of the page, two funnels or two pages side by side, and every chart with the previous period ghosted behind it.
Launch is enabled when the tracker is live, every step is registered, a test session passed and test mode is off. Start from VSL, quiz, lead-form, webinar or checkout templates.
Markers on every time chart for page changes, campaigns and incidents. Written automatically when a funnel launches, an experiment starts or a page is re-instrumented.
03 Built for AI agents
RetaFunnel ships an MCP server with 51 tools and 6 resources. Paste one line into Claude Code, Cursor or any MCP client: the agent creates the site and funnel, edits the HTML so every element is tracked, verifies each event in test mode, creates the default retargeting segments and launches. No dashboard clicks.
instrument_html applies rules, not a model call, so the markup is predictable and lintable.› Integrate analytics: https://mcp.retafunnel.com/connect/k_7f3a… (workspace: Brand X) ● get_onboarding_guide(vsl)● ensure_site(brandx.com) site_key sk_… script tag inserted● instrument_html(index.html) 14 changes · 6 CTAs · 1 video · 1 form● validate_html pass● set_test_mode(30 min)● verify_test_session ✓ pageview + attribution ✓ scroll 25 50 75 100 ✓ video 10 → 100 vsl_main ✓ cta_hero cta_pricing cta_footer ✓ form_submit optin_main ✓ identify (sha256)● create_default_segments 4 segments · Meta sync on● launch_funnel checklist 7/7 · live Done. Site key, funnel id and segments are in the dashboard.
04 Sales attribution
Lead-form funnels lose the story the moment the form is submitted. RetaFunnel fills hidden fields with the visitor id and attribution, matches later sales by hashed email or phone, and attributes revenue back to the sessions and ads that led there.
fbc capturedcta_pricing, left without opting ingclid · form with hidden fs_visitor_id→ Meta Purchase · Google offline conv.05 Test mode and privacy
Test mode
Flag a session with ?_rf_test=1, a data-test attribute, or switch the whole site into test mode for 30 minutes and click through the funnel yourself. Test rows are isolated at ingest, excluded from every report, segment refresh and Meta or Google sync, and purged after 7 days.
| pageview + attribution | received |
| scroll 25 / 50 / 75 / 100 | 4 / 4 |
| video vsl_main 10 → 100 | 6 / 6 |
| click cta_footer | missing · fix suggested |
| form_submit + identify | received |
Privacy
Data lives in Frankfurt. Each site picks a consent level, auto, implied or strict, and any page can override it. Emails and phones are hashed with SHA-256 before storage, IPs truncated to /24, and every workspace sets its own retention. A deletion endpoint cascades through sessions, persons and synced audiences.
fs.consent().06 Pricing
A session is one visit to one of your sites, up to 30 minutes of inactivity. Test sessions are never counted.
All plans: data hosted in the EU (Frankfurt), consent modes per site and page, hashed identifiers and per-workspace retention. Prices exclude VAT.
07 Questions
No. Keep them for standard events if you like. RetaFunnel reads the existing _fbp and _fbc cookies when a pixel is present, sends its own events server-side through the Conversions API and deduplicates with event_id. What it adds is the behaviour layer: audiences built from what people watched, scrolled, answered and clicked.
The script is 6.5 KB gzipped with no dependencies and loads with defer. It batches events every 5 seconds and on exit via sendBeacon, so a typical session produces three to five small requests. Video player APIs are loaded only when a Vimeo or YouTube embed is on the page.
Buttons, links, forms and videos are detected automatically and named from their id or text. For precise names you add one attribute: data-track="cta_hero", data-quiz-step="3", data-video-id="vsl_main". An AI agent using the MCP server adds these for you and validates the page.
Yes. For anonymous visitors each synced segment fires a Conversions API event named after it, with fbp, fbc, client IP and user agent. In Meta you build a Website Custom Audience on that event. Identified people are added to Custom Audiences and Google Customer Match lists by hashed email or phone.
In Frankfurt, on Supabase, behind Cloudflare Workers. Each site chooses a consent level: auto measures the session anonymously until consent is granted and then upgrades it in place, implied tracks from the first pageview, strict sends nothing until consent. Any page can override the site default. Identifiers are hashed, IPs truncated, retention is yours to set.
Any MCP-capable client: Claude Code, Claude Desktop, Cursor or your own agents. The server speaks Streamable HTTP and ships a stdio wrapper for local use. Its instructions and an onboarding://start resource tell the agent the exact procedure, so it does not need to know the product beforehand.
Install in a minute, or hand the connect link to your agent. Free to start, test mode included, data in the EU.
<script src="https://t.retafunnel.com/rf.js" data-site="SITE_KEY" defer></script>