Internal
Runs entirely in your browser. Nothing you paste is sent, stored, or logged, paste live links freely.
Read one link end to end: every parameter explained in plain English, problems flagged red / amber / green, then fix the values inline and copy a clean rebuilt link.
Paste a URL
Put two links side by side to see exactly where they differ, the affiliate ID, tracking slots, and campaign params, so you can spot what changed between a working link and a broken one.
Link A
Link B
Audit a whole column of links at once: a green / red pass-fail table with the reason for each, plus bulk fixes and a CSV export. Good for checking a campaign's worth of links in one go.
Paste one link per line
Work with a tracker's postback (S2S) URL: Generate a ready-to-paste one per tracker with the right BuyGoods tokens, or Check an existing one against the tokens BuyGoods actually fills.
Paste a postback URL
Look up a Stripe, Braintree, or NMI decline code to see who fixes it and what to do, customer, their bank, BuyGoods tech, or a fraud signal to flag, plus the ready message for the HelpGrid agent. Paste several codes (comma or space separated) to triage a batch by who owns them.
Paste a decline code, or several
How to use
Read any BuyGoods link in one glance.
Paste a checkout, offer, or postback URL, Param Decoder explains what every parameter does, flags what's broken, and lets you fix and rebuild it. Nothing you paste leaves your browser.
Worked example, a live checkout link
The two jobs of every link
One BuyGoods link does two separate jobs from a single click. Telling them apart is the whole point of this tool.
A link can pay the affiliate yet never report back to their tracker, or track perfectly yet earn no commission. Different breakage, different fix. That's why a missing aff_id is an error, while an empty subid is only a heads-up.
The path tells a story too
BuyGoods VSL funnels encode the funnel in the URL path, before the ?. Param Decoder reads it so you don't have to decode it by hand:
Why not just a generic URL decoder?
A generic parser splits a query string and decodes %-encoding, useful, but blind to BuyGoods. This tool's edge is narrow and lives only here:
Knows BuyGoods. aff_id, the five subid slots, postback tokens, the funnel in the path, a generic tool sees none of it.
Validates, not just lists. It flags the broken thing, empty aff_id, a typo'd param name, in plain terms.
100% private. Online parsers POST your URL to their server; this runs entirely in your browser, so live customer links are safe to paste.
Hands you a ticket. Inspect → diagnosis → a copy-paste, ticket-ready report, fitted to a support flow.
The modes
Inspect
When you have one offer or checkout link
Read and repair one link. Every param is labelled in plain English; flags are red / amber / green; edit values inline, toggle params off, then copy a clean rebuilt link. Decodes Base64 redirects, reads the funnel from the path, catches typo'd param names, tolerates messy pasted input, checks against a saved QA template, and exports a ticket-ready diagnosis.
Compare
When you have two links to compare
Two links side by side, merged by param. Differences in aff_id and subid stand out the most, the fastest way to answer "why does one track and the other doesn't".
Batch
When you have a whole column of links
Paste a whole spreadsheet column of links, get a green/red pass-fail table back. Check a campaign's worth of links at once; jump into any row with one click.
Postback
When you have a tracker's postback URL
Check a tracker's postback URL against the tokens BuyGoods actually fills ({SUBID}…{SUBID5}, {ORDERID}, {COMMISSION_AMOUNT}…), and copy the exact template for Voluum, CPV Lab, or AnyTrack, each tracker's own param names, sourced from its docs.
Decline
When you have a decline code from a failed charge (from the transaction, not a URL)
Paste a Stripe, Braintree, or NMI code and get the part Google won't: who fixes it and what to do, customer, customer's bank, BuyGoods tech, or a fraud signal to flag to the AM, plus the ready message for the HelpGrid agent. Backed by ~190 codes from each processor's own docs, source cited.
What the flags mean
Reading a decline code
The code's meaning is a Google search away. What it doesn't give you is the decision: who fixes this, and what do I do? That's what Decline mode leads with, mapped to BuyGoods' three pillars, so a junior knows whether to coach the buyer, wait on the bank, escalate to tech, or flag an affiliate. You paste the code (from the transaction / backoffice / gateway response), not a link. (If a failure URL carries the code, e.g. ?decline_code=do_not_honor, Inspect explains it inline.)
✓ sourced The code definition is transcribed verbatim from Stripe, Braintree, or NMI's own docs (~190 codes), each result links its source. Soft vs hard and worth-a-retry are still shown as supporting detail.
Saved names , stored on this device only, never sent
QA templates , expected param sets per offer, this device only
Param notes , meanings you've captured, this device only