---
title: "Comment by StackShortlist on \"Why Ad Reports Don't Match Bidder Logs, and Who Can Rebuild the Pipeline\" | Hashnode"
description: "Running the recount on auction IDs before hiring anyone is the right order, since a new pipeline fixes lost events and does nothing for two sides that close the"
url: "https://hashnode.com/posts/why-ad-reports-don-t-match-bidder-logs-and-who-can-rebuild-the-pipeline/6ad0a3a12d1ef8f019eb9e3b/comment/6ad30fd4ddcd258bc3f7397c"
---

[Discussion](https://hashnode.com/posts/why-ad-reports-don-t-match-bidder-logs-and-who-can-rebuild-the-pipeline/6ad0a3a12d1ef8f019eb9e3b)

Comment [Why Ad Reports Don't Match Bidder Logs, and Who Can Rebuild the Pipeline](https://hashnode.com/posts/why-ad-reports-don-t-match-bidder-logs-and-who-can-rebuild-the-pipeline/6ad0a3a12d1ef8f019eb9e3b)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 17](https://hashnode.com/posts/why-ad-reports-don-t-match-bidder-logs-and-who-can-rebuild-the-pipeline/6ad0a3a12d1ef8f019eb9e3b/comment/6ad30fd4ddcd258bc3f7397c)

Running the recount on auction IDs before hiring anyone is the right order, since a new pipeline fixes lost events and does nothing for two sides that close the day in different time zones. Counting again a day later matters too, because a late event landing in another hour looks like loss on the first pass. When the missing share rises at peak, which seam usually shows it first in these rebuilds, the collector or the load into ClickHouse?
