The Shopalyst landing page can be utilized as an ad by leveraging the HTML5 creative approach. This method is supported on platforms that accommodate HTML5 creatives. The ideal ad placement for this approach is half-page ads, with dimensions of 300x600 (width x height).


The system supports two primary use cases:

  1. Standard HTML5 Ad Tag - Compatible with platforms like Google Ads, DV360, and similar.
  2. MRAID-Compliant Ad Tag - Designed for platforms such as InMobi, Xandr, and others


1. Standard HTML5 Ad Tag

This option involves sharing a ZIP file containing an HTML file with the following functionalities:

  • Meta Tag for Ad Size:
    The file includes a meta tag (ad.size) to define the ad's dimensions.
  • Impression Tracker:
    Upon serving the ad, an impression tracker fires using a 1x1 HTML image tag (<img>).
  • Shopalyst Landing Page in an iFrame:
    The HTML file renders the Shopalyst landing page within an iframe, set to occupy 100% of the ad's width and height.
  • Click Tracker Trigger:
    The first click anywhere inside the iframe triggers a click tracker, while subsequent clicks do not.
  • Optional Brand Safety Tag:
    If the brand requires additional tracking for brand safety, the system can trigger this tag alongside the impression tracker.



2. MRAID-Compliant Ad Tag

MRAID-compliant ad tags follow the Mobile Rich Media Ad Interface Definitions (MRAID) API standard. These tags enable rich media ads to interact with mobile apps using HTML5 and JavaScript.

This option involves sharing a ZIP file containing an HTML file that performs the following actions:

  • MRAID SDK Integration:
    The file expects the presence of the MRAID SDK in the ad environment. It listens for the ready event broadcast by the SDK.
  • Device Orientation and Screen Size:
    Once the SDK is ready, the ad unit:
    • Fixes the device orientation to portrait.
    • Detects the screen size and renders an iframe to fill 100% of the detected width and height.
    • Loads the Shopalyst landing page inside the iframe.
  • Click Tracker Trigger:
    The first click anywhere on the ad unit triggers a click tracker. The click tracker is implemented using the ${CLICK_URL} macro, which the ad environment populates dynamically.
    • Note: No impression tracker is supported for MRAID-compliant ad tags.


Brand Requirements for Activating Ad Tags

To take an ad tag live, the following elements are required:

For Standard HTML5 Ad Tag:

  • Click Tracker: Mandatory
  • Impression Tracker: Optional

For MRAID-Compliant Ad Tag:

  • Click Tracker: Mandatory


How to Set Up a Landing Page and Download an Ad Tag


1. Select the Purpose:

Use the create landing page workflow in the experience module and select the purpose based on the type of ad tag you want to generate. See the screenshot below.


2. Set Up Trackers:

Configuring the tracker provided by the brand. Trackers can only be set up during the creation stage. Ensuring that all trackers are accurately added, as changes cannot be made later.


3. Add Widgets

Add widgets to the landing page, just as you normally would. Customize the page with the desired elements to enhance its functionality and user engagement.


4. Submit and Download the Ad Tag

Once the setup is complete, submit the landing page. A modal will appear, offering the following options:

  • Download the Ad Tag: Click to download the generated ad tag.
  • Validate the Ad Tag: A link to the Google HTML5 Ad Validator will be provided. Use this tool to verify the validity of your ad tag.


5. Validate the Ad Tag

Upload the ad tag to the Google HTML5 Ad Validator and ensure that all checks are marked green, except for the relative asset check, which is acceptable in this case.




What to Monitor After the Ad Tag is Shared with the Brand and Goes Live

  • Data Discrepancies: Be aware of potential differences between the data recorded by the impression tracker and the store views displayed on our dashboard. These discrepancies primarily arise due to filtering mechanisms employed by most ad platforms. These platforms use additional signals (not accessible to us) to determine the authenticity of impressions.


  • Custom Reports: Please reach out to Ops team for tailored reports on campaign statistics or engagement metrics.



Looking for more help? Instructions to reach out to support is here.