How to Track Qualified Inquiries From Organic Social

TrueFuture Media · Measurement

A LinkedIn post shows how to replace a pump seal without removing the housing. The post gets clicks. Later, your sales team receives a request for a retrofit review. Can you tell whether that request followed the post, and whether the buyer had a system you could actually support? Those are two different questions. A tagged link can help answer the first. The team that reads the inquiry answers the second.

Clay figure sorts tabbed inquiry cards into a tray

How do you track qualified inquiries from organic social? Add consistent UTM tags to the links you share from unpaid posts. These tags are short labels for the source, medium, campaign, and content that sent the visit. Test that the labels reach your site and, where your setup and consent choices allow, the inquiry record in your customer relationship management system (CRM). Fire a lead event only after the form succeeds. Have sales mark each real, distinct request as qualified, not a fit, or still pending. Report link source and sales status together, but keep reader-reported sources separate from tracked ones. When neither is available, leave the source unknown. A recorded source shows the path you observed, not what caused the buyer to act.

For a complex product, the evidence that gets a click may be different from the evidence that gets a buyer to ask for help. An engineer might watch a retrofit demo, but wait to contact you until they see a compatibility chart. Measure the handoff as well as the post. TrueFuture’s Social Demand Loop shows where buyer proof, the next step, and inquiry capture fit together.

What counts as a qualified inquiry?

A qualified inquiry is a distinct request that someone has reviewed against criteria your team agreed on in advance. A person asking how much an industrial pump costs might be a buyer, a student, or a supplier. The form alone can’t tell you which. For a retrofit service, a useful starting rule might be: a company with a real site, a system in the supported range, and an active need to assess a retrofit. If the request doesn’t say what system they have, mark it pending instead of forcing a yes or no.

Give one person ownership of review, and keep inquiry status separate from source. That way a good project from an untagged visit can still qualify, and a tracked request outside your service area won’t count as a fit. Count a second submission about the same project once, but don’t automatically merge two different sites just because the same buyer filled out both forms.

The organic social inquiry pathA social link provides a source clue. Form success records an inquiry. A sales review decides whether the inquiry fits. 123 Tagged visitForm successSales review Records a source clueRecords a requestChecks whether it fits
Each step answers a different question. Don’t count a visit or a form submit as a qualified inquiry.

How should you tag links from organic social?

Take the URL for the page that answers the buyer’s question and add a small set of consistent labels. In Google’s campaign URL guidance, source identifies the referrer, medium describes the marketing channel or method, and campaign groups related activity. The content label can distinguish links within that activity. Google notes that UTM values are case sensitive. Pick one house style, such as lowercase words joined with hyphens, and reuse it.

UTM template for an illustrative seal replacement post
FieldExample valueWhat it tells you
utm_sourcelinkedinWhere you placed the link.
utm_mediumsocialThe medium in this example. Keep paid values distinct and check your own report grouping.
utm_campaignpump-retrofitThe buyer question or initiative grouping related posts.
utm_contentseal-replacement-demoThe specific post or placement this link was built for.

Example URL (replace the placeholder domain and path):

https://example.com/retrofit?utm_source=linkedin&utm_medium=social&utm_campaign=pump-retrofit&utm_content=seal-replacement-demo

Keep one row per published link in a shared sheet: platform, placement, destination, campaign, content label, publish date, and URL. If several posts tell readers to use the same profile link, label it as a profile link. Don’t assign a particular post credit the URL can’t establish. Likewise, a link copied into a group chat can retain its LinkedIn tag. The tag tells you how you labeled that link, not necessarily where the buyer last saw it.

Use campaign tags on links you distribute outside your site. Use your site events or ordinary page paths to understand internal navigation rather than adding a fresh campaign tag to every internal button. If the destination doesn’t continue the post’s promise, tracking will tell you where the path breaks, but won’t fix it. The social landing page guide explains how to carry the buyer question into the right proof and inquiry form.

Overhead view of hands typing on a laptop and writing in a notebook
Keep the naming rules with the link inventory, where the next person can find them. Photo by MJ Duford on Unsplash.

How do the tags reach the inquiry record?

A campaign can show up in Google Analytics 4 (GA4) even if your sales team never sees the tag. Website analytics and your CRM are different systems. Set up and test a way for allowed campaign values to reach the inquiry, through a supported form integration or mapped hidden fields. Hidden fields are values the system submits with the form without asking the buyer to fill them in. Don’t assume the form carries them simply because the address bar shows them.

Decide what moment the field represents before anyone builds it. A simple first version is source on the inquiry path: the tracked campaign evidence available when the request arrives. Keep that separate from a contact’s first known source and from what the person tells sales. In HubSpot, for instance, Original and Latest Traffic Source describe first and most recent known web sources, while Record Source describes how the record was created. Neither label automatically means “the post that drove this request.” A contact-level value can change while the facts about an old inquiry stay the same.

If your intake sits on another page or an outside booking tool, walk from the original post to that exact final step and inspect what the CRM receives. When a redirect or handoff drops tags, check whether that integration supports carrying the values you need. If it doesn’t, accept the gap or use a supported intake path. Don’t bypass privacy settings to fill in blanks. Google’s Analytics privacy guidance prohibits sending personally identifiable information, including email addresses, in data Google can recognize as such. Keep personal details and free-text inquiry notes in your authorized business system, not in tags, URLs, or Analytics event fields.

