Operational article · published

Capture Acquisition Source at Intake

Preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff. Use this evidence-led revenue measurement guide to build a reviewable.

Reviewed 2026-07-30 · National guidance, Austin proof
01

The task and the failure mode

Built for: Marketing, sales, intake, and operations teams connecting acquisition context to qualification, pipeline, completed work, and revenue. This guide is for the person who must preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff. and leave a decision trail that implementation, editorial, analytics, or operations can review.

Capture Acquisition Source at Intake becomes risky when several states are reported as one. The design should retain raw fields and a normalized interpretation rather than replacing evidence with one label. A team may then repair the wrong layer, lose the earlier configuration, or publish a conclusion that another reviewer cannot reproduce. The safer approach is to define preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff., then make the source capture specification carry the supporting and contradictory evidence.

Frame

Decision brief

Write the narrowest route, cohort, workflow stage, or configuration that still represents Capture Acquisition Source at Intake. List adjacent states separately so scope does not expand by implication.

Define the control case that should remain unchanged during Capture Acquisition Source at Intake. A passing target with a broken control is not a successful release.

Attach the review date to the evidence, not merely the page. Volatile platform behavior and business facts need their own freshness owner.

Ask

Questions to answer before changing the system

  1. 01What evidence would prove that The design should retain raw fields and a normalized interpretation rather than replacing evidence with one label. is the wrong explanation?
  2. 02What does the source capture specification need to show for another reviewer to reproduce the result?
  3. 03Which observation should trigger containment or rollback?
  4. 04What counterevidence should be placed beside the recommended action?
  5. 05What is the smallest representative surface for preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff.?
02

Workflow

  1. 01State preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff. as a falsifiable working question, then list the people and systems that could be affected by the answer.
  2. 02Collect one direct observation for the suspected mechanism and one observation from an unaffected control.
  3. 03Build a small sample that could disprove the current explanation instead of selecting only examples that support it.
  4. 04Code the sample as supporting, contradicting, unavailable, or irrelevant to preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff..
  5. 05Prioritize the response that survives the counterevidence and requires the fewest unsupported assumptions.
  6. 06Have a reviewer reproduce the observation from the documented starting state and primary sources.
  7. 07Write the decision, rejected alternatives, counterevidence, and condition that would reopen Capture Acquisition Source at Intake.
03

Evidence to retain

  • The source capture specification, headed with “Capture Acquisition Source at Intake,” identifies the decision owner, reviewer, affected surface, explicit exclusions, and observation date.
  • A direct before-state receipt for preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff.. Keep the requested and final state, timestamp, version or report definition, and the source that produced the observation.
  • One cluster-specific proof item: allowed acquisition fields and source precedence rule. Connect it to the case where it was observed and explain why that case represents this decision.
  • One independent cross-check using duplicate and merge behavior documented. If the two observations disagree, preserve both and classify the likely boundary instead of selecting the cleaner result.
  • A representative case set for Capture Acquisition Source at Intake: ordinary, high-value, edge, failure, and unaffected control, each with an expected result written before the test.
  • The primary-source trail behind The design should retain raw fields and a normalized interpretation rather than replacing evidence with one label. Record which part of the wording is directly supported and which part remains a project-specific inference.
  • A disposition for every exception in the source capture specification: fix, monitor, accept with rationale and expiry, escalate for qualified review, or remove from the admitted scope.
Sample

Worked decision: Capture Acquisition Source at Intake

Situation
Several reports disagree because they use different requested and final states.
Question
Preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff.
Evidence
Build the source capture specification; include a representative case, an exception, a control, timestamps, and the cluster-specific observations listed in this guide.
Decision
Apply the smallest change supported by the evidence, assign every exception, and keep the broader crm and revenue attribution surface unchanged until it is tested.
Acceptance
The reviewer can reproduce the observation, inspect the primary sources, verify the changed state, and identify what remains unmeasured.
04

Source capture specification release checklist

  • A high-value case, ordinary case, edge case, known failure, and unaffected control are represented.
  • The selected action is no broader than the mechanism supported by the evidence.
  • Another reviewer can repeat the observation from the source capture specification.
  • Primary documentation and volatile business facts have a next review date.
  • The scope of Capture Acquisition Source at Intake includes one explicit boundary and one explicit exclusion.
  • Unavailable evidence is labeled unavailable rather than converted to zero or a pass.
  • A browser, crawler, vendor, model, analytics, and operational receipt are distinguished where they represent different stages.
  • Every exception has a fix, monitor, accept, escalate, or remove disposition.
  • The closeout for preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff. records the next action and the condition that would reopen the decision.
  • Material claims cite primary sources that support the exact wording used.
Measure

What to measure—and what it does not prove

  • Capture Acquisition Source at Intake primary state: measure source context surviving without silent overwrite. The source capture specification must name the source, calculation, route or cohort, observation window, and freshness.
  • Quality control for preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff.: sample the records behind duplicates, spam, existing customers, and out-of-scope inquiries separated. A clean rate does not establish that individual cases are complete, correctly classified, or free of duplicates.
  • Exception measure: count unresolved, accepted, escalated, repeated, and timed-out cases created by this decision. Pair volume with an owner and response target instead of blending failures into the success denominator.
  • Outcome boundary: review the downstream user or business result after the planned lag, but do not treat completion of source capture specification as proof of ranking, revenue, compliance, safety, or causal impact.
05

Boundaries and caveats

Long sales cycles make recent cohorts incomplete.

Capture Acquisition Source at Intake supports a bounded decision, not a universal rule. Recheck cases whose route, market, device, provider, data sensitivity, or operating model differs from the admitted sample.

The source capture specification can show what was observed and why an action was chosen; it cannot turn unavailable evidence or an external platform outcome into a confirmed result.

Primary documentation and business facts can change. Revalidate the sources and obtain qualified legal, privacy, security, medical, financial, or regulatory review when preserve landing, referrer, campaign, call, and self-reported context at the earliest authorized handoff. could create material harm.

06

Primary sources

  1. Google Analytics Help: Lead acquisition reportsupport.google.com
  2. Google Analytics Help: Collect campaign data with custom URLssupport.google.com
  3. Google for Developers: Google Analytics Measurement Protocoldevelopers.google.com
  4. Google Search Central: Use Search Console and Google Analytics data for SEOdevelopers.google.com
Continue the task

Related working pages

Next

Start with one bounded case

Start with one representative case and open a source capture specification. If the evidence confirms the suspected mechanism, admit the smallest useful batch for implementation. If it does not, keep the finding as an unresolved hypothesis and return to the crm and revenue attribution baseline instead of expanding the change.