Segment on your landing pages
Segment is how many teams keep one stream of customer data: events come in once, from a source, and go out to every destination. LanderLab's webhook makes your landing pages one of those sources. Each lead is posted to Segment's HTTP Tracking API as a Track call, with the form's answers as properties and the visitor's IP, user agent, page and campaign in the context, so there's no connector to pay for and no Zap in the middle.
It suits teams where the landing page is the start of the customer record: SaaS demo and trial pages, ecom brands running quizzes, lead gen operations with a warehouse behind them. The lead lands in Segment next to everything else it knows about that person.
Landing page leads as Segment Track events
A Track call is Segment's way of saying something happened: here, "Lead Submitted", with the quiz answers and form fields as properties. The webhook's JSON mode builds the nested body Segment expects, so properties, traits and context land where Segment's spec puts them, and every destination reads them the way it reads your other events.
Use the person's email or your own ID as the userId, and the lead joins the same profile as the trial, the order or the app event that follows.
Campaign and page context for every destination
Segment's spec has a place for the campaign (source, medium, name, term, content) and for the page (its URL, path and referrer). Fill them from LanderLab's hidden fields and its own page URL, and every destination downstream receives a lead that already says which ad, which campaign and which landing page produced it.
Add the A/B variant as a property and your warehouse can compare variants on the outcomes that come later, not only on form fills.
Server-side delivery with the visitor's details
Because the event comes from LanderLab's server, Segment can't see the visitor's IP or browser on its own. LanderLab sends them: the visitor's IP and user agent go into the event's context, so geolocation and device data describe the person who filled the form, not a data center.
Judge campaigns on what happens after the form
Cost per lead is where most landing page reporting stops. With the lead event in Segment and the same person's later events next to it, the warehouse can answer the questions that pay the bills: which campaign's leads started trials, which variant's leads bought, which ad set brought in customers who stayed.
