Getting started

RetaFunnel records what people do on your landing pages, quizzes and video sales pages (how far they scroll, how much video they watch, which buttons they click, which forms they fill) and turns that behaviour into audiences and conversion events for Meta and Google. This guide takes you from sign-up to a launched funnel. There are two ways to install it: paste one line of code yourself, or hand a setup link to the AI agent that builds your pages.

Before you start#

You need:

• A page that is online (or about to be), on a domain you control. Something like https://www.yourbrand.com/offer.
• A way to add one line of code inside the <head> of that page: your page builder's "custom code" or "header code" box, your developer, or the AI agent that writes the page.
• Twenty minutes.

You do not need a Meta or Google connection to start. Tracking works on its own; the ad connections come later (see Connect Meta and Connect Google Ads).

The 5-minute path#

1. Create your account and workspace#

1. Open app.retafunnel.com/sign-up, enter your email and a password, confirm the email if you are asked to.
2. The first screen says Welcome to RetaFunnel. Type a Workspace name (your brand, or your client's brand if you are an agency) and continue.

A workspace is one business: its sites, funnels, segments, ad connections and team. You can create more later from the workspace switcher at the top of the left sidebar. Keep one workspace per client so their data and ad accounts never mix.

2. Create a site#

A site is one domain (or one group of pages that share the same tracking code).

1. In the left sidebar click Sites, then New site.
2. Name: anything you like, for example Main funnel.
3. Domain (optional): www.yourbrand.com.
4. Allowed origins: the addresses that are allowed to send data with this site's key, one per line, written as https://www.yourbrand.com (scheme and host, no path). Add every domain of the funnel, including a separate checkout or booking domain if you use one. Why it matters: the site key is visible in your page's code, so this list is what stops someone else from sending junk data with it. If you leave it empty, any origin is accepted; fine for a first test, tighten it before launch.
5. Consent mode: how the tracker behaves before a visitor accepts cookies.
   • Auto (recommended): the visit is measured anonymously until the visitor accepts cookies on your cookie banner, then the full tracking switches on. Cookiebot, Iubenda and Complianz banners are detected automatically.
   • Implied: full tracking from the first page view. Use only where your legal advice allows it.
   • Strict: nothing is sent until consent is given.
6. Leave Allow raw PII on identify off unless your CRM needs plain email addresses. Off means RetaFunnel stores only a one-way hash (a fingerprint) of emails and phone numbers, never the values.
7. Click Create. You land on the site page, on the Install tab.

3. Install the script tag#

The Install tab shows a single line that looks like this:

<script src="https://t.retafunnel.com/rf.js" data-site="rf_xxxxxxxxxxxx" defer></script>

1. Click the copy button next to it.
2. Paste it inside the <head> of every page of the funnel. In most page builders this is a box called "Custom code", "Header code" or "Head tracking code" (the FAQ has the exact place for WordPress, ClickFunnels and Webflow).
3. Publish the page.

That one line already records page views, scroll depth, time on page, clicks on buttons and links, form starts and submissions, HTML5, Vimeo and YouTube video progress, Calendly bookings and the ad parameters (UTMs, fbclid, gclid) of every visit. To give your buttons, forms and videos stable names (so a segment like "watched 50% of the video but did not opt in" works), the page needs a few extra attributes; the Instrumentation guide lists them, and an AI agent adds them for you (see "With an AI agent" below).

4. Verify with a test visit#

Never guess whether tracking works: prove it, without polluting your real data.

1. Open your page in a new tab with ?_rf_test=1 added to the address, for example https://www.yourbrand.com/offer?_rf_test=1. Everything you do in that tab is now a test session: stored, visible to you, but excluded from every report, segment and ad sync, and deleted after 7 days.
2. Behave like a visitor: scroll to the bottom, click the main button, play the video past the middle, fill the form with an address like test+1@retafunnel.test.
3. Back in RetaFunnel go to Sites, open your site, click the Test mode tab.
4. Under Page under test pick the page (or paste its URL) and click the button that loads the test plan: the list of events this page should produce.
5. Click Start watching. Your test session appears with each expected event marked received, missing or malformed, plus the "facts" RetaFunnel computed (scroll %, video %, whether you became a lead).
6. Anything missing means an element is not tracked yet: usually a button or form without a data-track attribute. Fix the page and repeat.

Prefer not to edit the URL? Turn on site-level test mode on the same tab (default 30 minutes): while it is on, every visit to the site is stored as test data, so you can click through the funnel normally.

5. Create a funnel from a template#

A funnel is the ordered list of steps you expect a visitor to go through. RetaFunnel checks every session against it and shows where people drop off.

1. Sidebar → Funnels → New funnel.
2. Pick a template: VSL funnel, Quiz funnel, Lead-form funnel, Webinar funnel or E-commerce funnel. Each one comes with its steps, the page types it expects and a set of ready-made retargeting segments (for example "VSL 50% – no lead").
3. Choose the Site, give the funnel a Name, and optionally a Base URL (https://www.yourbrand.com) so the steps match only your domain.
4. Click Use this template. The funnel is created as a draft.

You can edit steps later (funnel → Edit): a step can be a page URL pattern, an event like a button click, a video milestone, a lead, or an outcome such as a booked call or a purchase.

6. Run the pre-launch checklist and launch#

Open the funnel. The Pre-launch checklist panel lists what must be true before going live:

Below those are warnings (Meta connected, a segment syncing, an outcome source such as Stripe or a CSV import). They do not block the launch; they tell you what is still worth doing.

Click Launch. If a required check fails you get "Launch anyway?"; it is better to fix the check first. Launching marks the funnel live and adds a marker on every chart so you can see the before and after.

With an AI agent#

If an AI agent (Claude Code, Claude Desktop, Cursor or any tool that supports MCP) builds or edits your pages, let it do steps 2 to 6 for you:

1. Sidebar → Integrations → card AI setup link → Create link. Give it a name, keep the default scopes (setup + read; add write if the agent should also create segments and switch on ad syncs), choose an expiry and create it.
2. Copy the one-line prompt shown and paste it into your agent's chat, in the project that contains your page files. It reads: Integrate RetaFunnel analytics on this page: https://mcp.retafunnel.com/connect/… (workspace: Your Brand)
3. The agent connects, creates the site and funnel, adds the tracking attributes to your HTML, runs a test session, verifies every event, creates the default retargeting segments and runs the checklist. It reports back what passed and what still needs you (for example the Meta token).
4. Revoke the link from the same card when the work is done.

Full detail, including how to read the agent's test report: Set up with an AI agent.

What to do next#

• Watch the first real sessions arrive on Overview (within a minute of the first visit) and read the pages with Reading the dashboard.
• Connect your ad account so segments become audiences: Connect Meta, Connect Google Ads.
• Bring sales in so you can see which ad produced revenue: Sales, CRM and attribution.
• Put the ad URL parameters on your ads (Ads page → Ad URL templates) so campaigns, ad sets and ads appear by name.

Common problems#

"No live data yet" on Overview. Either no one visited a page with the tag outside test mode yet, or site-level test mode is still on (every visit is then stored as test data), or the date range and site filter at the top exclude the data. Turn the Show test data switch on to see your test sessions; turn it off for live data.

Install health says "No events yet". Open the page in a private window, check the page source contains the script tag with your site key (rf_…), and that the page address is in the site's allowed origins (a wrong origin makes the server refuse the data). Wait a minute and refresh.

Everything is "missing" in the test plan except pageview and scroll. The buttons, form and video have no data-track, data-track-form or data-video-id attributes. Ask the agent to run the instrumentation step, or add them following the Instrumentation guide.

The form submission shows but there is no lead. The form has no field recognised as email or phone (type="email", type="tel", or a field whose name contains "mail", "phone" or "tel"). Rename the field or add data-track-form="optin_main" with a proper email input.

My thank-you page is on another domain and the visitor becomes a new visitor. Add the second domain to the site's allowed origins and to the data-domains attribute of the script tag; the tracker then carries the visitor id across the hop.