Data & Attribution
The three screens Revenue Analysts and RevOps admins use to trust the numbers behind the pipeline: where revenue-attributed marketing spend really came from, how clean the CRM's account and contact records are, and whether the CRM is still telling the same story as ERP, Billing and the other connected systems.
What this group does
Pipeline & Funnel Operations tracks deals as they move; Data & Attribution looks sideways and backward at the data quality those deals depend on. All three screens answer a version of the same question — "can I trust this number?" — for a different layer of the stack: marketing credit, CRM record hygiene, and cross-system consistency.
All three screens share the same pattern as the rest of RevOps: a working ledger of records, an AI diagnostic that searches the ledger for similar cases before reasoning about the current one, and a quick action that pushes the finding back out — a budget reallocation, a bulk merge, or an auto-reconciliation.
1. Multi-Touch Attribution
Purpose: Calculate how much revenue credit each marketing and sales touchpoint in a customer's buying journey — a content download, a webinar, an email open, a demo call — deserves for a closed-won deal, using W-Shaped, Full-Path, Linear or AI-modeled attribution, and recommend where to shift marketing budget for the best return.
Key features
- Attributed Revenue ROI Efficiency gauge — a live percentage of closed-won revenue whose channel credit distribution fully adds up to 100%, i.e. is accurately mapped to real touchpoints.
- Attribution journey ledger — Journey ID, account name, closed-won deal value, the selected attribution model (W-Shaped / Full-Path / AI Machine Learning), the primary origin touchpoint (Paid Search / Organic Content), the key nurture touchpoint (Webinar / Outbound Call), the closing touchpoint (Executive Demo), the resulting channel credit split, and an AI optimization score.
- Reallocate Campaign Budget — a one-click action on any journey that calculates a budget shift from its lowest- to highest-credited channel and confirms it with an on-screen message.
- AI Attribution Model & Budget Optimization Diagnostic — enter an account, its attribution model, origin and closing touchpoints, and deal value; the assistant first searches the existing journey ledger for similar cases (semantic search, with a keyword fallback if no local model is available), lets you pick which matches to include, then reasons over the selected cases to return a risk level, which channel is over- or under-credited, and a recommended budget shift.
2. Data Hygiene Engine
Purpose: Scan the CRM and revenue database for duplicate company and contact records, missing contact data, invalid emails and broken account hierarchies, and clean them up before they cause bad reporting or reaching out to the wrong person.
Key features
- Revenue Database Health gauge — a live average data-quality health index across every scan on file.
- Data hygiene scan log — Scan ID, the target entity type (Account / Contact / Lead / Opportunity), the duplicate or error flag found (Fuzzy Match Candidate / Invalid Email Domain / Missing Parent Account / Standardized), the matching pair it flagged, a match confidence percentage, a data-quality health index, its resolution status (Pending Merge / Cleaned / Ignored), and the AI's recommended resolution plan.
- Execute Bulk Cleanse & Merge — a one-click action on any pending scan that runs the merge, marks the record Cleaned, and confirms it with an on-screen message; once cleaned, the action is disabled on that record.
- AI Deduplication & Normalization Diagnostic — enter the entity type, the flag, and the matching pair reference; the assistant searches the scan log for similar cases (semantic search with a keyword fallback), lets you select which ones to include, then returns a risk level, a field-by-field comparison note (e.g. a likely name variation such as "Acme Corp" vs. "Acme Inc."), a recommended merge confidence, and a suggested resolution plan.
3. Cross-System Sync
Purpose: Monitor the health of the two-way data integrations between the CRM and the systems it depends on — ERP, Billing, and marketing automation — and catch field mapping mismatches, sync conflicts and failed API or webhook calls before they cause the CRM and the connected system to disagree.
Key features
- Inter-System Sync Health gauge — a live percentage of logged sync transactions currently in a fully synced state.
- Sync health log — Sync Log ID, the connected system pair (CRM ↔ ERP / Billing ↔ CRM / MAP ↔ CRM), the object type being synced (Invoice / Contract / Account / Subscription), its payload status (Synced / Field Mismatch / API Rate Limited / Sync Blocked), the last sync timestamp, an error code, and the AI's healing action verdict.
- Trigger Auto-Reconciliation — a one-click action on any mismatched or blocked sync that runs the reconciliation, marks the record Synced, updates its last-sync timestamp, and confirms it with an on-screen message; once synced, the action is disabled on that record.
- AI Field Discrepancy & Reconciliation Diagnostic — enter the connected systems, object type, payload status and error code; the assistant searches the sync log for similar failures (semantic search with a keyword fallback), lets you choose which to include, then returns a risk level, the field most likely causing the discrepancy, a root-cause analysis, and a self-healing script description.
How the AI diagnostics work
Each screen's diagnostic runs in two stages so the AI's reasoning is always grounded in your organization's own data, never invented from scratch:
| Stage | What happens |
|---|---|
| 1 — Search | The screen searches its own ledger for records similar to the one you're investigating, ranks them by relevance, and lets you pick which ones matter before continuing. If no local search model is available, it falls back to a keyword match automatically. |
| 2 — Diagnose | The selected records are handed to the AI assistant along with the record you're investigating. It returns a risk level, a plain-language explanation of what's likely happening, and concrete next steps — scoped only to the records you selected. |
A note on the quick actions
Reallocate Campaign Budget, Execute Bulk Cleanse & Merge, and Trigger Auto-Reconciliation are not identical under the hood. Reallocate Campaign Budget always shows a confirmation message but does not change the journey's own record — it is a calculation and a hand-off point, since TotalApp does not yet have a live connection to your marketing platforms to push the budget change itself. Execute Bulk Cleanse & Merge and Trigger Auto-Reconciliation genuinely update the record they act on (status moves to Cleaned or Synced) and the action then disables itself on that record — but they likewise don't yet write back to a live CRM or webhook queue outside TotalApp. In every case, the on-screen confirmation tells you exactly what happened.
Who can do what
| Step | Required capability | Typical role |
|---|---|---|
| View any Data & Attribution screen | revops domain role | Revenue Analyst, Sales Ops Specialist, RevOps Admin |
| Create or edit a journey / scan / sync record | revops:analytics:read | Revenue Analyst, RevOps Admin |
| Run an AI diagnostic | revops:analytics:read | Revenue Analyst, RevOps Admin |
| Reallocate budget, merge records, or trigger reconciliation | revops:analytics:read | RevOps Admin |