Feedico
TradeTracker (favicon)

TradeTracker

TradeTracker affiliate data without a parallel integration stack

Publishers searching TradeTracker API often operate in Benelux and EU markets alongside global networks. Feedico lets you connect TradeTracker once, then consume coupon lists and merchant rows through the same endpoints as Impact or Admitad.

Also unify

Who is this for?

Teams that monetize through TradeTracker and need the same engineering pattern as other affiliate sources.

How data flows

What you get with Feedico

  • Unified pagination

    Same POST list routes as every other connected source.

  • Stable JSON fields

    Your app reads Feedico rows, not raw TradeTracker export quirks.

  • Provider filtering

    Segment TradeTracker coupons when compliance requires it.

  • Dashboard credentials

    Operators manage keys in one place alongside other networks.

Connecting TradeTracker: credentials, endpoints, and what syncs

Authentication: SOAP web service authentication with Customer ID + passphrase. Secrets are encrypted at rest and never returned by the API.

What you enter in the dashboard

Customer ID
Your TradeTracker customer ID.
API passphrase
Web services passphrase (not your login password); stored encrypted.
Affiliate site ID
Optional: limit sync to one of your sites.

TradeTracker APIs Feedico calls

SOAP affiliate service (soap-literal-wsi)
Campaigns and materials for your affiliate site.
How TradeTracker data maps to Feedico rows
TradeTracker objectFeedico row
CampaignFirm row, provider tradetracker
Voucher materialCoupon row
  • TradeTracker is SOAP-only; Feedico hides the XML envelopes so you read the same JSON as every other network.

About TradeTracker

TradeTracker is a performance marketing network with roots in the Netherlands, connecting advertisers and publishers across Europe. See tradetracker.com for programme policies and publisher documentation. www.tradetracker.com/. TradeTracker is independent third-party software; trademarks belong to their owner. We summarise public positioning only - confirm policies and programme rules on the vendor site.

How it works

  1. 1

    Connect TradeTracker

    Enter your Customer ID, API passphrase and Affiliate site ID in the dashboard - only for programmes you are approved on.

  2. 2

    Sync & normalize

    Feedico calls SOAP affiliate service (soap-literal-wsi), then maps campaign and voucher material into normalized firm and coupon rows.

  3. 3

    Call one API

    Same list endpoints, pagination, and POST filters as your other connected providers.

  4. 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 (tradetracker).

{
  "provider": "tradetracker",
  "networkName": "Example Shop NL",
  "merchant": "Example Shop",
  "title": "15% off your order",
  "code": "SAVE15",
  "offerUrl": "https://…"
}

Native integration vs Feedico

TradeTracker data: Feedico vs bespoke per-network client
TopicVia FeedicoOne-off native client
Schema alongside other networks✅ Shared❌ Fork per vendor
Auth & secrets in your app✅ One Feedico token⚠️ SOAP web service authentication with Customer ID + passphrase.
TradeTracker APIs to integrateHandled in the sync layer1 (SOAP affiliate service (soap-literal-wsi))
Schema drift from vendor updatesAbsorbed in mapping❌ Your on-call
When native API is still right - ✅ Exclusive fields / edge workflows

Why pair TradeTracker with a unified layer?

TradeTracker alone needs 3 credentials and its own auth scheme (SOAP web service authentication with Customer ID + passphrase). Most growth teams do not stop at one flagship programme source. When TradeTracker 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 TradeTracker?
No. TradeTracker is an independent affiliate network. Feedico normalizes data from connections you authorize in our dashboard.
Do I still need TradeTracker programme approval?
Yes. You must remain approved for advertisers you promote. Feedico surfaces synced data; it does not grant programme access.
Can TradeTracker rows mix with other networks?
Yes. Use provider filters when you need a TradeTracker-only slice, or blended lists for multi-network products.
When should I call TradeTracker APIs directly?
For TradeTracker-specific reporting or account administration. Use Feedico where multi-network coupon and merchant lists power your app.

Affiliate disclosure: some links on Feedico are affiliate links. We may earn a commission when you buy through them, at no extra cost to you. Publishers still need programme approval and compliant use at each affiliate network. Feedico provides the integration layer, not a substitute for network terms.

Related pages

Concept & comparisons