payment event at the moment a purchase is confirmed — so you can see, in the same dashboard where you track pageviews and sign-ups, exactly which source, campaign, or page is responsible for each transaction.
Recording a Payment Event
Calltinytrack() with the event name 'payment' and a properties object that describes the transaction. Fire this on your order confirmation page after a successful payment:
Recommended Properties for Payment Events
Use these standard property names to get the most out of TinyTrack’s Payments view. Consistent naming across all your payment events enables clean filtering and accurate revenue aggregation.
You can add any additional properties your business needs — TinyTrack accepts any key-value pairs alongside these recommended ones.
When to Fire the Payment Event
The right moment to fire the payment event depends on your checkout architecture:- Confirmation Page
- After Webhook Callback
Fire the event when your order confirmation or “thank you” page loads. This is the simplest approach and works for most storefronts and SaaS checkouts.
Viewing Payment Data in the Dashboard
Navigate to the Payments section of your TinyTrack dashboard to see:- Payment event count — the total number of payment events recorded in the selected date range, shown as a time-series chart.
- Revenue total — if you pass
amountandcurrency, TinyTrack aggregates total revenue and displays it alongside the event count. - Breakdown by source — see which traffic sources (organic, paid search, social, email, direct) are driving the most transactions.
- Breakdown by plan — if you pass a
planproperty, TinyTrack groups payments by plan name so you can see which tier is most popular. - Conversion path — combine the Payments view with the Goals & Funnels section to trace the full visitor journey from first pageview to completed purchase.