How the attribution contract is assembled
Seven identity and provenance fields form the base contract. Each selected channel adds only the fields and observable events it needs. Each selected lifecycle stage adds an entry event. The output uses stable names so a touch can retain its campaign, play, creative version, source and UTC timestamp after the contact or opportunity changes state.
Facts first, interpretation second
A raw event says what happened and when. “Sourced” and “influenced” are reporting interpretations. Store the event history first, then document the windows and qualification rules used by each report. That keeps a dashboard change from rewriting operational history.
Use the Campaign Launch Preflight to make sure the identifiers reach the live campaign. Read the operating model in Outbound attribution: how to build the data model.
Make the model operational
Trace the handoffs across your GTM stack.
We map the market, systems and CRM outcomes, then show where identity or ownership breaks.
Book your GTM Engine Review