Skip to main content

Integration Overview

Ad Format Integration Strategy​

Choosing where to start isn’t one-size-fits-all. Your optimal first format depends on which building blocks are ready today—catalog/advertiser data, placements, and the ad-serving path.

The goal is to get real signals flowing (requests, impressions, clicks, early conversions) while minimizing risk and rework. Use the conditional paths below to align scope with readiness, then expand in waves.

Why a Phased Approach​

  • Reduce moving parts: Validate placements and event plumbing on a simpler format before layering in creative-heavy or data-dependent ones.
  • Shorten the “time to first signal”: Start where you can ship fastest, then iterate toward your full surface map.
  • Keep teams unblocked: If one workstream (e.g., feed ingestion) stalls, progress with a neighboring track (e.g., display).

Pick Your Kick-off Move​

Launch Track A — Start with Sponsored Display​

(when the advertiser feed is unblocked but product feed has blockers)

When schema alignment, ingestion cadence, or QA on the product feed is slowing you down, kick off with display. You don’t need product sync to deliver banners, so you can stand up placements and test end-to-end delivery and tracking while catalog work continues.

Typical surfaces and examples:

  • Homepage hero/masthead (e.g., 728×90, 970×250)
  • Search results header band or mid-content banner
  • Category landing page billboard

Display can leverage the GoWit Display SDK to simplify rendering and visibility detection if you choose.

You’ll validate: placement wiring, request timing/latency, impression/click logging, and empty/204 handling—without waiting on catalog readiness.

Launch Track B — Start with Sponsored Product​

(when the product feed is unblocked)

If your product feed is ready, begin with product ads to exercise the full retail-media loop sooner (context → relevance → attribution).

Typical surfaces and examples:

  • Search results grid (inject sponsored items at defined positions)
  • Category/listing pages (inline native tiles within the product grid)
  • Product detail pages (complementary/related items modules)

For search/category:

  1. Fetch your organic results first.
  2. Then request ads with placement_id, session context, and a concise list of currently visible product IDs (optionally category).

This doesn’t mean we’ll advertise those same products; it provides page context so GoWit can return the most relevant sponsored units.

Responses for Sponsored Product include:

  • product_id
  • advertiser_id
  • ad_id (for tracking)

👉 Preserve order and render natively.

Launch Track C — Start with Off-site​

(when on-site ad serving is blocked but feeds are fine)

If advertiser and product feeds are healthy but front-end/back-end serving work is temporarily blocked, you can still advance by activating off-site inventory (e.g., Meta) as a parallel track.

This keeps momentum on creative and attribution while you finish on-site wiring. Treat it as an interim lane, not a replacement for on-site placements.

Expanding After the First Wave​

Once your initial format is stable (Display → add Product, Product → add Display or Off-site → add Display), layer in Sponsored Video last.

  • Video typically involves a heavier creative lift and player/viewability nuances, so it benefits from a mature request/measurement pipeline.
  • For hybrid formats (e.g., Display with Products), introduce them once both primitives are proven.

Operational Tips (Apply to Every Path in On-Site)​

  • Mirror production surfaces in staging: define placement IDs per page type/slot and test with real navigation flows.
  • Maintain response order: inject ads exactly as ranked; clearly mark “Sponsored.”
  • Handle “no ad” gracefully: collapse or apply a simple fallback without layout jitter; expect 204 responses when no inventory matches.
  • Set an ad request timeout of 100-150 ms. If elapsed with no response, stop waiting and continue rendering the page.
  • Keep event logging consistent:
    • Impressions on render
    • Clicks on interaction
    • Send all sales so GoWit can attribute across post-click/post-view windows (direct and indirect).