Measuring Which Blog Posts Actually Drive Enquiries
Why page views alone tell you nothing about enquiries
A blog post can collect thousands of views and still generate zero business. Traffic is a vanity signal until you can connect a specific article to a specific action, such as a contact form submission or a consultation request. Without that connection, you are guessing which content deserves more investment.
On design-logix.co.uk, the goal is to measure which posts actually move readers toward an enquiry. That means setting up tracking that links article reads to conversions, not just counting visits. The approach below is practical and can be implemented without a large analytics team.
Start with a clear conversion definition
Before touching any tag manager, decide what counts as an enquiry. A contact form submission is the obvious one, but a consultation request may arrive through a booking link, a phone call, or a short qualification form. Write these down as named events so every tool uses the same language.
If you cannot name the conversion, you cannot measure which post caused it.
Keep the list short. Two or three conversion events are enough to start: form submission, consultation booking, and perhaps a callback request. Anything more creates noise and makes reporting harder to interpret.
Attach article context to every conversion
The simplest reliable method is to pass the source article into your forms. When a reader lands on a post, store the page path and title in a cookie or session storage. When they submit a form, add that value as a hidden field. Your CRM or inbox then shows exactly which article preceded the enquiry.
- Add a small script that records the current article path and title on page load.
- Insert hidden fields in every form to capture those values.
- Confirm the values arrive correctly in a test submission.
- Review the data weekly and label each enquiry by source article.
This method survives ad blockers and cookie restrictions better than many third-party pixels, because it relies on your own form data rather than cross-site tracking.
Use GA4 events and a simple attribution report
Alongside the hidden fields, configure GA4 to fire a generate_lead event on form submission and a book_consultation event on booking confirmation. Mark both as key events. Then build an exploration report that shows the landing page and the event side by side.
The report does not need to be perfect. Even a directional view of which articles appear most often before an enquiry will change how you plan content. Pair it with the hidden-field data to validate the numbers.
| Article | Reads | Enquiries | Rate |
|---|---|---|---|
| Service pricing guide | 1,240 | 18 | 1.45% |
| Design process explainer | 860 | 6 | 0.70% |
| Case study roundup | 410 | 9 | 2.20% |
Review, refine, and feed the findings back
Set a monthly review. Look for posts with high read counts and low enquiry rates, then test stronger calls to action or a clearer next step. Look for low-traffic posts with strong conversion rates and consider promoting them.
- Tag every conversion with the source article.
- Compare enquiry rate, not just traffic.
- Update weak calls to action on high-traffic posts.
- Promote quiet posts that convert well.
Done consistently, this tracking turns your blog from a publishing habit into a measurable channel. You will know which articles actually drive enquiries, and you can defend every hour spent writing them.
