Skip to end of metadata
Go to start of metadata

AppNexus Seller Tag (AST)

The AppNexus Seller Tag (AST) is a lightweight JavaScript SDK that runs in the header or body of a web page in a user's browser and allows publishers to conduct auctions directly from the page. AST consolidates all ad slots on a page to be auctioned and sends information about them in a single ad request whenever possible. AST loads asynchronously, meaning that ad calls do not block the page content from loading.

AST will work with AMP HTML markup. Currently, banner ads only are supported. Click here for detailed information: https://github.com/ampproject/amphtml/blob/master/ads/appnexus.md

AST uses the "count on begin to render" methodology to track impressions.

In This Section
  • Set up Placements with AST
    Contains a sample web page showing how AST functions can be implemented in the header and body of the page.
  • AST API Reference
    Provides a complete API reference to the functions and options available with AST.

Benefits of AST

AST offers a number of benefits to legacy tags, such as tinytag (/ttj or /tt).

  • Can reduce ad delivery latency, typically resulting in faster page load times
    AST loads tags asynchronously and attempts to consolidate ad slots into a single ad call, reducing both the bandwidth and overhead of multiple ad calls while allowing the page to load while ads are being rendered.

  • Provides advertisers more control when buying inventory
    When ad slots are consolidated, advertisers can make use of additional controls that AppNexus Console provides, such as page-level frequency caps, roadblocks, or competitive exclusions.

  • Can reduce time and effort needed to debug ads on a page
    AST fires events and provides methods to easily debug an ad call to let a seller determine why a campaign is not serving or to quickly identify details of an ad that served. These methods have a global scope, so tools can be easily built on top of AST to capture and log this information as needed. Additionally, details about the auction results are included in the ad call response as a JSON structure, so Fiddler traces can also easily capture necessary information.

  • Provides many ad experiences to advertisers
    Numerous experiences are made available when using AST. In addition to supporting standard banners, AST can simultaneously support rich media, native, or video. If a high value video or native campaign is not available, a banner can serve without any redirects or new auctions.

  • Simplifies ad tagging and setup
    AST is flexible enough to support all ad formats and page integrations. Individual ad slots can be customized in the tag (providing dynamic configuration) or in Console (removing complexity from the tag). Additionally, custom ad rendering can be assigned to each ad slot and hosted with AppNexus. This removes the reliance on the code on page but provides unique, page-specific customization of how an ad renders. This is useful for native ads or when selling multiple ad formats in parallel. Lastly, the same tag can be used in pre-bid setups with a single flag to turn pre-bid support on or off.

  • Maintains support for future ad serving features and ad formats
    AST has been built to be flexible to support features we haven't even thought about yet. By adding options to the tag or within Console, AST will be able to deliver new formats or auction capabilities that we build in the future. As our primary tag, all features will be built and optimized to support AST; other tags will not always be updated.