An Amplitude alternative for funnels

Before you get an answer

why did trial signups drop last week?

From nothing installed to a working funnel. Here is every move, both ways.

6

Amplitude steps

4

Tiny Funnel steps

Amplitude

1 Agree an event taxonomy with whoever owns it, and name each event
2 Install the SDK and wire up identity across web and app
3 Instrument each event in code, or turn on autocapture and pick from what it collects
4 Ship the release, then wait for real events to arrive
5 Build the funnel in Pathfinder or the Funnels report, one event per step
6 Set a conversion window and a counting method that fits the flow
🥱 A funnel, built on the events someone decided in advance were worth recording

Tiny Funnel

1 Paste one script tag into your site
2 Click through the flow yourself with the recorder on
3 Add a condition if a step needs one, like an element containing the word subscribed
4 Post the paid step from your backend when the purchase finishes there
💡 A live funnel, about two minutes after you started

built for answers, not data scientists

Tiny Funnel is obsessed with getting you answers as quickly as possible. The funnel is the page that loads when you log in, and any visitor's whole journey is one click away.

See your funnel from every angle

The main view is always your funnel. You choose which visitors and from when and where.

See a visitor's full journey

Where they came from, which campaign, every page they touched, and whether they bounced, came back later, or converted.

what each one does

Amplitude against Tiny Funnel, on the things that decide it.

Capability	Amplitude	Tiny Funnel
Time to a first funnel	Agree a taxonomy, install the SDK, instrument or autocapture, ship, then build the funnel once events arrive.	One script tag, then click through your own site with the recorder on. Live in about two minutes.
How a step is defined	An event, filtered by event or user properties. The event has to exist and be flowing before a step can use it.	A URL, a click, a page state, or a server event. Recorded by clicking, so nothing is instrumented first.
What the dashboard opens on	Your project's boards, saved charts and Pathfinder explorations. The funnel is a report you build and come back to.	The funnel. It is the page, not a report you go and find.
Who it is built for	Product and growth teams, usually with someone who owns the taxonomy and reads the platform daily.	A founder or a marketing lead who wants one answer this afternoon, with nobody dedicated to running the tool.
Behavioural depth	Pathfinder, predictive cohorts, session replay and experimentation, all in one product.	Not here, on purpose. One funnel view and the journeys behind it.
One visitor's journey	A per-user timeline, tied together by the identity you wire into the SDK.	Every visitor's full journey, return visits included, ending on the step they stopped at.
A step your backend confirms	Server-side SDKs and an ingestion API, with identity management in your hands.	Post the event with your own user id and it lands on the right visitor's journey.
Pricing	Free up to 2M events a month, then priced by monthly event volume. Seats are unlimited on every plan.	$10 a month per active funnel. No seats, no event budget, and pausing a funnel stops the bill.

Track a funnel • $10/mo

which one is yours

Both answer real questions. They are not the same question.

Stay on Amplitude if

There is an analyst or a data team here who already owns the taxonomy
Session replay, experimentation and cohort analysis are part of the job, not a nice-to-have
You are tracking a mobile app, where a script tag cannot go
Predictive segments and behavioural pathing are questions you actually ask
Unlimited seats on every plan matters more than a taxonomy-free start

Switch to Tiny Funnel if

The question is where visitors come from, how far they get, and who buys
Nobody here is going to design an event taxonomy to answer it
You sell software, a course or another virtual good
You want the funnel live this afternoon, not after a taxonomy meeting
There is no analyst, and there is not going to be one

what Amplitude does better

{"Behavioural depth" => "Pathfinder, predictive cohorts and pathing analysis we do not attempt"}
Session replay and experimentation bundled into the same product
Mobile SDKs for iOS and Android, where a script tag cannot go
A free tier that covers 2 million events a month, with unlimited seats on every plan
Governance features that matter once an organisation has more than one team reading the data
A serious published research and content operation, worth studying on its own terms

What to do in the first ten minutes

