Product feed, SKU deep links, and creative banner sizes

Feed, deep link, and creative entity map

Use this map when designing CMS foreign keys or warehouse star schemas. The Feedico column shows what the catalogue API normalizes today.

SKU field checklist

Minimum viable product feed for deal grids, search indexes, and agent tooling. Optional fields still matter for geo filters and sale merchandising.

SKU catalogue and deep linking

A product feed row is a sellable item identity, not a promo code. Deep linking means the destination URL resolves to that SKU’s product page (or a mapped category) after tracking wrap. Keep click/subid parameters on the tracking layer; keep SKU identity on the catalogue layer.

Coupon offerUrl values are promotion-scoped tracked links. They may land on a homepage, category, or campaign URL. Do not assume every coupon URL is a valid SKU deep link for every product in that merchant’s catalogue.

{
  "id": "prod_9f8e7d6c5b4a3210",
  "firmName": "Example Outdoor Co",
  "provider": "cj_affiliate",
  "title": "30m climbing rope",
  "brand": "ExampleBrand",
  "sku": "SKU-ROPE-30",
  "price": 129.0,
  "salePrice": 99.0,
  "currency": "USD",
  "availability": "in stock",
  "countries": ["US", "CA"],
  "merchantUrl": "https://www.example-outdoor.com",
  "images": ["https://cdn.example/rope.jpg"]
}

Implementation: Product Data API · Product Deal Feed API · schema normalization.

Deep-link wrap flow

Publishers usually receive either a resolved product URL or a template with placeholders. The tracking wrap is network-specific (Impact subId1, CJ sid, Awin clickref, Admitad subid4, and peers). Attribution still keys off the click event, not the SKU primary key.

# Conceptual deep-link wrap (publisher side)
1. Feed row provides product destination (PDP or mapped category URL)
2. Publisher wraps with network tracking + sub_id / clickref / sid
3. Click lands on PDP after network redirect chain
4. Conversion postback (if any) keys off click_id — not SKU id

# Do not
- Treat promo code offerUrl as a SKU deep link
- Store banner binaries inside the product feed table
- Expect creative width/height on /me/products responses

For hop tagging and Managed Partner click match, see partner attribution docs and the webhook & postback data model.

Creative library: common banner sizes

Creative libraries ship display assets sized for ad slots. They are marketing creatives, not SKU rows. Pull width/height, asset URL, and default landing from the network creative API or publisher UI. Many programmes also expose text links and HTML widgets alongside fixed banners.

Feedico does not store banner binaries. Use network creative tools for assets; use Feedico for merchants, coupons, and optional product feeds.

Example creative asset shape (network-native)

Networks differ on field names, but the logical shape is stable. Keep this object in a creative_asset table keyed by programme, not inside Product.

{
  "creative_id": "bnr_728x90_spring",
  "type": "banner",
  "width": 728,
  "height": 90,
  "asset_url": "https://cdn.network.example/creatives/spring-728x90.jpg",
  "landing_url": "https://www.example-outdoor.com/spring",
  "language": "en",
  "programme_id": "4210991"
}

What to store where

• Catalogue API (Feedico): Firm, Coupon, optional Product SKU rows, list filters. Endpoints: /me/products, /catalog/products.
• Network creative UI/API: Banner sizes, HTML widgets, logo packs, seasonal creatives, language variants.
• Publisher CMS: Which size slots your templates accept, lazy-load rules, and brand compliance for logos.
• Tracker: Click ids, conversion postbacks, payouts. See the webhook & postback model.

Full platform entity checklist: affiliate platform data model.

Anti-patterns to avoid

• Joining banner creatives into the Product table by filename or campaign name
• Using coupon offerUrl as if it were a SKU deep link for every product click
• Hard-deleting SKUs on every sync miss (breaks historical deal pages)
• Expecting one global deep-link template across CJ, Awin, and Impact without provider branching
• Building SERP titles from raw keyword dumps instead of benefit-led product copy