Save a measurement baseline and track qualified outcomes

Analytics answers two different questions in PageOptimized, and keeping them separate is the point:

1. Baselines save what the project knew during one dated period.
2. Business outcomes record what a source system later confirmed after a GA4 event.

A GA4 event can be a useful lead or purchase signal. It is not automatically a qualified lead, signed case, won order, paid invoice, or confirmed revenue.

Save a measurement baseline

1. Open the project.
2. Go to Analytics > Baselines.
3. Click Capture baseline.
4. Name the baseline for the strategic moment, such as Pre-migration baseline.
5. Enter the owner and scope.
6. Choose the period end and a 28-, 90-, or 365-day window.
7. Write assumptions one per line. Assigned GA4 event value is a common assumption.
8. Write unknowns one per line. Missing CRM qualification or paid status belongs here.
9. Click Save immutable snapshot.

The snapshot saves completed Work Queue items, visibility signals, GA4 audience outcome signals, assumptions, unknowns, and the source link and exact period behind every metric. A missing source is saved as unavailable, not zero.

Saving and reopening a baseline uses stored project data and costs 0 credits. It does not run a crawl, rank check, link lookup, Analytics sync, or Search Console sync.

Reopen, compare, and share

Choose any item in Baseline history to reopen it. The snapshot does not refresh when opened, so the numbers remain the evidence that was available on that date.

Use Compare with to place the saved metric values beside another baseline. Compare only when the scope still means the same thing. A migration, market change, tracking change, or different keyword cohort can break comparability even when both snapshots are valid.

Click Share to create a public read-only link and copy it. Creating another share link rotates the previous token. The public view can read only the stored snapshot; it cannot start work or spend credits.

Set up project outcome stages

Open Analytics > Business outcomes. PageOptimized creates Lead, Qualified, Won, Paid, and Lost as separate default stages. Add the business's own stage name and map it to the meaning it carries. For example, Signed case may map to Won.

This outcome ledger belongs to the client project. It does not use PageOptimized's internal sales CRM.

Add an outcome source

Name the system that owns the downstream status. You can label a manual or generic CSV source, or identify a HubSpot, Salesforce, or Pipedrive export. These labels document export provenance; they do not claim a live OAuth sync.

Adding a source or reopening imported evidence costs 0 credits.

Import downstream outcomes

Export the relevant rows from the source system as CSV, then use Import to beside that source. Required columns are:

• external_id
• label
• stage
• occurred_at

Optional columns are:

• value
• currency
• landing_page
• work_item_id
• attribution_model: reported, first_touch, last_touch, manual, or unknown
• confidence: confirmed, inferred, or unknown
• evidence_url
• attribution_limit

Use an ISO date or date-time for occurred_at. Stage must match one of the project's saved stage names. Re-importing the same source and external_id updates the outcome and appends a stage-history row instead of creating a duplicate.

Read the outcome ledger correctly

The top summary deliberately says GA4 events are separate. Lead, Qualified, Won, Paid, and Confirmed paid value come only from imported project outcome records.

Each ledger row keeps:

1. The named source system and external ID.
2. The current project stage and retained stage-change count.
3. The dated value and currency.
4. The landing page, when the source carried one.
5. The linked PageOptimized Work Queue item, when supplied.
6. The attribution model and confidence.
7. The source evidence URL and attribution limitation.

Landing-page or work-item proximity does not prove SEO caused the result. Write the narrowest supported limitation, such as "CRM first-touch landing page; offline referrals may be missing." The limitation is shown beside the result rather than buried in report notes.

What this feature does not do

• It does not turn assigned GA4 event value into confirmed revenue.
• It does not infer qualified, won, or paid status from a form submission.
• It does not claim that linked PageOptimized work caused an outcome.
• HubSpot, Salesforce, and Pipedrive are currently dated export sources, not live bidirectional syncs.
• A baseline comparison shows movement; it does not establish causation.

Use Work Queue for the next owned action. Use the baseline share link when a reviewer needs the evidence as it existed, and use the project outcome ledger when the conversation reaches qualification, won work, or paid value.