Asana on your landing pages
Insurance agencies, B2B teams and agencies that run on Asana already have a home for work that needs an owner and a deadline. Paid leads usually skip it: they arrive by email, someone forwards them, and a week later nobody can say who called whom.
LanderLab's webhook creates the task through Asana's API the moment the form is sent: the lead's name and request as the task name, every answer in the notes, the campaign and variant in custom fields, an assignee already set. Your team works leads in the same project as everything else, and you can see which campaigns feed it.
Asana tasks that carry the whole quote request
Each lead becomes a task named for the person and the product, say Daniel Okoye · General liability, with the full set of answers in its notes: trade, number of employees, phone, email, the page they came from. A producer opens the task and has everything needed for the first call.
Every task is created in a project, so it lands where your process starts: one project per line of business, one per client, or a shared intake project your team triages each morning.
Custom fields for campaign, variant and source
Custom fields hold the campaign, the click ID and the A/B variant, one field each, so the project's list view can be sorted and filtered by them, and a fixed value like Paid search can mark every task a page creates.
Measure campaigns on quotes bound, not leads
With the campaign on every task and the outcome tracked in a section or a status field, an Asana report shows which ad sets produce bound policies or booked demos, not just form fills. A split test reads the same way: filter by variant and compare what closed.
For an agency, that report is the conversation with the client: here are the leads, here's what your team did with them, here's what each campaign produced.
Route leads before they reach Asana
If different leads belong in different projects, contractors in one and homeowners in another, LanderLab Workflows (beta) sort them first: a Switch node on the answer, an HTTP Request node per project, and a Runs view that shows where each lead went and whether any step failed.
