Skip to main content

Ad Request & Rendering Flow (User Journey)

This guide explains the real-time communication between your platform and GoWit during ad rendering. It clarifies responsibilities and ensures compliance and effectiveness.

1. User Visits a Page​

When a user navigates to any page (category, search results, homepage, PDP, etc.):

  • Your platform builds a list of organic products from your own catalog.
  • You send a real-time ad request to GoWit, including:
    • placement_id
    • session_id
    • Relevant contextual product IDs
    • Customer information (if available)

2. GoWit Returns Eligible Ad Units​

GoWit responds with a ranked and filtered list of ads.
Each ad payload includes:

  • product_id
  • advertiser_id
  • ad_id
  • position
  • redirect
  • img_url (if applicable)
  • html (for HTML creatives — a ready-to-render snippet with tracking already embedded; see below)

These ads arrive in their intended display order and are ready for insertion into your feed.

3. Partner Responsibilities​

You are responsible for rendering and displaying the ads. Specifically:

  • Inject the ads into the organic feed or designated placement zone.
  • Maintain the order provided by GoWit — do not randomize.
  • Mark all ads as sponsored to comply with legal and UX standards.
  • Embed click and impression tracking URLs exactly as provided for accurate attribution.

4. Rendering Logic Ownership​

  • For most formats, GoWit does not return ready-to-render components — you control the visual layout and placement of the ads.
  • Product-based formats should resemble native product listings (unless specified otherwise).
  • Display or video formats should use the supplied creative links and metadata to render your own components.
  • Exception — HTML creatives: when an ad includes an html field, GoWit returns a complete, ready-to-render creative with click and impression tracking already embedded. Render the html as-is (e.g. inside an <iframe> or container) and do not add your own tracking. See Tracking Events → HTML Creatives for the embedded-tracking details.

5. Consistency Across Ad Formats​

Each ad format’s integration guide should reiterate:

  • GoWit provides ranked ad data and tracking URLs.
  • You handle all UI rendering, placement, and sponsorship labeling.
  • Tracking URLs must be embedded as-is.

6. Initial Setup for Delivery​

Before sending real ad traffic, partners must complete or simulate these preparation steps to avoid integration blockers.

Staging Access​

  • Ensure access to the staging environment, including API credentials and dashboards.

Ad Placement Creation​

  • Define where ads will appear:
    • Homepage banners
    • Search pages
    • PDPs (Product Detail Pages)
  • Ad Placements are the core bridge between GoWit and the partner platform.
  • Each request must include the corresponding placement_id.
  • The placement_id dictates:
    • Eligible ad formats
    • Creative layout rules (size, dimensions)
    • Minimum CPC
    • Targeting constraints
  • Without a valid, preconfigured placement_id, ad requests return no ads.

Campaign Creation & Budgeting​

  • Create dummy or test campaigns under valid advertisers with products already uploaded.
  • Campaigns must be in an ACTIVE state.
  • Ensure budgets exist so the system returns ads during staging tests.