Leave Amplitude exactly where it is if it is already installed. Add the Tiny Funnel script tag next to it, then open the recorder and click through your own signup the way a customer would: the landing page, the pricing page, the signup form, the welcome screen. That click-through is the funnel. There is no taxonomy meeting first and nothing to name.

If the last step of your funnel finishes on a server rather than in a browser, a subscription webhook or an invoice paid on a schedule, post it as a server event with your own user id and it lands on the visitor who caused it, next to everything they did on the way there.

Amplitude is where a company arrives, not where it starts

Amplitude's own pitch has widened over the years: behavioural analytics, experimentation, session replay and a customer data platform, sold as one unified product. That breadth is real and a lot of it is genuinely good. It is also arithmetic, not incompetence: every product added is another concept the interface has to carry, and every concept is something somebody has to learn before the tool answers a question.

Our reader is usually not at that point yet. They have one question this Tuesday afternoon, where did these people come from, how far did they get, and who actually bought, and the honest answer is that Amplitude can tell them, once the taxonomy exists to ask it with. How per-event pricing changes what gets recorded is the same mechanism from the billing side: when an event costs money, you decide what is worth tracking before you know what you will want to ask, and the taxonomy tax shows up twice.

The short version

Keep Amplitude for the day a product org needs behavioural depth and has someone to run it. Use this for the funnel question today: one script tag, a click-through, and a live funnel in minutes. They can run side by side, and disagreeing on the numbers is information, not a bug.

frequently asked questions

Can I run Tiny Funnel and Amplitude at the same time?

Yes, and for a growing team that is a normal setup. Amplitude measures how people use the product once they are inside it. Tiny Funnel measures who arrives, how far down the funnel they get, and who buys. The two scripts do not interfere, so add the Tiny Funnel tag alongside the SDK you already have.

Do I need an event taxonomy before I can see a funnel?

No, and that is the whole difference in setup. A Tiny Funnel step is recorded by clicking through your own site, and can be a page view, a click, a page state or a server event, with optional conditions such as an element containing particular text. There is no naming convention to agree and no release to ship first.

Is Tiny Funnel a replacement for Amplitude?

Not for a team that needs it. There is no Pathfinder, no predictive cohorts, no session replay, no experimentation and no mobile SDK here. If those are the job, keep Amplitude. Tiny Funnel is the answer when the question is a marketing or signup funnel and a taxonomy is the thing standing between you and it.

Does Amplitude charge per seat?

No. Every Amplitude plan states unlimited seats, and pricing is metered by monthly event volume instead. If you have heard otherwise, that used to be closer to true and is not any more, so it is worth checking their pricing page directly before repeating it.

Will the two tools show me the same numbers?

Not exactly. An Amplitude funnel counts the events you instrumented, inside the conversion window and counting method you set. A Tiny Funnel funnel counts visitors reaching a step, where a step can be a URL, a click, a page state or a server event. Those are different definitions, so both tools can be right and still print different numbers.

Cookie-less means no consent banner, right?

Not something we can promise. Consent obligations depend on where you are and on everything else running on your site, and Tiny Funnel does keep a visitor id in local storage. What we can tell you is what it does. No cookies, no fingerprinting, no cross-site tracking, nothing shared with ad networks, and typed values never captured.

the bottom line

Two honest summaries, then the shortest way to decide.

Amplitude

Amplitude is where a product organisation arrives once usage analytics, behavioural depth and experimentation are genuinely the job, and there is someone whose role is to run it. It does that better than we ever will, because we are not building that product.

Tiny Funnel

Tiny Funnel is funnel analytics for the start, not the arrival. Where visitors come from, which of them buy, and how far and how often each cohort gets down your funnel, live within minutes and without a taxonomy meeting.

There is an analyst or a data team who owns the taxonomy

Amplitude

Session replay, experimentation or predictive cohorts are part of the job

Amplitude

I want the signup funnel live this afternoon, with nobody dedicated to running the tool

Tiny Funnel

The question is who buys, not how the product gets used

Tiny Funnel