Your client’s account
Each workspace uses its customer’s own authorization or credentials. Provider setup requirements vary.
Your client works in their own account. A configured outcome connection or workflow matches the recorded result back to the original lead, so its campaign stays in the report.
Illustrative example · Sample data
Source: Meta · Spring roofs
Carried by the configured delivery workflow
Returned against that lead’s identifier
Example identifiers are illustrative. Actual matching uses the lead ID returned by Attrival.
The workflow that delivers the lead to the client’s CRM must also carry the Attrival Lead ID. That identifier lets a later outcome update refer to the same lead.
Each workspace uses its customer’s own authorization or credentials. Provider setup requirements vary.
Store the returned Attrival Lead ID in the configured CRM field. Outcomes are not matched by guessing from a name or email.
Map stages and amount fields deliberately, confirm currency and enable the configured sync path. An open stage is not automatically a win.
Receipt of a lead and receipt of its matching outcome are separate checks. Use a deliberately supplied test lead in an authorized client or sandbox account.
Check the destination workspace, original source, campaign and contact fields.
Change the same test record in the authorized CRM and inspect its recorded result and value in Attrival.
Check actual sync or event timestamps and actionable failure or stalled-sync notices. External email/Slack alert delivery is not configured.
Authorized users can update manually managed leads with outcomes, values, notes and follow-ups. CRM-managed outcomes remain controlled by that CRM.
A stable Attrival Lead ID must be present in the configured workflow. Check the ID, mapping and connection health; do not count an unmatched update as a confirmed client outcome.
Creating a workspace does not start a paid subscription.