Map CallSource requirements
Share the CallSource source, fields, and reporting questions your team needs to answer.
What you can do with CallSource in Maven
Start with the calls, sources, tracking lines, dispositions, and lead-quality signals your team uses to judge demand. Maven will confirm access and field mappings before adding those outcomes to governed attribution.
How it works
Plan CallSource reporting before implementation
Confirm the source access, fields, governed definitions, validation criteria, and rollout scope before treating the connector as production-ready.
Define governed metric coverage
Maven documents how the approved CallSource fields would map into governed metrics before implementation begins.
Approve the implementation path
Confirm access, scope, validation criteria, and rollout timing before the connector is enabled for production reporting.
What Maven syncs from CallSource
Call tracking events
Works well with
Report CallSource alongside the rest of your stack
FAQ
CallSource reporting questions
What CallSource metrics can I report on in Maven?
Maven exposes 20 governed CallSource metrics, including Touchpoints, First-Touch Events, Last-Touch Events, Avg Session Duration (s), Interactions and Answered Interactions, each defined once so it means the same thing in every report.
What can I break CallSource performance down by?
You can break CallSource metrics down by Event Type, Event, Touchpoint Source, Channel, Source, Medium, Campaign and Utm Content, and more.
Can I combine CallSource with other data sources?
Yes. CallSource reports alongside sources like Google Analytics 4, Google Ads, Shopify and HubSpot. Maven models every source into one governed layer, so you can blend them in a single dashboard, report, or question.
What should we define before adding CallSource to Maven?
Start with the business questions, source fields, reporting grain, refresh cadence, and account access your team needs. Maven will confirm the implementation path and supported coverage before production use.
Is the CallSource integration available today?
Availability depends on the source and workspace requirements. Maven can review the CallSource reporting fields you need and confirm the current implementation path before you commit to a rollout.
How will Maven protect CallSource data?
Any production implementation must use scoped credentials, encrypted secret storage, workspace-level access controls, and only the reporting data approved during implementation review.
Ready to make client reporting easier to run and defend?
Bring one client report or disputed metric. We'll map the workflow and where Maven fits.
One report, reviewed end to end
Clear roles across data, QA, and delivery
No pitch deck. No pressure. 20 minutes.
