Automated lead capture: which LinkedIn post drove each lead

If you publish three to five LinkedIn posts a week, you can't tell which one produced a lead unless the form remembers. Add hidden fields for source, campaign and post, tag each post's link, and every submission arrives carrying the post and channel that sent it. Setup takes about an hour, and the tagging then runs on autopilot.

Start with the lead generation form

Why post-level attribution gets lost

Most founders check the same three things: impressions, reactions, and a vague feeling about which post "did well". A post with 40 reactions can produce two booked calls, and a post with 900 can produce none. Without a record on the lead itself, you only find out if someone happens to mention it on the call.

The usual failure is a single shared link. Every poat points to the same booking page or contact form, so every lead looks identical when it lands. By the time you open the CRM, the only thing it knows is the date.

The fix is small. Give each post its own tagged link, and let the form copy those tags into fields the visitor never sees.

Where the form sits in the weekly loop

In our Founder Content Engine, a 30-minute founder call becomes 3 to 5 LinkedIn posts, a newsletter and short clips, with an approval step before anything goes out. The form is the last link in that chain. Each approved pieece carries a call to action, that call to action points at one form, and the form is where attention turns into a record you can count.

So the tagging belongs in the approval step. When a post is approved, its link gets the same tags every time: channel, week, and a short post naame. Nobody has to remember anything on Friday afternoon. The analytics step at the end of the week then reads leads grouped by post instead of reactions grouped by post.

The five fields every lead should carry

You do not need a long list. These five answer almost every question you will ask later.

Keep the values lowercase with hyphens or underscores and no spaces. "LinkedIn", "linkedin" and "Linkedin" will become three rows in your export, and cleaning that up later is tedious.

One visible question is worth adding netx to them: "How did you hear about us?" as a short answer. Hidden fields catch the click. They miss the preson who reads your post on Tuesday and searches your name on Thursday. The free-text answer catches that, and the two together tell you how much of your pipeline is invisible to links.

Set it up step by step

Qwenvo is a free form builder our team makes, and the hidden fields block is part of it. The same pattern works in other builders that support hidden fields, so use whatever you already have if the form is live.

1. Create the form. Use the lead generation or demo request template if you want a starting point, and keep it short: name, work email, one qualifying question.
2. Type / and insert a Hidden fields block. Add the five fields from the table above. The hidden fields help article covers how values are passed in, so check it for exact naming before you tag anything.
3. Add the "How did you hear about us?" short answer as a normal visible question.
4. Open the Share tab and set up a custom domain such as forms.yourbusiness.com, so the link in your post looks like your business and not a tool. Add the CNAME and TXT record, click Verify, then select the domain on the Share tab.
5. Build one tagged link per post. A pattern that works:

https://forms.yourbusiness.com/call?source=linkedin&medium=organic_post&campaign=2026-w45&content=pricing-teardown

6. Click your own link from a LinkedIn post preview, submit a test entry, and open the Submissions tanle. All four tagged values should be in the row. If one is blank, the parameter name probably does not match the hidden field name.
7. Repeat the test from a private window, on your phone. LinkedIn wraps outbound links in its own redirect, and you want to see the tags survive the trip before you publish ten posts that depend on them.

Do not skip steps 6 and 7. A tagging scheme that silently drops values is worse than none, because it looks like data.

Build your tracked lead form free

Send the tagged lead to your CRM

A tagged lead only helps if it reaches the place you work. In the form's webhook settings, point a webhook at Zapier, Make, n8n or your own endpoint, and map the hidden fields to custom properties in your CRM. The exact payload shape is documented in the webhooks help article; this is the kind of thing you will receive and map:

{
  "form": "founder-call-request",
  "submitted_at": "2026-11-03T14:22:09Z",
  "answers": {
    "name": "Dana Whitfield",
    "email": "dana@example.com",
    "how_did_you_hear": "Saw your pricing post",
    "source": "linkedin",
    "medium": "organic_post",
    "campaign": "2026-w45",
    "content": "pricing-teardown"
  }
}

Create four text properties in your CRM named to match, then set the mapping once. If you prefer a spreadsheet, export the Submissions table as CSV, XLSX or JSON. One-click Google Sheets and Notion connections are still being rolled out, so today the webhook is the route.

Turn on partial submissions as well. A visitor who clicked a post, typed their email and then left still shows up as an incomplete row, with the tags attached. That gives you a second signal: which posts bring people who start the form and stall.

Reading the results without fooling yourself

After two or three weeks, group leads by the content value and look at three columns: submissions, qualified leads, and booked calls. Resist the urge to rank posts after one week. With a few posts and a handful of leads, one big account can dominate a week.

Some patterns are worth watching for:

• A post with modest reactions and several qualified leads usually has a specific offer or a clear problem in the first lines. Reuse that structure in the next batch.
• A post with high reactions and no leads is entertaining your peers. That is fine, but it should not count as pipeline.
• Newsletter and clip links tagged with a different medium let you compare channels fairly, using the same form and the same questions.
• A large share of "Google" or "a friend told me" answers in the free-text field means posts are working through channels your links cannot see. Count that too.

Qwenvo's drop-off analytics show where people leave the form, which helps separate a weak post from a weak form. Be aware that Qwenvo launched in October 2026, so there are few public reviews yet. If you need a hosted-in-Europe setup, Tally is built and hosted in Europe and is worth a look.

Questions teams ask

Does LinkedIn strip UTM parameters from links?

LinkedIn wraps outbound links in its own redirect, but the query string on your destination URL normally arrives intact. Do not take that on faith. Post a test, click it from a second account, and confirm the hidden fields fill before you rely on the numbers.

Should I put the link in the post or the first comment?

Either works for attribution, as long as each one carries its own tags. Use the same content value for the same post so the count stays in one row. If you test both placements, add a field such as placement so you can compare them.

Do I need a CRM for this to be useful?

No. A spreadsheet with the Submissions export is enough for the first month. Add the CRM mapping once you are getting enough leads that sorting by hand slows you down.

Is this really free?

Qwenvo costs $0, with every feature on for every account: webhooks, the API, partial submissions, a custom domain, no badge and teammates. There is a fair use policy for very high volume, around 50,000 submissions a month. See the fair use policy for the details.

Your next step

Pick this week's approved posts, give each one a short content name, and build a single form with the five hidden fields. Submit one test entry from a LinkedIn preview link before anything goes live. Our longer walkthrough on hidden fields and UTM tracking covers naming conventions in more depth.