Postback Not Firing: A Debug Checklist for Missing Nutra Conversions

How do you tell if the postback never fired or the click ID never arrived?

A missing conversion has two separate failure points, and confusing them wastes hours chasing the wrong log. Pull the tracker's raw click record for that visitor first. If a click row exists with a stored clickid, the postback stage is where you look next; if no click row exists at all, the clickid was lost upstream, before checkout ever happened.

The fastest split runs on what the tracker actually holds, not on what the offer page promises. Match what you see against the table below before opening a support ticket with the network.

Which macro mistakes silently break ClickBank, BuyGoods, and MaxWeb postbacks?

Macro mistakes break more nutra postbacks than actual network outages do, and almost all of them are invisible until you inspect the raw query string. ClickBank, BuyGoods, and MaxWeb each expect their own literal token names in the postback URL, and pasting a generic clickid placeholder instead of the network's actual macro syntax produces a URL that fires correctly but carries no usable data.

Test every macro against a live test transaction before pushing the offer live, not after the first missing conversion shows up on payout day. A five-minute dummy purchase catches a mistyped token that a week of live traffic will not.

• Leaving a generic placeholder token in the URL instead of the network's actual macro name, so the request fires but the payload is empty
• Case mismatch between a tracker's macro and a network's expected parameter, since some platforms read the query string as case sensitive even when the macro name itself is not
• Double URL-encoding a parameter so the receiving side reads a broken string instead of the original clickid
• Copying a sandbox or staging postback URL into the live offer, still pointing at a test domain
• Swapping affiliate ID and offer ID when a network's payload uses positional values instead of named macros

Where does the clickid get lost in an advertorial-to-VSL-to-checkout chain?

The clickid usually disappears at the handoff between pages, not inside any single page. An advertorial passes it to the VSL player as a URL parameter, the VSL player's checkout button must re-append it to the outbound link, and if that player strips query strings on its own redirect, the parameter never reaches the offer at all.

VSL players such as VTurb typically require the click-through button's destination URL to be configured with the incoming query string appended manually, since the player does not always carry it forward automatically depending on the embed mode. That configuration step, buried in a button setting rather than a raw HTML link, is a common silent break point that never throws an error.

If you built the funnel by following a structured build process rather than assembling pages ad hoc, this exact handoff is worth re-testing before launch, as covered in the 21-step campaign checklist. Pull the final checkout URL from a real click-through, not a bookmarked test link, and confirm the clickid string appears intact in the address bar the moment before payment submits.

How do you test a postback URL manually before blaming the network?

Test a postback URL by firing it yourself with dummy values before assuming the network or your tracker is broken. Take the exact postback URL from your tracker's setup panel, manually replace each macro with realistic test values in a browser address bar or a curl request, and send it. A correctly configured listener returns a 200 status and logs a new conversion row within seconds.

Repeat the same test using a clickid pulled from an actual click, not a fabricated one, since some trackers reject an outbound postback silently if the clickid does not match an open click record from the last several hours. Set up continuous monitoring on the receiving endpoint rather than testing once and walking away. UptimeRobot's free tier covers 50 monitors at a 5-minute check interval, enough to watch every active offer's postback listener and catch downtime before a payout cycle closes.

Why do conversions land under the wrong campaign or as 'unknown'?

Conversions land under the wrong campaign, or as unknown, when the postback carries a subid the tracker cannot map back to a specific click, usually because a static link replaced the dynamic macro somewhere in the chain. A landing page bookmarked before its tracking parameters were added, an email link pasted from an old campaign, or a QR code baked before launch all produce clean traffic with no attribution string attached.

Server-side forwarding setups create a second version of the same problem. RedTrack's free Relay tier, for instance, forwards conversion events to platforms like Meta's Conversions API but includes no dashboard and no attribution reporting of its own, so a conversion can be delivered successfully and still show as unmatched inside your primary tracker if you rely on Relay as the sole postback path rather than pairing it with a full tracking setup.

Do upsells and rebills fire separate postbacks — and is your tracker counting them twice?

Yes, upsells and rebills almost always fire their own postback, separate from the initial sale, and whether your tracker double-counts them depends on how you configured the payout event. Most nutra networks distinguish sale types with an event or transaction-type parameter — initial, upsell, rebill, refund — and a tracker that treats every inbound postback as an identical conversion event will inflate both revenue and payout totals unless each type gets mapped separately.

Rebill postbacks are also where data retention becomes a real constraint, not a theoretical one. Voluum's entry Profit plan retains click data for 6 months, which comfortably covers most continuity cycles, but a rebill firing after that window closes has nothing left to match against, and the conversion lands unattributed even though the postback itself worked correctly. A self-hosted tracker like Binom, by contrast, keeps click data indefinitely on its own license, which removes that failure mode entirely at the cost of running your own server.

When is the discrepancy actually network shaving, and how do you prove it?

Most of what gets called network shaving is not shaving at all — it is unresolved clickid loss somewhere upstream, and the checklist above accounts for far more missing conversions than deliberate underreporting ever does. Real shaving exists and networks have been caught doing it, but the number of technical failure points between an advertorial click and a checkout postback is large enough that most discrepancies resolve to a macro, a redirect, or a server issue once someone actually checks.

Proving the difference requires comparing two independent logs, not trusting either one alone. Pull your tracker's raw postback receipt log, with timestamps, clickids, and payout amounts as delivered, and set it against the network's own reporting dashboard or API for the same date range. A consistent, unexplained gap that persists after every macro and redirect check above comes back clean is the actual signature of shaving, not a single day's mismatch.

Self-hosted trackers add a failure mode that looks identical to shaving from the outside: an under-provisioned server dropping postbacks silently under load. Keitaro's own installation documentation recommends at least 4GB of RAM and 2 CPU cores for under 100,000 clicks/day, scaling to 16GB and 4 cores between 500,000 and 1,000,000 clicks/day. A tracker running past its sized capacity can queue or drop inbound postbacks during traffic spikes, producing a discrepancy pattern that is easy to misdiagnose as the network holding back money it already reported.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Ad spy comparison hub, Daily Intel vs Dropispy, Daily Intel vs Foreplay, Best Affiliate Tool Stack Under $50/Month, Best Affiliate Tool Stack Under $100/Month, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.