This is the final part. You have designed the exchange, placed the form, made the mail arrive, written the first reply, filtered the spam, tidied the data and built a follow-up flow. One question is left: where did this enquiry come from?
Without an answer, content decisions stay instinctive. If you cannot separate the articles that only produce reading from the ones that produce enquiries, what to write next month cannot be decided on evidence.
The minimum structure
No elaborate tooling is required. Three pieces make the connection.
UTM tagging applies to traffic arriving from outside. When people label the same campaign differently, it splits into several rows and the totals stop adding up, so agree a convention — lower case, hyphens — and share the table before anyone tags anything.
The referring page is the internal half. Carrying the article a visitor came from into a hidden field on the form ties one enquiry to one piece of writing. A single URL is enough — the minimum-collection principle from the previous part applies here as well.
Finally, store that value with the enquiry itself. Left only in a separate analytics tool it requires a reconciliation exercise later; sitting on the same row as the lead, it is readable the moment you open the list.
Last-click reporting always undervalues content
There is a common trap here. Record only the final path taken and someone who arrived through search, read an article, and returned days later by typing your company name is filed as a direct visit. The article brought them; the last click takes the credit.
Perfect tracking is impossible, and it is not the goal. One question on the form is surprisingly strong instead: “how did you hear about us?” surfaces the routes no tool can see — a recommendation, an offline conversation, a mention in a community. Put the measured data and the customer’s own answer side by side and the judgement gets considerably firmer.
Where evidence turns into a decision
With the connection in place, three things become possible. You can separate articles that produced enquiries from articles that were merely read and choose the next topic accordingly. You can apply the shape of the ones that converted — length, structure, the offer in the closing paragraph — to others. And you can update rather than discard the pieces that keep working.
Only one discipline is needed: write the next action beside the number. A source table on its own generates meetings; a source table with “update this article, write one more on this topic” beside it leaves a decision behind.
Next part
The series ends here, having tied the structure that produces enquiries to the operations that keep you from losing them.
Two directions follow naturally. Designing the metrics that turn this connection into a report is the subject of the No measurement, no improvement series, and how speed affects conversion before an enquiry is ever written is covered in Speed and conversion. As for the site itself — speed, security and SEO handled as one job — that is our optimization program, and the order we work in is published on the process page.