The requirement
For a service business, clicking Submit is only the beginning. The goal is to connect campaign context to a successfully saved inquiry, then distinguish that inquiry from a qualified opportunity and a won project. This proof of concept explores how to make each step visible and testable without treating every interaction as a conversion.
What we are building toward
- Build a commercial HVAC journey from service discovery to a three-step assessment request.
- Preserve useful campaign context and create one canonical assessment_accepted event only after a request is saved.
- Make retries recover the original receipt without creating another lead, and keep validation or storage failures out of conversion counts.
- Map accepted inquiries to GA4 generate_lead, a Google Ads inquiry action, Floodlight and Meta Lead, with qualification and won milestones kept separate.
- Make consent choices, event mappings and destination evidence inspectable, then package the findings into a clear handoff.
Where the project is today
The public preview introduces Fieldwork Mechanical through its homepage, service pages and assessment journey. An implementation walkthrough explains the proposed event model, destination mappings and failure scenarios.
The linked deployment is a static portfolio preview. Forms, sessions and tracking are disabled there, so visitors can explore the design without creating a lead or sending advertising events.
The walkthrough describes a WordPress block theme and project-owned plugin, with transactional storage, signed sessions, retry protection and a qualification lab. These are the architecture being developed for the interactive POC; the static preview is not evidence that those behaviors have been verified end to end.
Verification plan and current status
| Scenario | Expected behavior | Observed result |
|---|---|---|
| Public preview | Visitors can inspect the design and implementation approach. | Homepage and implementation walkthrough are available. The preview explicitly identifies its disabled forms, sessions and tracking. |
| Acceptance and retries | A saved request creates one lead; retrying returns the same receipt. | Planned acceptance criterion. Interactive runtime verification remains part of completing the POC. |
| Consent and failure handling | Declining optional tracking keeps the inquiry journey usable. Failed storage creates no conversion. | Documented in the walkthrough; not verified through this static deployment. |
| Destination receipt | Authorized test accounts show the intended events and parameters. | GA4, Google Ads, Floodlight, Meta and CRM receipt remain unverified. Local mappings are not proof of platform delivery. |
What comes next
The next milestone is a complete synthetic journey through the interactive runtime: validation, durable acceptance, retry recovery, consent changes and lead qualification. Destination checks then need to show what actually arrived in each authorized test account, separately from what the application generated.
Limitations
Draft case study for an in-progress proof of concept, not a completed client engagement. Fieldwork Mechanical is fictional. No campaign performance, revenue lift or verified advertising outcomes are claimed. This write-up will be updated with test evidence and confirmed functionality once the POC is complete.