Affiliate platform data model: entity map and ERD

Full affiliate platform entity map

Use this table when you need a full affiliate platform entity checklist: webhooks, product feeds, tracking links, payouts, and creative libraries. The Feedico column shows what this API normalizes for catalogue and sync workloads.

Feedico entity catalog

These are the platform entities exposed (directly or indirectly) through customer APIs and dashboard integrations. Internal admin tables are omitted. This is the publisher-facing ontology for the catalogue layer highlighted in the entity map above.

Relationships & entity diagram (ERD)

An Account owns many Integrations (one per connected network). Each Integration writes Firms and Coupons into tenant-scoped tables during sync. Coupons always reference a parent Firm via networkId. Product rows and Product lists are optional when catalog feeds are enabled. Webhook subscriptions emit delta events when eligible plans expose them.

erDiagram
  ACCOUNT ||--o{ INTEGRATION : owns
  INTEGRATION }o--|| PROVIDER : connects
  INTEGRATION ||--o{ FIRM : syncs
  FIRM ||--o{ COUPON : exposes
  FIRM ||--o{ PRODUCT : optional
  INTEGRATION ||--o{ WEBHOOK_DELIVERY : emits
  ACCOUNT {
    string appUserId
  }
  FIRM {
    string provider
    string externalMerchantKey
  }
  COUPON {
    string networkId
    string externalCouponId
    string code
  }

Firm & coupon JSON shapes

Customer list endpoints return these normalized objects regardless of upstream network. Field-by-field CJ / Awin / Impact mapping lives in the schema normalization deep dive.

{
  "id": "88341",
  "displayName": "Example Retailer EU",
  "provider": "awin_affiliate",
  "externalMerchantKey": "12345",
  "merchantWebsiteUrl": "https://example-retailer.eu",
  "status": "active",
  "couponCount": 12,
  "lastSyncedAt": "2026-08-10T18:04:00.000Z",
  "extra": { /* upstream programme fields */ }
}

{
  "id": "1849201",
  "networkId": "88341",
  "networkName": "Example Retailer EU",
  "provider": "awin_affiliate",
  "externalMerchantKey": "12345",
  "externalCouponId": "promo-998877",
  "code": "SPRING15",
  "title": "15% off sitewide",
  "startsAt": "2026-03-01T00:00:00.000Z",
  "endsAt": "2026-06-30T23:59:59.000Z",
  "offerUrl": "https://…/tracked-offer",
  "status": "active",
  "extra": { /* voucher type, region flags, native enums */ }
}

Frequently asked questions

What entities does an affiliate marketing network platform need?

A full-stack affiliate platform spans catalogue rows (merchants, coupons, product feeds), event surfaces (webhooks, conversion postbacks, tracking links), finance (payouts), and creative assets (banners). Use the platform entity map on this page for the complete checklist. Feedico implements the catalogue aggregation slice: Account, Integration, Provider, Firm, Coupon, optional Product rows, Sync snapshots, and Webhook deliveries.

What is the affiliate marketing webhook, conversion postback, and product feed data model?

Industry trackers model Webhook/postback as inbound conversion events tied to click ids; product feeds as SKU catalogs with deep links; creative assets as banner libraries. Feedico models outbound affiliate.delta webhooks when catalogue rows change, optional Product feed rows from CJ and peers, and does not store inbound conversion postbacks (those stay in your tracker or network reporting). See the webhook/postback and product feed sections on this page.

How are affiliate tracking links, conversions, and payouts modeled?

Click-tracking platforms use Click (immutable event), Conversion (commission trigger), and Payout/settlement ledger tables. Affiliate networks expose similar reporting APIs. Feedico does not duplicate those ledgers: it supplies normalized Firm and Coupon catalogue rows so your tracker or storefront can attach tracking links and postbacks separately.

How do Firm and Coupon relate in Feedico's schema?

Every Coupon references a Firm via networkId (the internal firm row id). Firms deduplicate on (provider, externalMerchantKey); coupons on (provider, externalCouponId). One firm can expose many coupons; coupons inherit networkName and merchant context from the parent firm row.

Is this the same as an affiliate tracking data model?

No. Generic affiliate tracker schemas center on referral links, click ids, conversion postbacks, and payout batches. Feedico is a multi-network aggregation layer: sync upstream programme and promotion catalogues, normalize field names, and expose one REST contract. Your product still owns attribution and checkout if you run a tracker separately.

Where do network-native fields live?

Top-level customer API fields are stable camelCase (provider, externalMerchantKey, code, startsAt, etc.). Upstream-only enums, regional flags, and vendor-specific metadata are preserved in an extra JSON object on each row so warehouses can promote fields later without re-syncing history.

What are the primary keys for warehouse upserts?

Use composite natural keys: (provider, externalMerchantKey) for firms and (provider, externalCouponId) for coupons, scoped to your tenant. Feedico id is a stable internal numeric string for CMS foreign keys; external keys track upstream identity across sync runs.

Where should I read field-by-field CJ/Awin/Impact mapping?

This page is the platform entity overview. For per-network column mapping, provider tags, pagination normalization, and the extra JSON escape hatch, read the schema normalization deep dive linked below.