Architecture and Integration

Introduction

The Cxense Advertising SaaS platform consists of three primary infrastructure deployments:

1. Cloud based services hosted with 24x7 support.

2. AdServers in locations close to your portal infrastructure.

3. Static content located in a Content Delivery Network (CDN).

This page gives you an overview of how these deployments work together and integrate into your environment.

Typical Scenario

The figure below depicts the typical deployment scenario for Cxense Advertising and related services.

A common process is as follows:

1. The Site Owner (a "Publisher" in cX:ad terminology) makes use of the cloud services (the AdManager UI specifically) to create an AdSpace. The AdManager UI presents a JavaScript fragment that is then inserted into page templates on the Site Owner's web site or portal. An example of the JavaScript fragment is below.

   <script type="text/javascript">
          (function() { try {
              var scriptEl = document.createElement('script'); scriptEl.type = 'text/javascript'; scriptEl.async = 'async';
              scriptEl.src = ('https:' == document.location.protocol) ? 'https://scdn.cxense.com/cx.js' : 'http://cdn.cxense.com/cx.js';
              var targetEl = document.getElementsByTagName('script')[0]; targetEl.parentNode.insertBefore(scriptEl, targetEl);
          } catch (e) { }; })();
      </script>
      <script id="scriptForAdSpace_000000000031068f" type="text/javascript">
          var cX = cX || {}; cX.callQueue = cX.callQueue || [];
          cX.callQueue.push(['insertAdSpace', { adSpaceId: '000000000031068f', adUnitWidth: 728, adUnitHeight: 90, initialHorizontalAdUnits: 1, initialVerticalAdUnits: 1}]);
      </script>
   

2. An End User visits pages on the web site.

3. The web site returns a page to the End User which includes a reference to the static JavaScript fragment hosted on the CDN. The fragment is hosted on a CDN to reduce latency and provide scale and fault tolerance.

4. The End User's browser asynchronously retrieves the JavaScript fragment and executes it. We use asynchronous execution to reduce the latency impact on the page delivered by the web site.

5. As a result of executing the JavaScript fragment, the End User's browser makes a request to the AdServers hosted in the Cxense Advertising edge data centre. The AdServer executes the request and responses with the appropriate advertisements.

6. The AdServer then logs this delivery of advertisements (an impression) and sends these logs to the cloud service for reporting in the AdManager UI.

Last updated: December 22, 2021