--- title: "Release 143" description: "51Degrees device intelligence, Pixalate fraud scoring, price adjustment rules, custom country groups, CPC/CPV billing for DSP partners, first-party DMP audiences." type: "reference" audience: [network-manager, admin] keywords: [release 143, release notes, device detection, pixalate, fraud, country groups, price adjustment, DMP] --- Fetch the complete documentation index at: https://epom.com/ad-server/docs/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version. # Release 143 **Released:** October 2025 — February 2026. A foundation release: the platform gained two new intelligence layers — device detection and traffic risk scoring — plus the first version of price adjustment rules. ## New features ### Advanced device intelligence (51Degrees) The platform now detects a rich set of device properties on every request: device vendor, model, release year, RAM, price band, hardware/browser/platform rank, and whether the request comes from an in-app WebView. All of them are available as [targeting dimensions](https://epom.com/ad-server/docs/reference/targeting-dimensions.md) at campaign, site, placement and banner level — including numeric relations for RAM (at least / at most / exactly) — and as [analytics dimensions](https://epom.com/ad-server/docs/reference/analytics-dimensions.md). The same properties are passed to DSPs in bid requests. Detection uses both the User-Agent and modern Client Hints headers. ### Traffic risk scoring (Pixalate) Incoming traffic is scored in real time for fraud probability and classified into risk levels (Low through Certain) and 25+ fraud categories — datacenter/proxy traffic, click farms, bots, app/domain spoofing, click fraud, device-ID stuffing, location obfuscation and more. Risk level and risk category can be used in include/exclude [targeting](https://epom.com/ad-server/docs/reference/targeting-dimensions.md) at campaign, site, placement and banner level, and appear as [report dimensions](https://epom.com/ad-server/docs/reference/analytics-dimensions.md). The feature is switched on per network by Epom — see [moderation and traffic quality](https://epom.com/ad-server/docs/guides/admin/moderation-and-quality.md). ### Price adjustment rules A new rule system dynamically adjusts banner pricing based on conditions — device type, operating system, browser, country and custom parameters — with percentage or fixed-amount actions. Rules are managed in the banner editor, gated by their own permission, and are cloned automatically when a banner is duplicated. See [price adjustment rules](https://epom.com/ad-server/docs/guides/delivery/price-adjustment-rules.md). (Campaign- and advertiser-level rules followed in [Release 145](https://epom.com/ad-server/docs/releases/release-145.md).) ### Custom country groups Administrators can create named [country groups](https://epom.com/ad-server/docs/guides/admin/taxonomies.md) — any combination of countries — and reference them in geo targeting across campaigns, placements, sites and banners, instead of re-selecting the same country list repeatedly. ### CPC and CPV billing for DSP partners [DSP partners](https://epom.com/ad-server/docs/guides/admin/dsp-partners.md) can be billed per click (CPC) or per view (CPV) in addition to the traditional CPM, selected via a new *Pricing Model* dropdown on the partner edit page. Auction price passing and settlement follow the chosen model. ### First-party DMP audiences Advertisers can target their own first-party audience segments: a new first-party DMP type joins the existing third-party integrations, with hierarchical audience-tree navigation in the DMP settings. See [audiences and retargeting](https://epom.com/ad-server/docs/use-cases/retargeting-and-audiences.md). ### Publisher- and advertiser-side macro visibility Entity-name [macros](https://epom.com/ad-server/docs/reference/macros.md) can be selectively exposed to the publisher and advertiser sides via new preference toggles, and deprecated macro names gained clearer replacements (`$$ADVERTISER_NAME$$`, `$$CAMPAIGN_NAME$$`). ### User identifier in AJAX ad tags The AJAX [ad code](https://epom.com/ad-server/docs/guides/inventory/ad-tags-and-api.md) can pass a publisher-provided user identifier (UUID) with each ad request, kept in sync with the user cookie for consistent tracking. ## Improvements - **TrafficHunt** joined the available [DSP partner](https://epom.com/ad-server/docs/guides/admin/dsp-partners.md) types with full OpenRTB integration. - **Video player update** — the Epom video ad player was refreshed with rendering fixes and performance improvements. - **Placement domain default** — a network-wide setting controls whether new placements use the placement domain as channel identifier by default. See [rules and defaults](https://epom.com/ad-server/docs/guides/admin/rules-and-defaults.md). - **Faster banner lists via API** — the banner list endpoint was heavily optimized, cutting database round-trips for large lists. - **More resilient domain parsing** for URLs without protocol or with unusual formats. ## Bug fixes - **Click URL redirects** — more robust parsing of redirect click URLs, including encoded and unencoded values and edge cases with trailing parameters. - **Advertiser API ignored category assignment** on create/update. - **Publisher-side search failed** for users who had view (but not share) permission. - **Device release year targeting** could error during ad matching; the value is now parsed and cached correctly. - **Device detection returned nothing** for requests with no usable evidence instead of an empty result; a client-supplied user agent now takes precedence when provided. - **Scheduled data updates** could fail silently due to a transaction-management issue. - **Programmatic (OpenRTB DSP) creatives are included in video waterfall responses.** ## Under the hood Platform upgrades and performance work. ## Related - [What's new in Epom Ad Server](https://epom.com/ad-server/docs/releases.md) - [Release 144](https://epom.com/ad-server/docs/releases/release-144.md)