...

• Q: What are the delivery options for batch win logs?
  A: In batch, either hourly or daily. Batch files are always joined, which means conversion and click data is matched against impression data.
  
  
• Q: Does viewability data from IAS and/or Moat always come through in win logs?
  A: This can vary slightly dependent on when we receive the log files from the provider. typically IAS delivers data once per day, whenever they send their feed. Meanwhile, Moat delivers data to Beeswax hourly.
  
  
• Q: What time does Beeswax write daily batch win logs to customer S3 buckets?
  A: Between 6-7am ET (6am during daylight savings time, 7am during non-DST periods)
  
  
• Q: Why are there duplicate auction_adgroup_id's?
  A: These events are from the browser/app, so these may be re-rendered from the browser/app. Auction IDs will only be de-duped in batch logs.
  
  
• Q: How do you deduplicate impressions?
  A: Beeswax deduplicates all impression events using auction_adgroup_id in batch logs.
  
  

...

Streaming Win Logs

• Q: What are the delivery options for streaming win logs?
  A: Win logs are available for streaming (real-time) via HTTP or Kinesis in either JSON or Protocol Buffer (Protobuf) formats. Streaming logs can be joined or unjoined.
  
  
• Q: What are the differences between Real-time (Streaming) Joined and Unjoined Logs?
  A: Unjoined logs will never contain information about the auction associated with the impression. Joined logs will match auction data, as well as click, activity and conversion data, back to the won Impression data in a single message.Unjoined logs will send a separate “unjoined” message for any Impression, Click, Activity or Conversion that occurs for a given auction_adgroup_id. In joined logs, as more information is received about a win event, a message will be sent with new information appended to the previously sent message for that Auction ID. This means new messages may repeat data from the same Auction ID that have already been logged.
  
  
• Q: Are there AWS region requirements for Streaming Win Logs?
  A: Kinesis: For unjoined logs, a Kinesis Stream must be co-located in the same region as the bidder instance. For joined logs, the Kinesis Stream must be co-located in US-EAST-1. HTTP: There are no requirements for colocation for an HTTP endpoint.
  
  
• Q: What types of events will I receive in my Streaming Win Logs?
  A: Joined and Unjoined Logs will receive slightly different sets of events with different behaviors:

...

• Q:How can I use Segment Logs?
  A: Standard Auction logs will limit the segment_id field to 600 characters, however Segment Logs will give you a complete listing of matched 1st party segments. By joining Auction and Segment Logs on auction_adgroup_id (as the key), you will extend your ability to do Audience Forecasting and Attribution. Both these use-cases require being able to see all segments on a given auction.
  
  

...

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. We always recommend de-duplicating your log-level data on auction_id or auction_adgroup_id in the case of bid logs or conversion_id in the case of conversion logs.

...

Q: Why do bid logs need to be de-duped on auction_adgroup_id?
A: In the case of bid logs, we recommend de-duping by auction_adgroup_id, as multiple bids can be submitted for the same auction_adgroup_id by different line items.