Integration Option One

Integration Option One typically ensures the best end user experience and fastest results to each browser.

Integration Summary

During ad serving:

  • Products are requested from the e-commerce server

  • Ads are requested to CitrusAd

  • Ads are returned to the e-commerce server

  • The retailer merges ads with the organic product results

  • Ads are served to the retailer's website

  • Ads and organic products are shown on the website together

  • Impressions are reported to CitrusAd

  • Clicks are reported to CitrusAd

  • Purchases related to ads are reported to CitrusAd

For the end user, listings are not shown until merged.

Workflow

Step 1

Customer loads e-commerce website and navigates to either a category page or a search results page.

Step 2

In the example of a customer navigating to a category page, the front end application (website) requests data from the backend server according to categories selected by the customer (e.g Computers - Notebooks).

Step 3

Retailer’s server simultaneously calls the CitrusAd API and requests ads from the “Computers - Notebooks” category. *Retailer also sends customer ID (#13Xv652s) to CitrusAd as part of the Ad request to ensure ads returned are relevant.

Step 4

CitrusAd uses the retailer inventory (catalogue) and sales data to calculate the most relevant ads for the request (for the category and the person viewing the page). Within 50ms CitrusAd will return ads to the Retailer server in the form of product code (GTIN) and URL for Banner Ads.

Step 5

Retailer server sends Product Listing Ads and Banner Ad content to the front end website.

Step 6

Retailer records which ads have been viewed and clicked on within the web browser using the CitrusAd Javascript SDK.

Step 7

Retailer reports any ads that have been purchased to CitrusAd.