BuyGoods Webhook MCP Server

buygoods-webhook

BuyGoods fires server-side postback pixels when affiliate conversions land — purchases, refunds, frontend sales, and upsells. Each POST is one stored report; flat query-style parameters normalize to JSON in export.json. Tools read what already arrived — read-only, no way to fire postbacks or change payout state from here.

BuyGoods dynamic values (upstream tokens)

BuyGoods replaces these tokens with live values at conversion time. The keys in stored JSON are whatever parameter names were chosen when the postback URL was mapped (for example cid, payout, txid) — not necessarily the token names below. Read export.json keys from the latest delivery; use ## This connection notes when the user documented their mapping.

First moves

1. Latest report — default for the most recent conversion signal.
2. Inspect export.json — flat key/value fields from the postback body.
3. Recent reports — audit volume, duplicate order ids, or missing subids.
4. Stable ids — dedupe and reconcile on order/transaction id and whichever subid slot carries the click id (often SUBID or SUBID2 in upstream docs, but stored under the mapped param name).

Response shape

• export.json — parsed postback parameters (primary source for conversion fields).
• export.text — raw body when JSON parsing is unavailable.
• source.captured_at — when the postback landed here (not necessarily the upstream sale timestamp — check payload fields when present).

Operational order

1. Start with the latest report — do not guess a report id.
2. If captured_at is older than expected, say so — postbacks arrive when BuyGoods sends them.
3. List recent reports only for history, duplicate suspicion, or explicit compare-by-date asks.
4. Read ## This connection in the skill supplement for this user's param-name mapping (subid slot, payout key, order id key).

Gotchas

• Read-only — cannot trigger postbacks, approve conversions, or change affiliate settings from here.
• Mapped param names — BuyGoods tokens are uppercase in templates; stored keys follow the user's query names (subid, cid, amount, orderid, etc.).
• Subid slots — up to five subid fields; the click id must match between offer link and postback mapping or attribution breaks upstream (check which slot is populated in export.json).
• Funnel context — upsell rows may include CONV_TYPE, FLAG_UPSELL, or UPSELL_PARENT when those tokens were mapped; frontend vs upsell commission can differ.
• Retries — BuyGoods may resend when the ingest endpoint did not respond; compare ORDERID (or the mapped order-id key) and source.captured_at when deduping.
• Global vs offer postbacks — global pixels fire across affiliated offers; offer-specific pixels only pass that offer's conversions — history may mix both if multiple URLs were used.