How convertlyft works: what happens after the tag lands

Page by page, what you actually see

The analytics half is the reports. The conversion rate optimization half is what follows them: a finding, a suggested fix, and a way to ship it. Every page below is named as it appears in the side menu.

Install: three ways to add the line

After sign-up a four-step setup opens: Your site, Add the tag, Check, Done. Every step can be skipped. It asks for your site address first, looks at the homepage to see what the site is built with, and leads with the instructions for that platform. There are three ways to add the line: paste it into your site’s head yourself; paste a paragraph into Lovable, Bolt, v0 or whatever built the site, which says exactly what to add and to change nothing else; or, once GitHub is connected on Connections and a repository is picked, let us open a draft pull request. A person on your side merges it, never Convertlyft. Then press Check. GitLab shows “Not available yet”.

Shopify: two pastes

On a Shopify store the line goes in the theme, and a second script goes in Shopify admin under Settings → Customer events as a custom pixel. Shopify’s checkout and thank-you pages do not run your theme’s code, so the first line cannot see a sale; the second paste is what counts purchases. The Install page shows both, with your key already filled in, when it recognises a Shopify store. If someone buys without having browsed the store in the same visit, we count the sale but cannot tie it to a visit.

Live and Home: is data arriving?

Live is the human check: the last 60 events as they land, refreshed every 5 seconds, internal traffic excluded. Home has three cards — Visitors, Converted sessions, Conversion rate — each with a per-day sparkline, plus where people come from, phone or computer, the top pages, and visitors by country. A session counts as converted only when the purchase event you mapped actually reaches us; when none did, the page says so in amber.

Analytics, Sessions and Paths: the website conversion rate, by source

Analytics adds conversion rate by entry channel, campaign tags, and “Search (Google)” from Search Console (finalised about two days late), plus scroll depth and an event explorer. Sessions lists every visit newest first, up to 200 shown; Paths ranks the top 10 entry and exit pages and the top 25 page-to-page moves. Nothing is sampled; the lists are capped, and the pages say so on screen.

Where the conversion funnel leaks

On Funnels a funnel is up to 6 steps, each an event with an optional “Page contains” filter; people are counted once per step and only if they did the earlier steps first. The biggest step-to-step loss prints in amber: “Biggest leak: step N→N+1 — X people left”. Amber marks any step fewer than 50 in 100 people went on from. “Open recordings” sits beside the leak; it opens every recording in the date range — the page says it cannot yet narrow them to the people who left at one step. Suggested funnels carry their own caveat on screen: we picked the steps, nobody has confirmed them.

Session replays and heatmaps

Replays shows the newest 100, with filters for Converted, Crashed, Has friction and 30 seconds or longer. Default recordings capture structure and interaction only — words drawn as bars, typed values never; visual replay is an opt-in that loads images from your live site. Recordings are kept 30 days. Heatmaps are pointer positions, not clicks — the page says to read them as where people stopped moving — drawn over a screenshot taken by a nightly run; the page shows when the next capture starts, and “Photograph this page” queues a page it missed.

Errors, Site health and Friction

Errors groups JavaScript errors into issues, each with events, sessions and people, split into your site’s code versus external issues. The page says it: “there is no resolve button here yet.” Site health rates LCP, INP and CLS, with FCP and TTFB alongside, for the typical visitor (p75) against Google’s thresholds, and lists the slowest pages. Friction lists dead and rage clicks per page per thousand views, with sample replays.

Digests: one briefing a day at 06:00 UTC

The digest job runs every day at 06:00 UTC over the previous complete UTC day; on Mondays a weekly email goes out at 06:30 UTC. Digests keeps the record: one card per day, one row per finding with one link, and a “Watched” line of visits, pageviews, pages seen, funnel steps checked and new issues. A quiet day reads “Nothing leaked above noise level.” Each finding compares a day to its own trailing 7-day normal — it carries no change marker, so it never attributes a move to a deploy. Alerts you set are looked at once a day and ride the daily email. Destinations sends findings to Telegram or to an email address as well; sending them to your own address as JSON is part of the paid plans, which are not open yet, and Slack is not connected yet. There is no SMS.

What to do and Tasks

What to do is fed by a run over the last 7 complete days. The header names the week, when it was computed, and how many findings were held back as too small to trust. Each row carries a severity chip (Fix, Watch or Note), the measurement, a suggested fix where the rule has one, and an effort chip. The buttons are View, More details, “Copy prompt for your AI agent” (written locally — no AI ran and it costs nothing), Add to tasks, Mark done and Dismiss. Tasks is a board: To do, In progress, Done. There is no draft PR, no approve button and no ship step on this path. Convertlyft does not claim that a shipped fix improved a number.

Ask: a question in plain words

Ask answers a question about your own numbers: visits, funnels, errors, slow pages, clicks that did nothing, and search data already pulled. Today it reads, keeps a decision or preference you tell it, and can do a few small jobs you ask for, such as setting up a funnel, adding a task or drafting a swap. A swap it drafts is saved but not live until you turn it on. It cannot disconnect anything or change who has access.

Swaps: different words for different visitors

Swaps changes a headline or other copy for the people you choose — where they came from, the campaign tag on their link, whether they have been before, the size of their window — without a deploy. It needs its own line of code, which is not the same as the install line; the Swaps page gives it to you. Up to 10 can be live at once. It refuses to swap a price, a stock level, legal text or a claim about your business. These are rules, not experiments: there is no split test yet, and we do not report what a swap did to your numbers.