Estimate usage from the whole journey
Billing counts tracked visits, offer clicks, and custom events. It is broader than the Conversions metric in reports, which depends on which events your goals mark as conversions. For example, a journey with one recorded visit, one offer click, and two recorded custom events contributes four events to usage, even if only the final custom event is a conversion. Outgoing postback attempts and failed-event records are not added as separate billable events by the current usage calculation. The usage display is processed asynchronously. Compare it against the billing period shown on Subscription, rather than expecting an arbitrary campaign date filter or a live request count to match immediately. For metered paid subscriptions, usage above the included allowance is billed in the next Stripe invoice cycle. The Free plan uses an allowance with delayed limit enforcement rather than metered overage. Check the live plan’s terms when deciding whether a traffic increase fits your current plan.Choose the timing of a plan change
An upgrade can create a prorated Stripe charge for the remaining period. If the tracker says payment confirmation is pending, the new access has not yet been confirmed. Check the payment status and wait for the plan shown in Subscription to update.
For a practical example, if you need public API access for tomorrow’s export, complete an eligible plan upgrade and verify the displayed plan before creating the key. Scheduling a downgrade for next renewal serves a different purpose and will not change today’s limits.