Lesson 3 of 7 in Measure What Happened
- 1Define the measurement window before starting
- 2Choose a metric that matches the task
- 3Connect published URLs or provider identifiers where required
- 4Record manual results safely
- 5Read integration-backed results
- 6Separate task-linked metrics from workspace metrics
- 7Interpret met, partial, missed, and inconclusive results
Why this matters
Integration-backed measurement cannot read what it cannot identify. A GA4 pageviews result needs the exact public published page URL (or the UTM campaign/content pair it was published with); a social result needs the exact provider post URL owned by the connected account. Approximate URLs, draft links, and URLs from a different account produce broken bindings. The app will try to measure the wrong page, and you will not know until the window is already gone.
When to use it
After a publishing task is marked done, when the task needs a provider identifier to be measured automatically.
Before you start
- The task is done and the page/post is published and publicly reachable.
- The provider is connected: Workspace → Integrations shows it as Connected with a recent Last sync time. (Social: Instagram, Facebook Page / Meta Business Suite, LinkedIn, X. Analytics: GA4.)
- The task is metric-backed, not completion-proof-only (see Choose a metric that matches the task).
Do this
- 1Open Workspace → Integrations and confirm the relevant provider shows Connected. If it shows disconnected or stale, reconnect or run Sync Now before anything else.
- 2On the Marketing Plan page, open the "Log a task outcome" panel ("Choose a completed task to review or record its result.") and open the done task from its list. The URL field sits on the task card, under the measurement status.
- 3For a published page measured by GA4, paste the exact public URL into "Published page URL", character-for-character. If the card lists utm_campaign and utm_content values, publish the link with exactly those. No draft URLs, no staging links.
- 4For a social post, paste the exact provider post URL owned by the connected account into the published post URL field: LinkedIn activity/share/UGC URLs, X status URLs, Meta post/media permalinks. The URL must belong to the connected account, not a screenshot of someone else's share.
- 5Click "Save URL" and read the result: a confirmation that the exact page or post will be matched during the next sync, or an error. If the app rejects the URL, check three things: exact match, publicly reachable, owned by the connected account. Fix and re-save.
- 6Confirm the task now shows "Task completed. Measurement pending." The binding is armed; measurement starts from the moment you saved the URL.
What you should see
A saved binding with no validation error, and the task in its automatic-measurement state ("Task completed. Measurement pending."). If validation fails, you see an error. Treat it as real and fix the URL; do not click past it.
How to judge it
The bound identifier is exact, public, and owned by the connected account, and validation passed. Anything less is a measurement waiting to fail.
What it does not mean
A bound URL does not guarantee the provider read will succeed. Read failures are a separate, visible state (see Read integration-backed results). A bound URL means the app knows what to read, not that the read worked.
Try it in Signal & Science
Open Integrations and check the Last sync time on each provider your measured tasks depend on.
Open in Signal & Science