Skip to content

Reading your reporting

What the workspace report totals, why a figure can say "Not reported" instead of zero, and the two ways a figure reaches it.

Updated

Reporting totals the results held against one workspace, organic and paid side by side, and computes the rates over them.

The most important thing to understand before reading a number here is where the rows came from. There are two ways in and no others. A row is either read from a provider account you have connected, by the nightly analytics ingestion, and stored with the account, the period and the moment it was retrieved; or it is written through the workspace report-metrics API, which your own integration calls.

The second thing to understand is what happens when a read cannot happen. Reading needs a connection this deployment can actually use: for most platforms that means the operator holds the platform's application credentials AND the platform itself has granted access for other people's accounts, and it always means the connection still holds a working token. Where any of that is missing, or the provider is unreachable, or it asked us to slow down, nothing is written at all. That is deliberate. An unreadable provider must never turn into a row of zeroes, because a zero is a claim that something was measured. Recording an ad account on this page is separate bookkeeping: it notes that the account belongs to this workspace, and it connects nothing.

The third thing is that a blank is never turned into a zero. A figure nobody reported reads "Not reported"; a figure somebody reported as zero reads as zero and says how many rows measured it. A rate whose denominator does not exist reads as a dash, never as 0%.

BEFORE YOU START

  • The "view" permission for the workspace, and access to the workspace itself.
  • The "connect" permission to record an ad account. Without it the page says so rather than offering a button that fails.
  • Something already recorded. An empty report is an empty report, and the page says which kind of empty it is.

STEPS

  1. Open Reporting for the workspace, or go to /app/workspaces/{workspace}/reporting.
  2. Read the coverage line under the heading. It says how many recorded metrics the totals came from, over what dates, and across which platforms.
  3. Set "From" and "To" and choose "Apply period" to narrow the window. A date that is not in the form 2026-08-15 is ignored and the report falls back to all time.
  4. Read the main table. Organic, Paid and Combined are separate columns, and every cell says how much of the segment reported that figure.
  5. Read "By platform" underneath. Platforms are ordered by engagements, and any platform nobody reported engagements for is placed last rather than ranked beneath a measured zero.
  6. To note an advertising account against the workspace, choose the platform, choose "Record ad account", and give the external id and a display name when prompted.

WHAT YOU SHOULD SEE

Totals with their coverage stated in the cell. A complete figure shows as a plain number. A partial one shows as the total followed by how many of the rows contributed. A genuinely measured zero shows as zero followed by how many rows measured it, so it cannot be mistaken for silence.

WHAT THIS WILL NOT DO

  • It will not fetch anything itself, and neither will this page. Reading happens on a schedule, against accounts connected elsewhere in the product. Recording an ad account here stores its status as recorded, never as connected, and no credential can be stored against it because there is no column for one.
  • It will not export. A downloadable report exists only in the client portal, for clients you have given a portal link to.
  • It will not compare you with anyone. There is no benchmark, no competitor figure and no industry average anywhere in this product.
  • It will not predict. Nothing here forecasts a result or recommends a time to post.

WORTH KNOWING

Some rows were recorded before the system could store "not reported" at all. Where that applies, the coverage line adds a sentence saying how many, and warns that a zero on those rows may be a measurement or may be a figure nobody supplied, and that nothing recorded which. That sentence is a real caveat about your own data, not boilerplate.

IF IT DOES NOT WORK

  • "No metrics recorded yet - the report shows zeroes until organic or paid results are added." means nothing has ever been recorded for this workspace.
  • "No metrics in the selected period - the report shows zeroes for this window. Widen the dates to see other periods." means data exists, but not inside your dates.
  • "Your role cannot add ad accounts here." means you lack the connect permission.
  • "connect permission required." and "view permission required." are the same refusal from the API.
  • "You do not have access to this workspace." means your access does not reach it. A workspace in another organisation returns a plain not-found instead.
  • "That ad account could not be recorded." and "That ad account could not be recorded - the request did not complete." are the two failures the form distinguishes. The second one means the outcome is unknown; reload before trying again.

COMMON QUESTIONS

Why does a rate say a dash rather than zero?

Because the division has nothing to divide by, or because the two figures it divides were reported by different rows. Printing 0% there would be inventing a measurement.

Can I connect a platform so figures arrive on their own?

Yes, where that platform is readable from this deployment. A connected account is read nightly and its figures are written here with their provenance. Whether a given platform is readable is not a setting anybody here can flip: it needs the operator to hold that platform's application credentials, and it needs the platform itself to have granted access for other people's accounts. Until both hold, the read is refused and nothing is written — which is why the report can stay empty even after you have connected something.

Why is my report still empty after connecting an account?

Because a refusal writes nothing rather than zeroes. The connection may be new and not yet read, the token may have expired and need reconnecting, the platform may not have granted this deployment reporting access, or the provider may have been unreachable. In every one of those cases the honest answer is an empty report, not a report full of zeroes.

Why is a platform I publish to missing from "By platform"?

Because no row has ever reported it. The report covers platforms that have data, which is not necessarily everywhere you publish.

  • Attributing revenue to channels

    Reading first-touch, last-touch and linear credit over your recorded touchpoints and conversions, why some conversions are unattributed, and why two currencies are never added together.

  • What your recorded results support

    Reading the performance recommendations, the sample size every claim must clear, and the list of questions the recorded data cannot answer.

  • Slots that have done better

    How the next-best-slot card decides one day and part of the day did measurably better, and the three floors it has to clear.