My sales suddenly stopped being tracked

Tracking that worked and then stopped dead is almost always a webhook signing secret that no longer matches. Your payment provider is still sending events and LinkJolt is still receiving them, but every one fails its security check and is rejected before any sale is recorded.

How to recognise it

Signature failures are all or nothing, which is what makes this easy to tell apart from an attribution problem.

• Conversions stop on a date. Not fewer, none.
• Clicks keep recording. Links and the tracking script are unaffected, only the sale path is broken.
• Your provider's dashboard shows failed deliveries to LinkJolt, returning 400 or 401.
• On the Stripe step of the Integration Hub you may see a warning that your webhook stopped receiving events.

The usual triggers are rolling the secret, deleting and recreating the endpoint (a new endpoint gets a new secret), switching provider account, or deleting the saved secret inside LinkJolt. If some sales record and others do not, this is not your problem, read "Why is an affiliate conversion not showing up?" instead.

Every rejected event is refused before anything is written, so each sale that completes while the secret is wrong is a commission your affiliate never gets credited for.

How to fix it

1. Open your payment provider dashboard and find the webhook endpoint pointing at LinkJolt.
2. Copy the current signing secret. In Stripe it starts with whsec_. In Paddle it is the endpoint secret key, starting with pdl_ntfset_.
3. In LinkJolt go to Settings, Payment Providers, click Create Webhook Secret, pick that provider and paste the value in.
4. Make a small real purchase and confirm it appears in your dashboard.

Saving replaces the previous secret for that provider automatically, so there is nothing to delete first. Account owners can copy the stored secret from the row's copy button and compare it against the provider's value before re-pasting. Saving needs the account owner or a team member with payout permission.

Gumroad is the exception: it does not issue a signing secret, so you create one in LinkJolt and it becomes part of your Ping URL.

The shorter fix on Stripe

If the Stripe step of the Integration Hub offers "Fix it with Stripe", take it. Connecting your Stripe account sends events to LinkJolt directly, with no endpoint to maintain and no secret to paste, so this failure cannot recur. Revoking that connection in Stripe stops tracking again.

If it still does not record

• Check the endpoint URL still matches the one shown in your Integration Hub for that provider. Yours is specific to your brand.
• Stripe keeps separate webhook lists for live and test mode. Real purchases only reach an endpoint added in live mode.
• On Gumroad the Ping URL contains a token derived from your secret. After saving a new secret, copy the new Ping URL out of Settings, Payment Providers and paste it back into Gumroad, or pings keep failing.

We watch for this too

For Stripe, Paddle and Gumroad, a daily check looks for sustained rejections with no successfully verified events in the same period, then emails the account owner and posts a dashboard alert unless you have System updates notifications switched off. It repeats at most once every three days. If any events are still verifying, for example because a second healthy endpoint exists, no alert is sent. Lemon Squeezy and GoPay reject unverifiable events the same way but are not covered, so watch those yourself. Polar is covered, and there is no secret for you to save, because Polar hands LinkJolt the signing secret when you connect. If Polar's events start failing the check, or its webhook is deleted or keeps being switched off, we email the account owner, and Reconnect on the Polar tab under Integrations fixes it.

Fixing the secret does not recreate the sales rejected while it was wrong. Some providers retry recent failed deliveries, so check the delivery log after the fix, then ask support about a backfill with the order ids and the date tracking stopped.