Switching guide

Moving from Funnelytics to MapIntact

If your team already maps journeys in Funnelytics, the concepts carry over one to one and the tracking calls carry over unchanged. Here is what is the same, what is different, and the order to do the switch in.

What is the same

The canvas
Traffic sources, pages with screenshots, actions, purchases, offline steps, notes, and lanes. Same vocabulary, same drag and drop.
Templates
Lead magnet, webinar, VSL, tripwire, application, ecommerce, SaaS, local, and reporting layouts, each with benchmarks and a checklist.
Forecast
Per-edge conversion assumptions, traffic and cost per source, offer prices and refunds. Revenue, spend, profit, CAC, and ROAS on the canvas.
Tracking overlay
People, sessions, flow, conversion, revenue, and cost modes, with date ranges, segments, and a compare view.
Explorer
Drag forward or backward from any step to see the real next and previous pages, then add them to the canvas in one click.
Share links
Read-only canvases with optional password and expiry, plus PDF and PNG export.

What is different

Setup Assistant
Platform detection, guided install, headless verification, a live listener for forms and purchases, and scheduled health replays. Setup is a wizard, not a help article.
A free tier
Three canvases, one site, and 2,000 sessions a month, forever. Not a trial.
Annual pricing
Every paid plan has a published annual price with two months free.
Sessions metering
Plans are sized by tracked sessions, with a published overage rate. Tracking features are not gated by tier.
Compat API
Your existing trigger and commerce calls keep working. Nested objects in event properties are accepted too.
Tracking-health alerts
If a mapped event stops firing, you get an alert, and the Analyst checks tracking before it explains a drop.

Your events keep working

The MapIntact script exposes a compatibility shim. Calls to the Funnelytics trigger method and the commerce action payload are accepted as-is and mapped to MapIntact events, so nothing in your pages, Tag Manager, or checkout has to change on day one.

// Funnelytics-style calls keep working unchanged:
window.funnelytics.events.trigger('Add to Cart', { productName: 'Cool Snowboard' });
window.funnelytics.events.trigger('__commerce_action__', { __total_in_cents__: 49700, __order__: 'ORD-1001', __currency__: 'USD', __label__: 'Signature program' });

When you are ready, the native calls are shorter and accept nested objects:

mi('event', 'Add to Cart', { productName: 'Cool Snowboard', productPrice: 999, currency: 'USD', quantity: 1 });
mi('purchase', { value: 497, currency: 'USD', orderId: 'ORD-1001', label: 'Signature program' });

Full tracking docs

The switch, in five steps

1
Export what you can
Take screenshots or PDFs of each canvas, and copy your forecast assumptions. Canvas import is manual for now (see the note below).
2
Create the site and run the Setup Assistant
Add the domain, pick the install path, and let verification confirm a pageview reaches the collector.
3
Swap the script
Remove the old base script from Tag Manager or the theme, publish, and confirm with the Setup Assistant that exactly one script fires.
4
Leave custom events alone
The compat shim accepts the existing calls unchanged. Verify each one in the live listener and name the node.
5
Rebuild the canvas from a template or Map My Site
Start from the matching template, or paste the domain and let Map My Site place every page. Draw the edges, set the forecast, and share the link.

A note on canvas import. There is no file format we can import from Funnelytics today, so canvases are rebuilt by hand. The fastest path is a matching template or Map My Site, which places every page on your domain with a thumbnail in about a minute. Most teams rebuild a canvas in under fifteen minutes. If an export format becomes available we will add an importer.

Start with one site, free

Run the Setup Assistant next to your existing install and compare the numbers before you switch anything off.

Start free Browse templates