Daily DevOps Lead Tracking Workbook

Use this workbook to connect traffic source, consultation intent, and follow-up outcomes so the site is measurable from first click to finished lead.

Workbook Purpose

The live site already captures UTM parameters, referrers, landing pages, and CTA clicks. This workbook turns those signals into a simple operating record for follow-up and reporting.

Suggested Columns

Column	Purpose
`lead_id`	Stable internal identifier for the inquiry.
`submitted_at`	Timestamp of the submission or booking.
`source`	UTM source or channel.
`medium`	UTM medium.
`campaign`	UTM campaign name.
`content`	UTM content / CTA variant.
`term`	UTM term or search term.
`first_landing_page`	First page seen in the session.
`landing_page`	Page where the conversion happened.
`referrer`	Referring page or domain.
`cta_id`	Stable CTA identifier when applicable.
`form_id`	Contact form identifier when applicable.
`lead_name`	Contact name for follow-up.
`lead_email`	Contact email for follow-up.
`company`	Organization name.
`request_summary`	Short description of the request.
`owner`	Person responsible for the follow-up.
`status`	New, contacted, qualified, won, lost, or nurturing.
`next_step`	Immediate action for the lead.
`outcome`	Final result after follow-up.
`notes`	Internal notes and handoff details.

CSV Template

The repo includes a starter CSV at docs/templates/lead-tracking-template.csv.

Operating Rules

Keep the workbook small and current.
Record the source metadata at the time the lead arrives.
Do not rely on memory for the follow-up stage.
Review stalled leads weekly.
Use the workbook alongside the GA4 events and lead-tracking data flow docs.

Next Step

If you want the full conversion path, start with the consulting page and then use the workbook to track the lead from source to outcome.

Jon Price