Separate task-linked metrics from workspace metrics

This lesson prevents the most costly mistake in measurement: claiming the business moved because your task worked. Task-linked metrics (exact pageviews on the page you published, engagement on the exact post you shipped) are tied to the work. Workspace metrics (GA4 sessions, GBP call clicks, follower movement, revenue/orders, review movement) were observed during the window, and must be explicitly not claimed as task-caused. Mixing the two turns a clean win into an indefensible story.

Every time you read results (Analytics, the "Recorded task results" section, or a plan review) after at least one measurement window has closed.

• At least one closed measurement window with task-linked results.
• Workspace metrics visible for the same period (Analytics, or the providers directly).

1. 1List the task-linked metrics first: exact pageviews on the bound page URL, post metrics on the bound post URL. They are tied to the exact identifier the task produced; the task card says "Matched to this task's exact published page or post."
2. 2List the workspace metrics for the same window: GA4 sessions, GBP call clicks, follower movement, revenue/orders, review movement. Note them as observed during the window.
3. 3Draw the line explicitly, in words: "The post earned X engagements (task-linked). During the same window, site sessions were Y and revenue was Z (workspace-wide, not claimed as task-caused)."
4. 4Watch for the tempting correlation: a task ships, revenue rises the same week. That is "coincided with", never "driven by", unless the evidence genuinely supports a causal claim (it almost never does from one window).
5. 5Keep distribution and impact in separate columns. Reach, views, and impressions are distribution evidence: seen, not sold. Leads and revenue are business impact, and business impact belongs to the workspace unless a task-linked trail connects them.

On the task card: a task-linked result reads "Matched to this task's exact published page or post.", and a workspace metric reads "Workspace metric observed during this task's measurement window; this does not claim the task caused the change." Analytics does not label numbers this way, so do the sorting yourself there. Both present, neither claiming the other's role.