Aniview Platform Updates - October 2025

Performance, compliance, smarter monetization.

This month, we have rolled out updates across two core surfaces: Ads Player (AP) and Ad Manager (AM). Below is what shipped, why it matters, and how it impacts your monetization and control.

Ads Player (AP)

Theme: stronger demand, safer defaults, cleaner rendering, and better resilience.

1. Updated Prebid stack and demand access

• Prebid.js upgraded from v9.33.0 to v10.11.0.
  This gives us access to the latest bidding logic, performance improvements, and compatibility updates.
  
  
• New FreeWheel bid adapter (“fwssp”).
  Opens up more premium demand and aligns with partners already using FreeWheel.
  
  
• Added device info into the ortb2 object passed to Prebid.
  Buyers get better context (like device type), which tends to increase bid relevance and yield.
  
  

2. Brand safety and policy guardrails by default

• We now send a default category block list in ortb2.bcat:
  [‘IAB25’, ‘IAB26’, ‘IAB1-8’]
  These map to sensitive/restricted categories.
  
  
• You can still override this with your own adConfig.ortb2.bcat.
  
  
• Note: not all adapters fully support bcat, so treat this as a strong baseline, not a perfect global block.
  
  

3. Auction health and timeout control

• We added an auction.timeout configuration with a default of 8 seconds.
  Why this matters: if a bidder stalls, the auction won’t hang the page forever. You stay fast, and ad delivery doesn’t block content rendering.
  
  
• PubMatic gzip behavior was disabled to avoid compatibility/response issues in some environments.
  
  
• We improved container initialization and recycling logic in certain modes to better recover in “heavy ad intervention” cases (especially when running with imamode = 1).
  
  

4. Currency + tracking intelligence

• We added support for the Prebid.js currency module and the ability to load it conditionally per ad source/advertiser.
  This helps normalize bids across currencies and roll out currency handling gradually instead of flipping it on globally.
  
  
• We introduced conditional tracking support at the advertiser/ad-source level.
  This lets you fire specific trackers only under certain rules (for example: per campaign, per region). This is key for more advanced formats and for Magnetic Player activity.
  
  

5. Cleaner experience and more accurate reporting

• Manual viewability vs. hidden content: we no longer mark placements as “viewable” when the content is actually hidden. That protects you from inflated viewability signals.
  
  
• Consistent identifier macro: we added AV_IFA as an alias for AV_IDFA / AV_AID, so you don’t have to guess which field is available per device.
  
  
• URL-encoded tracking pixels: creative IDs and related values in tracking URLs are now encoded. This prevents broken pixels when special characters (like #) appear in partner macros.
  
  
• Session timeout configuration: you can now configure session timeout behavior, giving you better control over frequency, reporting windows, and compliance rules.
  
  

6. UI / render stability fixes

• Outstream controls fixed.
  “Show Position” and “Show Player Features” in Outstream placements are now working as expected again.
  
  
• showPlayer flag reliability.
  Logic around when the player should (or shouldn’t) render is now behaving consistently.
  
  
• Centered video in fixed-size templates.
  We corrected layout issues where the player wasn’t visually centered in certain fixed-dimension embeds.
  
  
• Heavy ad intervention handling.
  Better detection and recovery in lightweight IMA mode (imamode = 1) helps keep playback alive even when the browser tries to aggressively throttle or kill “heavy” ads.
  
  

7. Easier configuration & integration

• You can now enrich player config using HTML data-attributes, not just runtime JS.
  That’s especially useful if you’re templating the player across many placements.
  
  
• General improvements around container recycling and initialization for more predictable behavior in complex pages.
  
  

In short, Ads Player is now faster to bid, easier to control, safer by default, and more honest about what actually got viewed.

Ad Manager (AM)

 Theme: policy alignment and financial clarity.

1. Default sensitive-category blocking

Ad Manager now applies a default blocklist for restricted categories that lines up with what the Ads Player is already sending in ortb2.bcat.
Result: safer inventory out of the box, less manual policy work on day one.

2. Currency module support

We’ve added support for Prebid’s currency module at the Ad Manager level.
Why this matters:

• If you work with buyers who bid in different currencies, we can normalize those bids for reporting and decisioning.
  
  
• You get cleaner forecasting and billing alignment across regions, instead of stitching it together manually.
  
  

That’s the update. If you encounter unexpected behavior in production, particularly around auction timing, viewability, or Outstream controls, please share the details (placement, behavior, console output). We’ll jump on it. Drop us an email at info@aniview.com.