Click actions
Know what users actually clicked. Wakeline records the buttons and elements people interacted with inside a guide, so you can tell what's working from what's being ignored.
Every click counted
See which calls-to-action and elements get the action.
Working vs. ignored
Tell apart the buttons that convert from the ones that don't.
Refine the copy
Double down on what gets clicks.
Live in three steps.
Add buttons
Build your guide with calls-to-action.
Ship it
Let users interact.
Read the clicks
See what landed.
Two buttons, one honest answer about intent.
Your launch modal offers "Try it now" and "Watch a demo". Which one users click is a product decision hiding in a guide — click actions surface it.
Instrument by building
Nothing to set up: every button and interactive element in a guide records clicks automatically. The buttons you already shipped are the experiment.
Read the split
Reports shows the tally: 68% "Try it now", 9% "Watch a demo", the rest dismissed. Your users want hands-on, not video — noted.
Act on the loser
Retire the demo button next launch and give the space to a second direct action. Or keep it and A/B the label — "2-min demo" versus "Watch a demo" — now that you know it is weak.
Cross-check with dismissals
High dismissal alongside low clicks means the moment is wrong, not the buttons. Click data reads best next to the funnel, not instead of it.
What to expect: Button-level truth about what users choose when offered. Compounded across guides, it becomes a house style: your users' revealed preference for direct action over explanation, or vice versa.
When not to use click actions.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
Analytics for your whole app
Click actions cover interactions inside Wakeline guides. For heatmaps of your product itself, use a product-analytics tool — or watch session replays, which capture the full page.
Verdicts from thin traffic
A 60/40 split over twenty clicks is a coin flip. Let real volume accumulate before rewriting your CTAs around it.
Counting clicks as success
A click is interest; the outcome you wanted lives after it. Pair the click with the destination's own numbers — the button that gets fewer clicks but better follow-through is often the winner.
What gets recorded?
Clicks on buttons and interactive elements inside your guides — which button, in which step, how many times — plus the button's action (next, open URL, complete, dismiss). It appears in the flow's Reports automatically; there is nothing to wire up.
Can I see which users clicked?
Guide events carry user identity where known, and "Who saw this guide" lists them. For a full picture of one user's behavior around the click, jump into their session replay.
How is this different from the funnel?
The funnel shows whether users progressed; click actions show what they chose. A step can hold 90% of users while everyone ignores the button you cared about — you want both lenses.
Do link clicks in step copy count too?
Interactive elements in guides record engagement — buttons are the primary unit, with open-URL actions making destinations measurable. Structure real choices as buttons rather than inline links when you intend to measure them.
Can click data feed my own analytics stack?
Yes — guide events, clicks included, are exportable via the warehouse export (NDJSON or CSV with BigQuery and Snowflake snippets) and can stream out through signed webhooks. Join button clicks against downstream conversion in your own models whenever Reports alone is not enough.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.