CJ Affiliate
CJ programme & coupon data - without owning the whole CJ client stack
Teams searching CJ API usually want offers, merchants, or links in product - not another bespoke OAuth + schema project. Feedico is not CJ; we are a normalization layer. Connect CJ Affiliate in the dashboard, then read firms and coupons through the same coupon API-style lists you use for Awin or Impact. Broader framing: affiliate network API, unified affiliate API.
Also unify
Who is this for?
Teams that monetize through CJ Affiliate and need the same engineering pattern as other affiliate sources.
How data flows
What you get with Feedico
Same list endpoints as every other source
Pagination and POST filters behave like your Awin or Impact jobs - no CJ-special case in your router.
Provider-aware rows
Filter by provider when a feature slice should only show CJ-derived coupons.
Less schema archaeology
Upstream field churn is mapped inside Feedico instead of scattered across your services.
Room for a native escape hatch
Keep CJ-first-party APIs for edge workflows; consume Feedico where multi-network UX wins.
About CJ Affiliate
CJ (often referred to historically as Commission Junction) is one of the best-known global affiliate networks, connecting advertisers and publishers across retail, services, and travel. It traces its roots to the late 1990s U.S. performance marketing market and today sits within the Publicis Groupe media ecosystem - see the vendor’s own “About” and publisher pages for current leadership, footprint, and programme policies. www.cj.com/. CJ Affiliate is independent third-party software; trademarks belong to their owner. We summarise public positioning only - confirm policies and programme rules on the vendor site.
What we don't promise
We don't bypass CJ enrollment, network rules, or commission reporting. Feedico surfaces data your connected integration syncs - always defer to CJ's publisher documentation for programme-specific obligations.
How it works
- 1
Connect CJ Affiliate
Add credentials in the dashboard - only for programmes you are approved on.
- 2
Sync & normalize
Feedico pulls upstream data and maps firms and coupons into shared list models.
- 3
Call one API
Same list endpoints, pagination, and POST filters as your other connected providers.
- 4
Ship product
Websites, apps, extensions, or pipelines - one consumer path for every network.
Example row shape
Illustrative JSON - your integration uses customer OpenAPI field names. provider identifies the source (cj_affiliate).
{
"provider": "cj_affiliate",
"networkName": "Nike US",
"merchant": "Nike",
"title": "15% off your order",
"code": "SAVE15",
"offerUrl": "https://…"
}Native integration vs Feedico
| Topic | Via Feedico | One-off native client |
|---|---|---|
| Schema alongside other networks | ✅ Shared | ❌ Fork per vendor |
| Auth & secrets in your app | ✅ One Feedico token | ⚠️ Many token flows |
| Schema drift from vendor updates | Absorbed in mapping | ❌ Your on-call |
| When native API is still right | - | ✅ Exclusive fields / edge workflows |
Why pair CJ Affiliate with a unified layer?
Most growth teams do not stop at one flagship programme source. When CJ Affiliate is one leg of a multi-network roadmap, maintaining parallel DTOs burns velocity. Feedico lets you keep the relationships that matter while consolidating what your product consumes day to day.
Frequently asked questions
- Is Feedico the same company as CJ Affiliate?
- No. CJ Affiliate (Commission Junction) is an independent affiliate network. Feedico is a separate integration product: you connect your CJ credentials in our dashboard, and your application reads normalized rows through Feedico's API.
- Do I still need CJ programme approval?
- Yes. Feedico does not bypass CJ enrollment or publisher policies. You must be approved for the programmes you promote; we surface data from connections you legitimately authorize.
- Can I combine CJ with other networks in one codebase?
- Yes - that is the primary use case. Wire CJ alongside Awin, Impact, or other supported sources; filter by provider when a downstream system needs only CJ rows.
- When should I still use CJ's native APIs directly?
- When you need CJ-exclusive fields, deep reporting workflows, or account administration that only first-party endpoints expose. Feedico is optimized for multi-network catalogue and coupon consumption in your own product.
- How are API quotas handled?
- Successful Feedico list calls count against your plan quota (UTC calendar month). When exceeded, the API returns a documented error - design caching and backoff accordingly. See documentation and plan copy for caps.
You need programme approval and compliant use at each affiliate network. Feedico provides the integration layer - not a substitute for network terms.