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
  1. Integration

Reporting Clicks and Impressions

You will need to get your Base URL from Project Agora Commerce before you are able to report impressions and clicks to CitrusAd.

Reporting clicks and impressions can take up to one hour on our staging environment. This is not reflective of production speed and should not be regarded as such.

Project Agora Commerce Javascript Library - Web integrations

The JavaScript Library (formerly the JavaScript SDK) makes it possible to send reports of clicks and impressions to Project Agora Commerce. The Javascript Library adds more tracking information and is advised for web based integrations.

Retailer has to ensure that every click event (Eg. SPL click, SPL add to cart, Banner click) should be connected with the reportClick function.

In addition please ensure that the right clicks and middle-scroll button clicks (as well as left clicks) also should be connected with the reportClick functions

The setup is straightforward. The API currently exposes two methods.

<script type="text/javascript" src="https://assets.citrusad.net/citrusjs/1.2.0/citrus.js"></script>
<script type="text/javascript">
   var citrusAd = CitrusAd.init(
    '$BASE_URL/v1',
    {
      disableTracking: false, // Optional: defaults to false.
      trackingOptions: {
          sessionId: 'YOUR_OWN_TRACKING_TOKEN' // Optional, this token can be used to tie impressions/clicks with a session token that you maintain
      }
    }
  );
  citrusAd.reportClick('adId').then(function (result) {
    console.log(result);
  }).catch(function (error) {
    console.log(error);
  })
  citrusAd.reportImpression('adId').then(function (result) {
    console.log(result);
  }).catch(function (error) {
    console.log(error);
  })
</script>

Here is how to include a file using a script tag:

<script type="text/javascript" src="https://assets.citrusad.net/citrusjs/1.2.0/citrus.js"></script>

PreviousSyncing Order Data Via APINextIntegration Checklist

Last updated 3 years ago