Webhook, conversion postback, and feed data model

Event and feed entity map

Start here when someone asks for a single “webhook + postback + product feed data model.” Split the tables first; then wire APIs.

Postback vs catalogue delta (do not merge tables)

{
  "webhook_version": 1,
  "event": "affiliate.delta",
  "occurred_at": "2026-06-20T14:22:11.000Z",
  "provider": "cj_affiliate",
  "property_id": "12844",
  "networks": {
    "upserted": ["88341", "88342"],
    "inactivated": ["88101"]
  },
  "coupons": {
    "upserted": ["1849201", "1849202", "1849203"],
    "inactivated": ["1840001"]
  },
  "truncated": false
}

{
  "event": "conversion",
  "click_id": "clk_8f2a1c",
  "order_id": "ORD-100294",
  "order_value": 149.00,
  "currency": "USD",
  "commission": 12.45,
  "status": "pending",
  "sub_id": "pub_campaign_42",
  "occurred_at": "2026-09-14T16:02:11.000Z"
}

Conversion postback field checklist

Exact parameter names differ by network (CJ, Awin, Impact, Admitad, Takeads, and peers). Normalize into your own columns once at the tracker edge.

affiliate.delta field checklist

Catalogue deltas never carry order value or commission. They tell you which firm and coupon ids to refresh from the REST API.

Architecture deep dive: webhooks & delta sync.

Ownership matrix

Ambiguous ownership is the usual reason teams merge postback and delta tables. Assign each surface explicitly.

Worker sketch: keep handlers separate

Two entrypoints, two persistence paths. Share logging and alerting, not a single polymorphic events table unless you add a hard event_family discriminator and never mix write paths.

async function handleAffiliateDelta(payload) {
  // 1. Verify HMAC signature before this function runs
  for (const networkId of payload.networks.upserted) {
    await upsertNetworkFromApi(networkId);
  }
  for (const couponId of payload.coupons.upserted) {
    await upsertCouponFromApi(couponId);
  }
  for (const couponId of payload.coupons.inactivated) {
    await markCouponInactive(couponId);
  }
  if (payload.truncated) {
    await paginateProviderDelta(payload.provider, payload.property_id);
  }
  await bustCacheTags(payload.provider);
}

async function handleConversionPostback(payload) {
  // Separate table from catalogue deltas
  await upsertConversion({
    clickId: payload.click_id,
    orderId: payload.order_id,
    status: payload.status,
    commission: payload.commission,
  });
}

Product feeds and creative assets in the same stack

Product feed and creative library rows are not conversion events. SKUs belong next to Firm/Coupon catalogue tables; banner assets stay in the network creative library. Price changes and new banners are almost never delivered inside a conversion postback.

• Refresh SKUs via Product Data API after catalogue sync or on a poll cadence.
• Pull banner sizes and creatives from the network UI/API; see product feed, SKU deep links & banner sizes.
• Use the full platform entity map when you need payout and tracking tables too.

Anti-patterns to avoid

• Writing commission rows into the same table as firm/coupon upserts from affiliate.delta
• Treating truncated: true as success without a follow-up list pull
• Skipping HMAC verification because the endpoint is behind a VPN
• Expecting product price changes or banner uploads inside conversion postbacks
• Deleting historical conversions when status flips from pending to rejected

Implementation next steps

1. Wire HMAC-verified workers for delta sync; keep a daily reconcile job.
2. Keep postback endpoints on your tracker; do not expect commission payloads from Feedico.
3. Poll or webhook-trigger product and coupon list pulls for catalogue freshness (warehouse ETL guide).
4. Confirm webhook and product feed entitlements on pricing.