Lead and Tracking Workflow

How leads and tracking signals flow — capture, attribution, integration handoff.

The Lead and Tracking Workflow is the cross-product process that captures lead-generation signals (form submissions, link clicks, conversion-relevant events), attributes them, lands them in the admin records, surfaces them in analytics, and (where wired) pushes them to connected integrations. This page is the Reference definition.

What is this for?

Read this page when you want the structural definition of lead and tracking flow — what gets captured, how attribution attaches, where the data lands, and how it pairs with analytics.

Good use cases

• You are scoping a marketing operation and need the lead-flow model.
• You are explaining to a stakeholder how SGEN attributes captured signals.
• You hit a "where do leads end up?" question and want the model laid out.

What NOT to use this for

• Step-by-step capture-config procedures — open the relevant Guide.
• Per-release shipped change — open What's New or Changelog.
• Custom attribution model design — out of scope.

How this connects to other features

• Workflows Overview — parent Reference area.
• Form Submission Workflow — primary capture entry path.
• Analytics and Reporting Workflow — sibling that surfaces tracking signals as analytics.
• Google Analytics 4 — analytics ingest layer.
• SG-Admin Overview — where lead records land.

Definition

The Lead and Tracking Workflow is the cross-product process for capturing, attributing, and routing lead and tracking signals. It overlaps with the Form Submission Workflow (forms are the primary capture path) but extends to other tracking events the platform surfaces.

The defining property is attribution. Every captured signal carries the source context — which page, which campaign, which session — so downstream analytics and integration handoffs can use the attribution.

Purpose

The purpose of this page is to define the lead and tracking flow as a Reference layer. It explains capture sources, attribution model, and where the data flows downstream.

Scope

This page covers the workflow at the Reference level.

The page covers:

• The capture sources (forms, conversion events, click-tracked links).
• The attribution model.
• The downstream paths (SG-Admin records, analytics surfacing, integration push).
• The boundary against custom attribution work.

• Step-by-step capture configuration — Guides.
• Custom attribution model design — out of scope.
• Per-release shipped change — What's New or Changelog.

Capture sources

Forms

Form submissions are the primary lead capture source. The Form Submission Workflow handles the multi-handoff flow; this Lead and Tracking Workflow consumes the captured submissions as leads.

Conversion events

Configured conversion events fire when visitors complete defined goals (newsletter signup, store checkout, demo request).

Click-tracked links

Where the platform supports it, links on the public site can be tagged for click tracking. The clicks fire as tracking events.

Attribution model

Each captured signal carries source context.

Source page

The page the visitor was on when the capture event fired.

Referrer

The referrer the visitor arrived from (organic search, paid campaign, direct, social).

Session

The visitor's session identifier so multi-event sessions can be reconstructed.

Campaign tags

Where applicable, UTM-style campaign tags propagated through the visitor's session.

Downstream paths

SG-Admin record landing

Captured signals land as records in the admin (My Forms for form submissions, conversion records for conversion events).

Analytics surfacing

Analytics integrations (GA4 and others) consume tracking signals. Aggregated views surface in SG-Dashboard Analytics; raw events surface in Event Logs.

Integration push

Where wired, captured signals flow out to connected services (CRM, email-marketing).

Constraints and boundaries

This Reference covers the cross-product lead-and-tracking flow.

Use this Reference for:

• Understanding capture sources and the attribution model.
• Routing lead-related questions to the correct downstream surface.

• Step-by-step capture configuration — Guides.
• Custom attribution model design — out of scope.
• Per-release shipped change — What's New or Changelog.

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Form submission generates a lead with full attribution

A visitor finds the site via organic search, lands on /pricing, fills out the contact form. The submission lands in the admin My Forms with full attribution (source page, referrer, session, campaign tag). The CRM push includes the same attribution.

Example 2 — Stakeholder asks "where did our leads come from this month?"

The operator opens SG-Dashboard Analytics, scopes to last 28 days, reviews the conversion summary by referrer and campaign. The Reference grounds the question in the platform's attribution model.

Example 3 — Lead loses attribution

A submission lands without expected attribution (referrer = "unknown"). The operator walks the Reference, identifies the likely cause (no UTM tagging on the inbound link, session reset, or another known case), and adjusts.

Documentation guidance

Use this page as the structural definition for the lead-and-tracking flow. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.

Reading order

Open this page when scoping marketing operations or troubleshooting attribution-related questions.

Related reading

• Workflows Overview — parent Reference area.
• Form Submission Workflow — primary capture entry.
• Analytics and Reporting Workflow — analytics surfacing.
• Google Analytics 4 — analytics ingest.
• SG-Admin Overview — record landing.
• Content Update Workflow — sibling for update cycle.
• Publishing Workflow — sibling for publish mechanics.

Vocabulary cross-reference

• Lead is a captured signal with operator-actionable contact context.
• Tracking signal is a captured event without operator-actionable contact context.
• Attribution is the source context attached to a captured signal.
• Capture source is the surface that produced the signal (form, conversion event, click).
• Downstream path is one of: SG-Admin record landing, analytics surfacing, integration push.

Maintenance discipline

When the lead-and-tracking flow changes across releases (new capture source, new attribution field, new downstream path), update this Reference and log the change in Changelog.

Related reading