Why do I not see a result right after delivery?

Because there is none yet. An honest measurement needs an "after" window comparable to a "before" — 14 days. Until then the session page says exactly when Valhalla reads the data.

What if I do not have GA4 connected?

Valhalla notes that the window closed without connected data, and Florentin writes the result from the platform or from what you observe — marked as such. Connecting Google makes measurement automatic.

How to track impact

The situation

Session 2 fixed conversion tracking. Two weeks later, in History, under "Delivered", it shows: "Key events 14 → 31 (+121%, 14 days)". You want to know what that number means, what it does not mean, and how much to rely on it.

Three words, never mixed

Every result in the Florentin Purcea ecosystem carries one of three words:

Delivered — it shipped and you can verify it: a tag fixed, a page live, a correct feed. In the portal: the session is "Done", deliverables are ticked, you confirmed.
Observed — a number measured after, in your own accounts, with the window stated. In the portal: the result under the delivery, in History and on the session page, "before → after" with the window stated.
Attributed — a causal claim ("conversions grew because of the session"). It is made only with the caveat written next to it and never with invented revenue. If the effect cannot be isolated, the result says "unknown".

The rule is simple: an Observed number does not become Attributed just because it came after a delivery.

The measurement window

Delivery → you confirm → the session enters "measuring result · N days left".
14 days after delivery, Valhalla reads the data. If Google is connected, it compares in GA4 the key events and sessions of the 14 days before with the 14 days after.
Valhalla writes a proposed result in the session log — "GA4 14 days before/after: key events 14 → 31 (+121%), sessions 1,820 → 1,905. Proposed result — to confirm." You get a notification "Measurement ready for session 002".
Florentin closes the result: confirms it, corrects it or writes explicitly that it could not be measured. Only then does it appear as a measured result in History and on the session page.

Without connected data, Valhalla does not invent: it asks for the result from the platform or from what you observe, and it is noted as such.

Where you see impact

Now › This week — what shipped this week, with the first result.
Session page › What we measure, and when — the date Valhalla reads the data, then the number.
History › Month by month — every delivery, with "being measured until …" or the closed result.
History › Your business now — the state of each area (website, ads, Google search, AI assistants, measurement, automations, AI on your site), in words, rechecked daily; when an area cannot be measured it shows "Not connected" or "Not checked yet", not zero.

The monthly recap

At the start of each month, Valhalla builds last month's recap from what actually shipped: sessions, hours, improvements by area, what was measured, emergencies resolved. It also writes a short text — from the existing numbers only. Florentin checks and publishes it; you get the notification and find it in History › Your months, with Print / PDF.