Notion on your landing pages
A lot of small teams run their pipeline in Notion: a law firm's intake board, an agency's client tracker, a sales team that never bought a CRM. What they lack is a clean way in. Leads arrive as emails or exports, and someone retypes them into the database, late and with typos.
LanderLab's webhook posts each lead to Notion's API, so every submit becomes a page in your database with the answers filled into its properties. All your team notices is new cards on the board, each with the campaign and the variant that produced it.
Notion database properties filled from your form
Notion is strict about property types, and for lead data that's a good thing. The lead's name becomes the page title, the email lands in an email property you can click, the phone number in a phone property, the landing page in a URL property. Nothing arrives as one long block of text someone has to split by hand.
Because each lead is a real Notion page, your team can write call notes, attach documents and mention a colleague right under the properties the form filled in. The record and the conversation about it live in the same place.
An intake board your team works from
Add a Status property and every new page starts in the column you choose, say New. Group a board view by Status and the morning's leads are a column of cards your intake team moves to Contacted, Qualified and Signed. A calendar view on a callback date shows who to ring today.
Different people can see different slices of the same database: the intake team a board of New leads, the attorney a table of Qualified cases, the owner a view grouped by campaign.
Judge ad sets on signed cases, not form fills
Hidden fields named utm_source, utm_campaign and gclid or fbclid fill from the ad's URL and travel with the lead, and LL Variant ID records which version of the page the visitor saw. In Notion that's a set of properties you can group and filter by.
Filter the database to one campaign and count the Signed cards, and you know what that ad set really produced. Run the same filter on two variants of a split test and you can keep the page that brings cases, even if it brings fewer form fills.
Rules before the lead reaches Notion
Not every lead belongs in the same database. LanderLab Workflows (beta) can sit in front: a Filter node that only passes completed quizzes, a Switch node that sends personal injury leads to one database and workers' comp to another, each through its own HTTP Request node. The Runs view shows each lead's path, so a failed send is easy to spot.
