Amazon Web Services on November 19, 2026, made AWS RTB Fabric Modules generally available through AWS Marketplace, allowing ad tech platforms to attach outside vendors' fraud screening, device data and placement quality scores to bid traffic as it crosses Amazon's private auction network. The first three modules come from Pixalate, WURFL by ScientiaMobile and Picnic, and their charges appear on the customer's AWS bill instead of on separate vendor invoices.
In Short
AWS now lets companies that buy and sell ads over its RTB Fabric network add data from outside vendors, such as fraud screening from Pixalate, device details from ScientiaMobile and placement quality scores from Picnic, to each bid request as it passes through. That matters to ad tech platforms and publishers because each new data source has until now needed its own integration, contract and engineering work, and AWS says the modules run within single-digit milliseconds. The change is in the plumbing and the paperwork: vendors list once on AWS Marketplace and AWS does the billing, although no prices have been published and a link holds only two modules under the default quota.
What AWS put on the shelf
The announcement appeared on the AWS for Industries blog under the headline "Introducing AWS RTB Fabric Modules available through AWS Marketplace: AdTech partner intelligence, inline in the bid path." Three people signed it: Sergio Serra, the product leader for AWS RTB Fabric; Jonathan Harmms, a product marketer for the advertising and marketing industry at AWS; and Trevor Dyck, head of product for AWS RTB Fabric. According to AWS, the modules entered general availability to give ad tech companies and their partners "ad intelligence and decisioning capabilities" inside their real-time bidding workloads.
AWS frames the problem in terms of signals. Brand safety, fraud, device and inventory quality data determine "which impressions advertising technology (AdTech) companies win, what they pay, and whether they overpay for the wrong ones," according to the post. Moving those signals from specialist vendors into the path of a bid has been slow and expensive. "Each new partner means a custom integration, its own contract, and weeks to months of engineering work, and each one adds latency to a bid path where every millisecond counts," the post states. The result, AWS argues, is engineering teams maintaining integration code when they could be building their own platforms.
The proposed fix is a subscription. Demand-side platforms, supply-side platforms and publishers running on RTB Fabric can now, according to AWS, "discover, configure, and deploy partner signals directly to their RTB workloads in minutes, with no custom integration, running inline at single-digit millisecond latency." Third-party module providers, on the other side of the transaction, can reach RTB Fabric customers "from a single AWS Marketplace listing."
AWS lists four benefits for the platforms that buy modules. They can be found on AWS Marketplace and attached to an RTB Fabric link without custom integration code. They filter invalid requests before the bidder deserializes and evaluates them, which AWS says cuts wasted compute. They run inline on the RTB Fabric network, colocated with the bidding workload, "with no extra network hops." And partner charges appear on a single AWS bill, so ad operations and procurement teams manage fewer vendor contracts and invoices.
For vendors, the offer is distribution. Module providers gain access to "programmatic advertising workloads that were previously difficult to reach through traditional integrations or a software catalog," according to the post. A provider builds a module once and reaches customers through one listing, and AWS says it keeps full control of its data and intellectual property, with no per-customer integrations and no colocated infrastructure of its own.
Three vendors, three kinds of signal
Modules plug into RTB Fabric links to filter, enrich or observe bid requests before they reach a bidder, according to AWS. Each module is a separate building block, which means a platform can choose a different provider for each signal "instead of accepting whatever comes bundled in a single stack."
Pixalate, which AWS describes as a global platform specializing in privacy compliance, ad fraud prevention and digital ad supply chain data intelligence, supplies a module called IVT Blocking, Bid Enrichment & CTV Show-Level Intelligence. It screens invalid traffic before it reaches the bidder and adds the show, channel, genre and content rating to connected TV bid requests. Coverage, according to AWS, spans more than 770,000 US streaming TV shows across more than 17,900 FAST and linear channels.
Those numbers have moved quickly. When Pixalate released its OpenEPG DB 1.0 and Pre-Bid API on September 21, 2026, the database covered more than 13,900 channels and more than 580,000 shows. By PPC Land's calculation, the November figures are about 4,000 channels (29%) and 190,000 shows (33%) higher in under two months, although all four numbers are floors rather than exact counts. The September release already described an in-bidstream version for RTB Fabric with a latency of about 5 milliseconds at the median and 12 milliseconds at the 99th percentile, against a 10-millisecond median target for Pixalate's separate REST interface. Weeks later, the company added a clawback warning label to its ratings of apps and sites, based on buyers' invalid traffic disputes.
WURFL by ScientiaMobile draws on more than 120,000 device profiles. Its module, WURFL Device Signals, recognizes the device from the request's own fields and adds consistent attributes to OpenRTB bid requests as they pass through RTB Fabric: device type, make and model, operating system, browser, screen and bot flags. On AWS's product page for modules, ScientiaMobile states that more than 99% of requests are enriched, a figure it attributes to web bid traffic.
Picnic Inventory Quality, or PIQ, scores inventory across more than 100 signals "right down to placement level, using proprietary data," according to AWS. The module matches every bid request to the most specific placement it can and returns a PIQ Score in real time. It works in two ways. In filtering mode, PIQ decides which requests are worth passing on, which reduces the volume a platform pays for and processes; in enrichment mode, the score and its signals are added to each request so that the bidder can weigh placement quality alongside audience and price. The module covers display and video, with "no feed or integration to build."
| Provider | Module name | What it does, according to AWS | Scale stated |
|---|---|---|---|
| Pixalate | IVT Blocking, Bid Enrichment & CTV Show-Level Intelligence | Screens invalid bid requests before the bidder; adds show, channel, genre and content rating to CTV bid requests | 770,000+ US streaming TV shows; 17,900+ FAST and linear channels |
| WURFL by ScientiaMobile | WURFL Device Signals | Identifies the device from request fields; adds device type, make and model, OS, browser, screen and bot flags | 120,000+ device profiles |
| Picnic | Picnic Inventory Quality (PIQ) | Matches requests to placements and returns a PIQ Score; filtering or enrichment mode; display and video | 100+ signals, down to placement level |
How a module reaches a link
According to the AWS RTB Fabric User Guide, attaching a vendor module happens in two stages, subscription and attachment. The console path the guide describes has six steps:
- Under Module marketplace in the console's navigation pane, the Discover modules page lists available modules, searchable by name, vendor or function and filterable by category. Choosing View details opens a module's page.
- On that page, View subscription options, or Try for free where a vendor offers it, leads to pricing and terms. Accepting the offer creates an AWS Marketplace agreement, and the charges appear on the customer's AWS bill.
- Subscribed modules appear on the My modules page, where a Source column shows whether each one came from AWS Marketplace or is built in. Subscribing alone does not change traffic, according to the guide; a module processes requests only once it is added to a link's flow.
- From My modules, Attach to link opens the attachment screen. Gateway type stays on Responder gateway, the gateway and link are selected (only active links are shown), and Configure flows opens the flow editor.
- On the Configure flow screen, under "Modules you can add", the module version is selected and Copy snippet produces a configuration fragment. That fragment is pasted into the modules list in Flow configuration (JSON), adjusted according to the vendor's instructions, and submitted.
- The change then rolls out asynchronously. The link keeps serving its previous flows until the update applies, and if the update fails, the link returns to an ACTIVE state with its old configuration.
The command line follows the same sequence in three calls, according to the guide: get-link to retrieve a lockToken, put-link-flows with that token and the new flow definition, which returns a PENDING_UPDATE status and an updateId, and get-update to track progress. Renewals and cancellations are handled in the AWS Marketplace console, and the guide notes that AWS Marketplace and AWS License Manager permissions are needed alongside RTB Fabric permissions.
Rules written into the documentation
The guide is precise about limits, and some of them qualify the marketing. "A link has at most one flow," it states, and the modules in a flow count against a "Modules per flow quota, which is 2 by default." Going over the quota returns a ServiceQuotaExceededException. With three vendor modules on sale at launch, a link on the default quota can run at most two of them at the same time, by PPC Land's reading of the guide; the page does not say how a higher quota is granted.
Order matters too. In a sequential pipeline, "modules run in order, and each module sees the previous module's output." In a phased pipeline, "phases run in order, and the modules in a phase run at the same time on the same request." In either design, "A response from any module, such as a no-bid, ends the flow."
Failure handling is set per module through a failureMode field: "OPEN continues the flow, and CLOSED answers the request with a no-bid response." Vendor modules "default to OPEN." In the guide's worked example, a module call that fails or times out lets the flow continue without that module's result, while the link's own timeout still applies to the whole request. An activationPercentage value between 0 and 100, defaulting to 100, sets the share of requests a module sees, sampled independently for each request. Vendor enrichment is written into the bid request under ext.rtbfabric.modules followed by the module's name, with an outcome of ALLOW or DROP.
Changes are all or nothing. "Submitting replaces the link's whole flow," the guide warns, and "The update can take up to 30 minutes, and longer in some cases." That is a ceiling for applying a configuration change, not the engineering timeline AWS compares itself against when it promises integration "in minutes, not months," but it is a longer wait than the "few clicks" Serra described in a LinkedIn post.
Vendor modules join modules that AWS supplies itself. According to AWS's general availability notice of October 23, 2025, RTB Fabric launched with three built-in modules aimed at optimizing traffic, improving bid efficiency and increasing bid response rates. The guide currently documents three built-in modules.
| Built-in module | Module ID and version | Parameters in the guide |
|---|---|---|
| Rate Limiter Module | module-rateLimiter, 1.0.0 | tps (required), "from 1 through 16,777,216"; runs on every request and takes no failureMode |
| No-bid module | module-noBid, 1.0.0 | Optional reason (up to 50 letters and digits) and reasonCode (0 through 10); with reasonCode the response is HTTP 200 with the code as nbr, without it HTTP 204 with no body |
| OpenRTB Attribute Module | module-openrtbAttributeFilter, 2.0.0 | filterType, filterConfiguration, optional action |
The network underneath
RTB Fabric is just over a year old. AWS launched the service on October 23, 2025 as a managed network for bidding workloads in six regions - US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Tokyo), Europe (Frankfurt) and Europe (Ireland) - priced per billion transactions with no upfront commitments. The November post calls it "a fully managed service purpose-built for real-time bidding workloads that delivers single-digit millisecond latency." According to AWS, Amazon Ads, GumGum, Kargo, MobileFuse, TripleLift, Viant, Yieldmo and others use it to reach supply and demand partners on a private network and "save up to 80% compared to standard networking costs, without colocated infrastructure or upfront commitments."
The service has picked up features and customers since. AWS let bidders keep their own domains in May 2026 by pointing existing endpoints at a regional RTB Fabric gateway through a CNAME record, so that partners change nothing on their side. In June, Bigabid joined, a Tel Aviv mobile DSP whose arrival Dyck announced on LinkedIn.
The November post includes a list of customer results. Every figure comes from AWS, and the baselines differ: some compare with the public internet, one with direct routing, others with standard networking costs. None states a measurement period.
| Company | Result, according to AWS | Baseline stated |
|---|---|---|
| Yieldmo | More than 80% fewer timeouts; higher bid rates | Not stated |
| CloudX | More than 5 billion bid requests a day; up to 75% lower networking costs per request; 13.3% lower timeout rate | Direct routing |
| Axel Springer (first publisher on RTB Fabric) | Median bid latency from 45 to 80 ms down to under 10 ms; bidder timeouts from 8 to 12% down to under 2%; data transfer costs down 66%; yield up 2% | Its own earlier figures |
| UNICORN and fluct | Network costs down by up to 86%; all RTB traffic between their SSP and DSP moved to RTB Fabric; UNICORN processes more than 1.2 trillion impressions a month | Public internet |
| TripleLift | Key partners connected in under 10 minutes; 15 to 20% lower latency; 30% more ad spend; 30% more win volume; more than 80% lower networking costs | Public web |
| Azerion | More than 50% fewer timeout and connection errors | Not stated |
| Viant and Bigabid | More than 80% saved on networking costs each; Bigabid reinvested savings in model compute and more queries per second | Not stated |
| Amazon Publisher Services | Global RTB workloads at millions of queries per second | Not applicable |
What the partners said
Viant, a customer rather than a module provider, was the only buyer-side company quoted. "AWS RTB Fabric Modules accelerate how quickly new data and intelligence can be put to work for advertisers," said Keith Petri, SVP Data + Identity at Viant. "Viant has been on RTB Fabric since early access, and Modules let a partner's signal reach our bid path through configuration instead of a lengthy engineering project. That matters because advertisers rely on us for the intelligence we bring to every impression, across identity, content, and attention. The faster a new signal goes live, the sooner it shows up in their performance."
Each launch vendor gave its own account. Amin Bandeali, CTO of Pixalate, put a number on the compute argument: "Pixalate's modules screen invalid bid requests on AWS RTB Fabric before they reach the bidder, cutting wasted compute by up to 15%, and a single AWS Marketplace listing lets us reach RTB Fabric customers."
Luca Passani, CTO of ScientiaMobile, focused on data quality. "Device data in bid requests is often thin and inconsistent, yet the device is a core signal in programmatic advertising," he said. "WURFL Device Signals on AWS RTB Fabric brings that missing signal back to the auction, with no installing, integrating, or updating. Customers attach the module, and we keep the device data current with full control of our intellectual property."
Matthew Goldhill, founder and CEO of Picnic, described the old route. "Until now, getting placement-level quality data to the platforms that buy and sell media took a custom integration for each one," he said. "Any DSP or SSP on AWS RTB Fabric can switch on Picnic Inventory Quality (PIQ) in minutes, so more spend goes to placements that perform. The more platforms that use it, the healthier the Open Web becomes for buyers, publishers, and readers alike."
The product lead's version
Serra gave a more personal account in a LinkedIn post that links to the AWS announcement. He wrote that his goal on joining AWS, after years building ad exchanges and bidding platforms, was to "help make it the best cloud for running real-time bidding" applications. RTB Fabric followed "nearly a year later, in October 2025," and he called it "one of the most successful launches at AWS," without offering a measure. His list of companies that used the service in its first year differs from the blog's: he names Yahoo DSP, Viant Technology and TripleLift, and Yahoo DSP does not appear in the AWS post's customer list.
"This one is personal for me," he wrote of the modules. "I remember how much engineering work it took to get one more signal into a bid request. Even something as simple as identifying the make and model of a phone meant building and maintaining an integration." According to Serra, the process "all takes a few clicks, and the modules are automatically installed and colocated for laser-fast latency." He thanked the teams at ScientiaMobile, Picnic and Pixalate for building the first modules, and closed with a forecast: "More big names in ad tech are dropping their own RTB Fabric modules soon." He named none of them.
A crowded race for the bid path
AWS is not the only company trying to move third-party logic closer to the auction. IAB Tech Lab's Agentic RTB Framework, declared final as version 1.0 on August 12, 2026, specifies how containerized agents are deployed inside bidding infrastructure. When the framework opened for public comment in November 2025, Amazon Ads sat in the working group behind it, and the draft listed Amazon's Elastic Container Service as one deployment option.
Exchanges have built their own versions. In April 2026, Bedrock became the first DSP to run its full bidder inside Index Exchange's Index Cloud, with a container execution window Index put at under five milliseconds. In June, PubMatic opened Decision Fabric, which hosts partners' decisioning models as Docker containers inside its auction and returns segment IDs in under ten milliseconds, according to the company, which says it handles 2.7 trillion bid requests a day. Amazon Ads, for its part, donated its Dynamic Traffic Engine to IAB Tech Lab in April 2026, open-sourcing a system in which DSPs publish signal files so that SSPs can drop unwanted bid requests before sending them.
What separates the AWS approach is location. Index and PubMatic run partner code inside their own exchanges. AWS places modules on the links between RTB Fabric customers and their partners, at the network layer, so the vendor's signal is attached before the request reaches whichever bidder sits at the other end. The November post does not mention the Agentic RTB Framework, and it does not say whether modules are built to that specification.
Why it matters for marketers
The effect on advertisers is indirect but real. Every bid request a DSP evaluates costs compute, and every request that turns out to be fraudulent or poor quality costs more if it is bought. Pixalate's claim that screening invalid requests before the bidder cuts wasted compute by up to 15% would show up first in platform costs and only later, if at all, in what advertisers pay. The scale of programmatic waste is well documented: figures cited in coverage of Amazon's traffic-filtering donation put publishers' share at 51 cents of each dollar, according to ISBA, and the share of programmatic spend going to non-working media at 42%, according to the ANA.
The procurement change may matter as much as the technology. Ad tech companies that buy data from several vendors typically hold a contract with each; under this model, the vendor's charge becomes a line on the AWS invoice. AWS Marketplace is turning into a procurement route well beyond advertising. On November 9, 2026, AWS customers gained the ability to buy ChatGPT Enterprise through the marketplace, with eligible spend counting toward their AWS commitments subject to their agreements. The modules post says nothing about whether module charges are treated the same way.
The arrangement also deepens Amazon's position in the supply chain. Amazon operates the network, runs the marketplace that bills for vendor data and is itself a participant, since Amazon Ads and Amazon Publisher Services are among the customers AWS lists. PPC Land examined AWS's widening reach in October 2025, when AWS began to look like central infrastructure for advertising beyond Amazon's own business. For vendors such as Pixalate, ScientiaMobile and Picnic, a single listing replaces dozens of integrations, but it also routes their commercial relationship with RTB Fabric customers through Amazon.
Publishers have their own numbers to weigh. Axel Springer's reported drop in median bid latency from 45 to 80 milliseconds to under 10, with yield up 2%, is the clearest publisher case AWS has offered, and it predates modules. Whether third-party signals attached at the network layer lift publisher revenue further is not addressed in the post.
What the post does not say
AWS published no module prices and did not say what it charges vendors for listings, in which regions modules are available, whether module spend counts toward AWS commitments or whether modules follow IAB Tech Lab's framework. The customer results carry no measurement periods and have not been independently verified.
Key facts
- Product: AWS RTB Fabric Modules available through AWS Marketplace, generally available
- Announcement: "Introducing AWS RTB Fabric Modules available through AWS Marketplace: AdTech partner intelligence, inline in the bid path," AWS for Industries blog, by Sergio Serra, Jonathan Harmms and Trevor Dyck, November 19, 2026, https://aws.amazon.com/blogs/industries/introducing-aws-rtb-fabric-modules-available-through-aws-marketplace-adtech-partner-intelligence-inline-in-the-bid-path/
- Product page: https://aws.amazon.com/rtb-fabric/features/modules
- Launch modules: Pixalate IVT Blocking, Bid Enrichment & CTV Show-Level Intelligence; WURFL Device Signals (WURFL by ScientiaMobile); Picnic Inventory Quality (PIQ)
- Module functions: filter, enrich or observe bid requests before they reach the bidder
- Target customers: demand-side platforms, supply-side platforms and publishers running on AWS RTB Fabric
- Billing: subscription creates an AWS Marketplace agreement; partner charges appear on the AWS bill; no prices in the announcement
- Documentation: AWS RTB Fabric User Guide, discovering and attaching modules, https://docs.aws.amazon.com/rtb-fabric/latest/userguide/discovering-attaching-modules.html
- Default limits: one flow per link; "Modules per flow quota, which is 2 by default"; flow updates "can take up to 30 minutes, and longer in some cases"
- Failure default: vendor modules "default to OPEN" (the flow continues without the module's result)
- Built-in modules: Rate Limiter Module (module-rateLimiter 1.0.0), No-bid module (module-noBid 1.0.0), OpenRTB Attribute Module (module-openrtbAttributeFilter 2.0.0)
- Underlying service: AWS RTB Fabric, generally available October 23, 2025, in US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Tokyo), Europe (Frankfurt) and Europe (Ireland)
- Quoted: Keith Petri, SVP Data + Identity, Viant; Amin Bandeali, CTO, Pixalate; Luca Passani, CTO, ScientiaMobile; Matthew Goldhill, founder and CEO, Picnic
- LinkedIn post: Sergio Serra, product, Amazon (AWS), linking to the announcement
Timeline
- October 23, 2025 - AWS launches RTB Fabric in six regions, with up to 80% lower networking costs claimed.
- October 29, 2025 - PPC Land examines AWS's role as infrastructure for advertising beyond Amazon's own business.
- November 13, 2025 - IAB Tech Lab opens its Agentic RTB Framework for public comment, with Amazon Ads in the working group.
- April 2026 - Amazon Ads donates its Dynamic Traffic Engine to IAB Tech Lab as open source.
- April 21, 2026 - Bedrock's DSP bidder goes live inside Index Exchange's Index Cloud.
- May 2026 - AWS RTB Fabric adds custom domain support for bidders.
- June 1, 2026 - PubMatic launches Decision Fabric for partner models inside its auction.
- June 12, 2026 - Trevor Dyck announces that Bigabid has joined AWS RTB Fabric.
- September 21, 2026 - Pixalate releases OpenEPG DB 1.0 and its Pre-Bid API, covering more than 13,900 channels.
- October 2026 - Pixalate adds a clawback warning label to its ratings of apps and sites.
- November 9, 2026 - ChatGPT Enterprise becomes available on AWS Marketplace.
- November 19, 2026 - AWS makes RTB Fabric Modules generally available through AWS Marketplace, with Pixalate, WURFL by ScientiaMobile and Picnic as launch partners.
- November 19, 2026 (US time) - Sergio Serra publishes a LinkedIn post on the launch, saying more ad tech companies will release modules soon.
Related PPC Land coverage
- AWS launches dedicated network for real-time ad bidding workloads - The October 2025 launch of RTB Fabric, its six regions, pricing model and early customers.
- AWS RTB Fabric now lets bidders keep their own domains - How RTB Fabric added custom domains through CNAME records pointing at regional gateways.
- Bigabid joins AWS RTB Fabric as mobile DSP bets on ML depth - A mobile DSP reporting more than 80% networking savings and reinvesting them in model compute.
- AWS becomes central infrastructure for advertising beyond Amazon's own business - An October 2025 analysis of AWS's growing role in advertising technology, with critical commentary.
- Pixalate API adds show titles to CTV bids across 13,900 channels - Pixalate's September 2026 show-level CTV data release, including the latency figures for its RTB Fabric version.
- Pixalate flags apps and sites hit by ad fraud clawbacks in 12 months - A ratings label built on buyers' invalid traffic disputes, applied across more than 17.5 million CTV apps, mobile apps and websites.
- PubMatic puts partner AI models inside the auction with Decision Fabric - An exchange-hosted alternative that runs partner containers inside PubMatic's auction.
- Bedrock becomes first DSP to run its bidder inside an exchange - Index Exchange's Index Cloud hosting a full DSP bidder as a container.
- IAB Tech Lab opens agentic RTB framework for container-based advertising - The industry specification for deploying containers inside bidding infrastructure.
- Amazon gives away the tool that fixes programmatic's QPS waste problem - Amazon Ads' Dynamic Traffic Engine, donated to IAB Tech Lab to filter bid requests before they are sent.
- AWS customers can now buy ChatGPT Enterprise against cloud commitments - How AWS Marketplace billing and commitment drawdown work for a third-party enterprise product.
Summary
Who: Amazon Web Services, through its AWS RTB Fabric team (Sergio Serra, Trevor Dyck and Jonathan Harmms), with launch module providers Pixalate, WURFL by ScientiaMobile and Picnic, and Viant quoted as a customer. The products are aimed at demand-side platforms, supply-side platforms and publishers.
What: AWS RTB Fabric Modules became generally available through AWS Marketplace. Third-party modules attach to RTB Fabric links to filter, enrich or observe bid requests before they reach a bidder, with partner charges billed through AWS. The default quota allows two modules per flow and one flow per link.
When: November 19, 2026, on the AWS for Industries blog, followed by a LinkedIn post from Serra. RTB Fabric itself has been generally available since October 23, 2025.
Where: On the AWS RTB Fabric network, which launched in six AWS regions across the United States, Asia Pacific and Europe, and in AWS Marketplace. The post does not list regions for modules.
Why: AWS says each new data partner in the bid path has meant a custom integration, a separate contract and weeks to months of engineering, plus added latency. For the marketing community, the launch moves fraud, device and placement quality data into the auction path at the network layer and makes AWS the billing party for those vendors, while prices and several operating details remain undisclosed.
Discussion