Distinguish requested from measured baseline
Your own pre-order observation may differ from the baseline recorded when a service begins. Save both values and their timestamps. If the panel does not define its start-count field, ask how it is obtained and whether it applies to this service type.
Check target identity
A surprising baseline can indicate the wrong content item, a changed URL, or a different metric. Verify the target identifier before calculating a deficit. Similar display names and reposted content can make visual checks unreliable without the direct link.
Avoid unsupported subtraction
Subtracting a start count from a later public total gives a net change, not necessarily the isolated delivery from one order. Other activity or removals may affect the total. Use the service's documented reporting method when deciding whether to open a support request.
Decision checklist
| Decision | What to check |
|---|---|
| Baseline | Value and capture time |
| Target | Exact content identifier |
| Calculation | Net change versus delivery |
Worked example
A hypothetical buyer records 900 before ordering; the panel records 920 when processing starts. A later total of 1,100 represents a 200 increase from the buyer's snapshot and 180 from the panel's baseline. Neither difference alone resolves attribution.
Example figures explain the decision; they are not current prices or promised results.