Use the success signal from the actual form or trusted integration as the trigger for generate_lead, which Google lists as a recommended event for a submission or information request. Don’t fire it on a button tap, a validation error, or a page reload. Keep qualification in the CRM unless you separately implement and validate an approved offline feedback workflow. Marking a form event as important in Analytics does not qualify the buyer.

What should you test before using the numbers?

Run a labeled test from the exact place you published the link, ideally in the mobile app your buyer uses. Then try the same path without tags. Look at the form result, the analytics event, and the inquiry row side by side. In GA4 DebugView, you can inspect events from a device in debug mode. Google cautions that DebugView has limited attribution analysis; use Acquisition reports for the later attribution check rather than treating the debug screen as your campaign report.

Minimum tests before you use the data
Run this pathLook for this result
Tagged link → valid requestDestination opens. The form succeeds. One test inquiry arrives with the expected source labels where allowed.
Tagged link → invalid formThe form shows an error. There’s no success event and no inquiry record.
Success → refresh or retryA refresh isn’t a new lead. A duplicate request about the same project doesn’t inflate the reviewed count.
Untagged link or tracking declinedThe form can still work. Missing source isn’t filled in by guessing or by bypassing the person’s choices.
Alternative route or deviceCheck redirect, a second page, or hosted form. Document what survives and what you cannot observe.

Repeat the useful cases after a form change, a new landing page, or a switch in link shortener. Exclude test rows from the review. If analytics and CRM counts don’t match, compare the same date range and form, then look for different consent conditions, duplicates, or other intake paths. One system may count events while the other counts distinct requests. You don’t have to force them to agree before you can explain why they differ.

A man working at a desk with a laptop and notebook
Record the expected and observed result for each path. Photo by Vitaly Gariev on Unsplash.

How do you read the results without overstating credit?

Group inquiries by when the request arrived, and decide how long sales has to review them. Keep pending cases visible. Next to the sales status, keep three kinds of source evidence distinct: tagged path, buyer-reported source, and unknown. If a form received a campaign tag and the person also told sales they saw the post, that is still one inquiry. Record both signals on the same row. If the tag says LinkedIn and the buyer says a coworker forwarded it, keep both. Those facts can coexist.

Worked example: a two-week retrofit review

Suppose the team receives 12 distinct retrofit inquiries. Five have a usable organic social tag, three mention an unpaid post but have no matching tag, and four have no usable source evidence. Of the five tagged requests, sales marks two qualified, two not a fit, and one pending. One of the buyer-reported requests also qualifies. These are example counts, not client results.

Report two qualified inquiries with a tagged social path, one more with buyer-reported social only, and one tagged inquiry still pending. Two out of five tagged inquiries qualified so far. If you’re looking at reviewed requests only, it’s two out of four; say which denominator you chose. Neither figure is a conversion rate from social views or proof that one post caused three inquiries.

Let the pattern tell you what to check next. If tagged requests arrive but rarely fit, compare the reasons sales records: a demo may be drawing attention from people with the wrong type of equipment. Test a post that states compatibility up front. If sales hears about the demo but every record is untagged, fix the route before declaring that the content did nothing. Once capture works, use the long buying cycle scorecard to compare what buyers ask and decide what evidence to make next.

Key takeaways

  • Use consistent UTM tags on external links, and label only the placement the link can identify.
  • Test the tags in the inquiry system, not just in the browser. Count successful submissions separately from sales qualification.
  • Review requests once per distinct project and keep pending cases visible.
  • Keep tagged, buyer-reported, and unknown source evidence separate. Track a path without claiming it caused the sale.

Frequently asked questions

Can I see which social post generated every inquiry?

No. A dedicated tagged link can show which link was used when the data survives. Someone might share it privately, return another day, or switch devices. Use the evidence you have and keep unknowns visible.

What if I can’t attach UTMs to the CRM record?

You can still check campaign traffic in analytics and ask an optional source question at intake. Report those separately. Don’t join traffic and inquiry rows by guesswork and present them as matches.

Should a booking or a form submit count as qualified?

Only after it meets the agreed review criteria. A booked meeting can still be outside your service area or unrelated to a product you sell. Count it as a booked meeting until you know more.

Start with one link and one form

Choose a post that answers a real buying question. Follow its link through to sales, and see if someone can tell what the buyer asked, what source evidence made it through, and whether the inquiry fits. Then repeat the test without a usable tag. You want the buyer to reach you either way.

If your buyers need to see how a product works before they take the next step, bring one recent post, its landing page, and the way sales reviews inquiries to a Fit Review. The Fit Review is a focused 20-minute conversation about what you sell and what buyers still need to understand.

Request a Fit Review

Sources

Media credits

The cover illustration and inquiry path diagram are by TrueFuture Media. The two workspace photos are by MJ Duford and Vitaly Gariev under the Unsplash License. Neither depicts a client or a measured result.

Next
Next

Sales Enablement Content: Build a One-Page Buyer Brief