Answers before your next client report.

Reports join each lead’s original source and campaign to its currently recorded result. Open a campaign to inspect matching leads within identical submission dates and scope.

UTC lead-submission dates. Later outcomes stay attached to the original submission cohort; the report is not a list of every job won that month.

No. Recorded contracts do not confirm payment, profit or return on ad spend. Missing amounts stay missing and currencies remain separate.

Missing source or campaign stays unknown. Attrival does not infer missing attribution or spread credit across multiple touches.

It may not have been recorded or matched. Check identifiers, mappings and health; absence alone does not establish a loss.

Authorized users can exclude a lead with a reason. Exclusion is reversible and audited; it does not delete the lead.

Yes. Choose goals per client. Layouts and saved configuration do not change records, permissions or data-source coverage.

Report and scoped lead CSV are available to authorized roles. PDF, schedules and previous-period comparisons remain deferred.

A workspace, recorded leads with attribution and a configured CRM or manual path. Check lead receipt and the matching outcome separately. Team and libraries can follow.

No. Configure intake and delivery separately, carrying the Attrival Lead ID into the destination. Account authorization does not create CRM records.

No. Authorization, intake, delivery and guided imports are separate. Import approved records only into their intended agency or workspace.

Yes. Owners and editors can update manually managed leads. CRM-owned outcomes remain protected; notes and follow-ups follow workspace roles.

Client roles grant authorized workspace access. Agency roles are separate; signing in or selecting a workspace does not grant membership.

Private reports require login and verified access. Invite the intended reader. Public previews use illustrative data and expose no customer report.

Viewers can read their authorized workspace. Manual edits require owner/editor permissions. CRM management requires an owner or authorized agency administrator.

The catalog separates implemented adapters, pending access and planned entries. Implemented code still needs activation, client authorization, mappings and verification.

No. A configured webhook or automation can return supported outcomes; it does not make the provider a native connector.

No. Report fetch and last successful CRM sync are separate. Inspect failures and stalled queues before relying on outcomes.

No. Identity sign-in is separate from Docs/Sheets library access. General library authorization remains restricted pending verification and review.

The restricted direct connector reads metadata and source links, not rendered designs. General library signup awaits provider review.

No. Paid checkout and subscriptions are unavailable. Creating a workspace does not activate a paid plan.

No. The proposed basis is active client workspaces. Prices, limits and entitlements are not final; ask about current access before relying on an offer.