Live SM Systems implementation

Conversion measurement and inbound lead system

A verified path from website enquiry to CRM, the main Airtable base, human qualification, deal creation, analytics QA, and reporting.

Discuss your tracking path

Implementation walkthrough

One traceable path from enquiry to qualified deal.

The visuals combine the live public form, privacy-safe provider views, the event plan, deterministic QA reports, active routing, and the measurement ledger in the main Airtable base.

Live SM Systems HubSpot enquiry form beside the website, contact, main Airtable and qualification path. — Live enquiry flow from smsystems.au to HubSpot and the main Airtable base, with deal creation held behind human qualification.

Seven-event conversion plan beside cropped native GTM workspace and published version evidence. — Versioned GTM and GA4 event design with a stable submission ID and no personal data in analytics.

Failing duplicate-event QA report beside the repaired exactly-once passing report. — Deterministic QA catches a duplicated generate_lead event before the repaired path passes exactly once.

Native active Make scenario with valid, duplicate, malformed, review and qualification routes. — Active Make routing handles confirmed, duplicate, malformed and review-required outcomes without prospect communication.

Native Measurement QA Runs table in the main SM Systems Pipeline Airtable base. — Website, delivery, review and qualification checks retained in the existing main Airtable operating base.

Project overview

Measurement and lead operations share one stable key.

MEASUREMENT PATHSeven non-PII events

Page views, case-study views, important CTA clicks, form start, and confirmed generate_lead are routed through versioned GTM tags.

LEAD OPERATIONSOne deduplicated route

A confirmed enquiry becomes one HubSpot contact and one matching inbound record in the main Airtable base.

QA CONTROLDuplicate caught and repaired

The Playwright harness caught two generate_lead events, then passed the repaired exactly-once path with zero PII findings.

Confirmed success

generate_lead fires only after form success.

The website emits a stable submission ID after the HubSpot success callback. The event route excludes names, email addresses, message contents, and other personal fields.

Qualification control

Unreviewed enquiries do not become deals.

Make writes the inbound record to the existing main Airtable base. A separate active scenario creates or associates a HubSpot deal only after the qualification state is approved.

Honest reporting

Realtime proves the event, not business outcomes.

GA4 Realtime recorded one commissioning generate_lead. Looker Studio is connected, while tiny test volume remains separate from future real traffic and does not support a conversion-rate claim.

Similar systems

Make every conversion path observable before you trust it.

SM Systems implements tracking, CRM handoffs, qualification gates, lead ledgers, workflow automation, and deterministic event QA.

Discuss your tracking path