Features
Configure your segment key for attribution, set threshold alerts on any metric, monitor attribution health, and check your backend sync status.
A segment key is a metadata field name that you attach to every Stripe charge or payment intent. LeakGuard reads this field to group costs by segment — for example, by pricing plan, team, product line, or region.
How to add metadata to charges
// Node.js / Stripe SDK example
const paymentIntent = await stripe.paymentIntents.create({
amount: 2000,
currency: 'usd',
metadata: {
plan: 'enterprise', // your segment key
region: 'EMEA', // optional additional keys
team_id: 'team_abc123', // any string value works
},
});Set the segment key in Settings
Navigate to Settings → App Configuration. Enter the metadata key name you want LeakGuard to use (e.g. "plan"). This applies globally — all views will break down by this key.
Check coverage
After setting the key, the Attribution Health card shows what percentage of your charges have this key. Low coverage means some charges won't appear in segment breakdowns.
Coverage updates
Coverage is calculated against the selected date range. New charges with the key start contributing to coverage immediately after the next sync.
Threshold alerts notify you when a metric crosses a configured limit. LeakGuard evaluates your configured alerts against the latest aggregated data:
Alert event types
Threshold exceeded
A metric (Refund Rate, Effective Rate, Dispute Rate, Win Rate) crosses a value you set. Example: alert when Refund Rate exceeds 1.5%.
Anomaly detected
A metric moves more than two standard deviations from its recent baseline — even if it hasn't crossed a specific threshold.
High-impact driver
A single segment, country, or payment method accounts for more than a configurable share of your total cost.
Alert frequency
Daily
Evaluated every day at 7 AM UTC. Best for high-velocity metrics like dispute rate.
Weekly
Evaluated every Monday. Good for slower-moving trends like segment drift.
Monthly
Evaluated on the 1st of each month. Useful for close-month threshold monitoring.
The Attribution Health FocusView (accessible from Settings) shows a detailed breakdown of which charge sources are contributing to your unattributed bucket:
Unattributed sources table
Ranked list of charge creation contexts that are missing your segment metadata key. Each row shows source identifier, charge count, volume, and % of total unattributed.
How-to-fix guidance
For each unattributed source, LeakGuard shows the Stripe API endpoint (payment_intents, charges) and links to the Stripe documentation for adding metadata to that object type.
Coverage trend
A sparkline showing attribution coverage over the last 30 days. Improving coverage after adding metadata is visible here.
The Cache Status bar (visible in the dashboard header) shows whether LeakGuard's backend data is current and how your data is being served:
Connected
Backend data is available and within the SLA for your date range. All metrics are served from pre-computed aggregates. This is the normal state.
Unavailable
The backend API is unreachable or data coverage is below the 95% threshold. Metrics are served from the Stripe API directly (fallback mode) — may be slower and limited to shorter date ranges.