When an inquiry arrives from your website, the first question is usually where it came from. If that answer is not captured at the moment of submission, it is gone, and any later guess is just a guess. Tracking the source at the point of capture is what makes the rest of your reporting possible

Sending form submissions to a shared inbox records the message, but rarely the campaign, the referring page or the landing page that produced it. The result is a list of inquiries with no reliable way to tell which parts of your marketing actually worked

Attribution usually breaks in one of three places: the form does not carry the campaign parameters, the submission is stored without the page it came from, or the data is copied into a tool that drops the original context. Each step quietly removes information that cannot be recovered later

Why attribution gets lost

Fixing this does not require a large analytics platform. It requires deciding exactly which fields matter and keeping them attached to the lead from the first submission onward

Once the fields are chosen, they need to survive the trip from the browser to your records. The most reliable approach is to resolve the organization and the site on the server when the form is submitted, then store the lead with its acquisition context in one place

• Source: where the visitor came from, for example a search engine, a social network or a direct visit

• Medium: the channel that carried the visit, such as organic, paid or email

• Campaign: the specific campaign name when the link includes one

• Landing page: the first page the visitor saw before submitting the form

• Referrer: the site that linked to yours when a visitor arrives from elsewhere

What to capture on every inquiry

Sending submissions only to a shared inbox removes the context before anyone can use it. The fields have to be captured in the same request as the form and stored with the lead, not somewhere beside it

Reports can then be built from a single record instead of reconciling exports from several tools. That is the difference between reporting and guesswork

Keep these fields on every lead:

• Source, medium and campaign

• Landing page and referrer

• Status from new to closed

Attribution in practice: a worked example

Suppose a visitor finds your site through an Instagram post, lands on a service page and submits the contact form a minute later. If the form captures the campaign and the landing page, the lead arrives labelled with both. If it captures nothing, the inquiry arrives as an email with no story

Putting it together

The setup is small and repeatable: capture the context, store the lead against the site, then review the reports before deciding where to invest more

• Capture the context at submission so it does not depend on memory or manual notes

• Store the lead with that context so every later report starts from the same data

Step 1 - Capture the context at submission

Read the campaign parameters and the referrer before the form is submitted, and include them in the same request. There is no need to ask the visitor for this information; the browser already has most of it

Step 2 - Store the lead against the site

Resolve the organization and the site on the server, then write the lead to your database with the context attached. This keeps ownership clear when one organization operates several websites

Step 3 - Review reports before spending

• Compare sources over the same period so the numbers remain comparable

• Look at closed leads, not only new ones, to see which sources produce real outcomes

None of this is complicated, but it depends on capturing the context once, at the right moment, and keeping it attached. A website that does this can answer a simple question with evidence: which sources are worth investing in?

Common mistakes to avoid

Sending submissions only to a shared inbox removes the context before anyone can use it. Copying leads into a spreadsheet by hand introduces delays and errors, and the original campaign data is usually lost in the process

A smaller, consistent set of fields is more useful than a large one nobody maintains. Decide the fields once, apply them to every site, and keep the same status model across the organization

• Do not rely on the form email as your lead record

• Do not mix different status models across sites

Frequently asked: which sources should I compare?

Start with the channels you already invest in, such as search, social and referrals, and compare them over the same period. If a channel produces inquiries but few closed leads, that is useful evidence too, and it usually points to a follow-up problem rather than a traffic problem