Loading
Because the answer spans systems. Traffic is in analytics, leads are in the CRM, revenue is in accounting, and joining them is a request to somebody with a query tool and a backlog.
By the time the answer arrives the decision it was for has been made on instinct.
Source tracking carries the campaign from first click through to closed revenue, and Pulse reads across those records to answer in the shape the question was asked — by campaign, by channel, by month — citing what it used.
Because it cites, the answer is checkable, which is the difference between a number you can act on and one you have to trust.
It will not run campaigns or spend budget, and it will not tell you why something worked. It reports what happened, with sources.
And it cannot see spend you have not given it. Cost per acquisition needs both halves, and Treepie only holds one of them by default.
The gap between wondering and knowing closes, so a channel that produces volume and no revenue is caught in weeks rather than at annual review.
Drafts for follow-up, briefs and summaries come from real records rather than from a blank page, and Growth supplies the search side of the same picture.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, through source tracking carried to closed revenue in Books.
Yes, every answer names the records it read.
Only if you supply it. Treepie holds the revenue side by default.
Half an hour on your own numbers is usually enough to say whether Pulse is the right place to start.