LogoLogo
  • Overview
  • What Ads Can Project Agora Commerce Serve?
  • Integration
    • API Introduction
    • Integration Workflow
      • Integration Summary
      • Integration Steps
    • Syncing Data
      • Syncing Data Via File Protocols
    • Syncing Catalog & Products
      • Syncing Catalog and Products Via File
    • Syncing Order Data
      • Syncing Order Data Via API
    • Reporting Clicks and Impressions
    • Integration Checklist
  • Integration Guides
    • HTTP Persistence & Ad Caching
    • Reference
    • Requesting Ads (the "Context" and its Parts)
    • Product Listing Ad Integration Guide
      • Requesting a Category Product Ad
      • Requesting a Search Term Product Ad
      • Requesting a Home Page Product Ad
    • Discovery Product Listing Ad Integration Guide
      • Requesting a Discovery Product Ad
    • Banner Ad Integration Guide
      • Banner Ad Content Standard
      • Requesting a Search Term Banner Ad
      • Requesting a Category Banner Ad
      • Requesting a Home Page Banner Ad
      • The Post Checkout Banner Ad Context
      • Graceful Fallback in the Event That No Ads Are Displayed
    • Banner X Ad Integration Guide
      • Banner X Ad Content Standard
      • Requesting a Category Banner X Ad
      • Requesting a Search Term Banner X Ad
      • Requesting a Home Page Banner X Ad
      • Banner X Ad Reference
      • Graceful Fallback in the Event That No Ads Are Displayed
Powered by GitBook
On this page
  • Adserving Summary
  • Workflow
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
  • Step 6
  • Step 7
  1. Integration
  2. Integration Workflow

Integration Summary

PreviousIntegration WorkflowNextIntegration Steps

Last updated 4 years ago

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

Adserving Summary

During ad serving:

  • Products are requested from the e-commerce server

  • Ads are requested to Project Agora Commerce

  • 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 Project Agora Commerce

  • Clicks are reported to Project Agora Commerce

  • Purchases related to ads are reported to Project Agora Commerce

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 Project Agora Commerce API and requests ads from the “Computers - Notebooks” category. *Retailer also sends customer ID (#13Xv652s) to Project Agora Commerce as part of the Ad request to ensure ads returned are relevant.

Step 4

Project Agora Commerce 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 Project Agora Commerce 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 Project Agora Commerce Javascript SDK.

Step 7

Retailer reports any ads that have been purchased to Project Agora Commerce.