Page History

...

• When Does this Occur: Impressions have been successfully emitted in Win Logs, but Beeswax has since detected that there was a methodology error rendering one or more field’s data incorrect for the emitted impressions. 
• How Does Beeswax Address: Beeswax will reissue corrected impression data and deliver it to the /backfill directory within a customer’s S3 bucket. A Status Page will be posted alerting customers to the backfill and communicating the field(s) that is/are affected, what is changing, and the rx_timestampdate range of impacted impressions. 
• Customer Action: If the impacted field is a field that is important to your data architecture, ingest the impressions from the /backfill directory to replace the corresponding impression data previously delivered, deduping on auction_adgroup_id. If the impacted fields are not relevant to your data architecture, no action is required.

...

As with all other Log Types, Beeswax uses auction_adgroup_id as our unique key in Win Logs. Customers should always use auction_adgroup_id for deduplication.

Antenna Win Logs

...

Beeswax Data Infrastructure uses an "at least once delivery" design pattern to ensure all events are eventually delivered to customers. In certain scenarios, this may mean that duplicative data is sent in logs to customers. WeBeeswax always recommend recommends de-duplicating your log-level data on auction_id or auctionon auction_adgroup_id in the case of bid logs or conversion_id in the case of conversion logs.