Loading
Because they are separate tools with different identifiers and different definitions of a visit. Joining them is a quarterly spreadsheet exercise that nobody enjoys or fully trusts.
GA4 session and behaviour data attaches to the same page record that holds the search data.
Sessions, engagement and conversions land per URL. Because the URL is a record rather than a string, its search performance and its outcomes sit together without a join step.
An organic session becomes an enquiry, which becomes a lead in Flow carrying the landing page. If that lead is won and invoiced in Books, the page shows the value.
It will not resolve individuals. Growth reads aggregate behaviour, not people, and does not attempt to identify visitors from analytics data.
Search Console and Bing on one side, Flow and Books on the other, with the page record as the join.
Sessions, engagement, conversions and revenue where configured.
Only for the enquiry hand-off, so the lead carries its landing page.
Yes, where it can supply per-URL sessions and conversions.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.