The following diagram describes the client–server two way communications during the process of standard ad display in the Sizmek platform.


  • (Step 5): In most cases, instead of implementing a 302 redirect response, a JavaScript code that performs the call to the display server is sent. A 302 redirect response is used only in cases where the client has no support for JavaScript or JavaScript is disabled.
  • In some cases, where Rich Media advertising is used – Sizmek can play the role of a 4th party ad server (Rich Media Ad Server). The IAB defines 4th Party Ad Server in Appendix A of the IAB Rich Media Measurement Guidelines: A publisher website has an advertiser that wishes to use one of Sizmek's Commercial Break advertising implementations. The publisher hosts its own ad server. The advertiser's agency uses a 3rd party ad server (other than Sizmek) to coordinate all buys in one location.

    The publisher ad server is loaded with a 3rd party ad tag. When the publisher ad server selects that ad campaign, it issues a redirect to the 3rd party ad tag. The 3rd party ad server, in turn, redirects the browser (using a 302, JavaScript, etc.) to the Sizmek MDX platform, which is housing the Commercial Break.

    In this case, the publisher would be considered the first party, the server that the advertiser's agency's uses to coordinate all media buys would be the 3rd party, and Sizmek the 4th party.


For more information about client-side impression counting, see OVERVIEW: Methodology: Impression Counting, Ad Start, and Clicks.

The following diagram describes the role of the Sizmek platform as a 3rd party ad server:


The following diagram describes the role of the Sizmek platform as a 4th party ad server:

diagram_methodology_Publisher4th party.gif

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request