Tebex webhook events to enable#

When you create a Tebex webhook endpoint, Tebex lets you choose which event types to send.

Recommended events#

Enable these for the most complete revenue tracking:

• Payment Completed: records completed purchases.
• Payment Refunded: updates revenue when a purchase is refunded.
• Payment Dispute Opened: marks revenue that is under dispute.
• Payment Dispute Won: helps restore confidence in disputed revenue.
• Payment Dispute Lost: records chargeback impact.
• Payment Dispute Closed: closes the dispute lifecycle when Tebex sends that update.

Optional events#

Recurring payment events can be useful if your store sells subscriptions. If you enable them, make sure your team understands how Tebex represents renewals and cancellations.

Events you usually do not need#

Basket abandoned and basket authenticated events are usually not needed for revenue attribution. They can be useful for store behavior analysis, but they are not required for normal Joinometry revenue tracking.

After enabling events#

Make one test purchase and, if possible, test a refund in your sandbox or test environment. The Revenue page should update after Joinometry receives the event.