What payment models are available?

Recurring payments (fixed monthly fee), prepaid (term agreement with price guarantee), installments (use today, pay later in 4 instalments), and variable fees (access + variable fee based on usage).

Can I support different payment intervals?

Yes. Define daily, weekly, monthly and custom cycles. Combine intervals within a single product.

Does Zevio support variable invoice amounts?

Yes. Ideal for consumption-based billing such as utilities. Automatic collection after invoice issuance.

Do I need my own mobile app?

No. Use Zevio via QR, email or website. Zevio app handles the wallet. API/SDK available.

Does the user have full control over subscriptions?

Yes. Users see all cycles/history and can pause/resume instantly.

Can I test the system before going live?

Yes. Full access to test environment with API documentation.

Conversion tracking

Conversion tracking connects Zevio hosted checkout with the tools you already use to measure campaigns and sales: Google Tag Manager, Google Analytics 4, and Meta (Pixel and Conversions API). When a customer opens a payment page, starts paying, completes a purchase, or leaves without paying, Zevio can send the matching ecommerce signals so your ads and analytics stay aligned with what actually happened in checkout.

Events follow the usual ecommerce language used by Google and Meta (view_item, begin_checkout, add_payment_info, purchase). You configure everything once for the organization; it then applies to payment links, QR payments, and checkout sessions for that organization.

What you get

Measurement of the full checkout journey on Zevio payment pages.
Browser tags on checkout and success screens when you enable them.
Server-side delivery to Meta and GA4 when you add the matching secrets - useful when the customer is redirected away from Zevio after payment.
Cookie choice before analytics tags load.
One journey identifier shared between browser and server so Meta can treat Pixel and Conversions API as the same conversion, not two.

Availability

Conversion tracking is available on Premium, Enterprise, and Trial. Organization owners and admins configure it under Settings → Organization. On lower plans the controls stay locked until you upgrade.

How the journey is measured

Zevio mirrors a classic ecommerce funnel on the hosted payment experience:

The customer opens the payment page - Zevio records that the offer was viewed and checkout began.
The customer confirms payment - Zevio records that payment details were submitted.
The payment succeeds - Zevio records a purchase with amount, currency, and payment id.
The customer leaves without paying, or a checkout session expires - Zevio can record an abandoned checkout.

Browser and server together

Tags in the browser cover the experience the customer sees on Zevio. Server delivery covers the same commercial moments when the browser cannot - for example after an external success URL, or when a tag is blocked. You can use browser only, server only, or both; both is the most complete setup for ads.

Relationship to webhooks

Webhooks remain the channel for your backend integration (payment.success, payment.pending, and related events). Conversion tracking is the channel for Google and Meta. Keep webhook names in your API handlers, and ecommerce event names in GTM, GA4, and Meta.

In this section

[Setup](/docs/conversion-tracking/setup) - how to turn tracking on and fill in Google and Meta fields.
[Events](/docs/conversion-tracking/events) - every event, when it fires, and what data it carries.
[Google Tag Manager and GA4](/docs/conversion-tracking/gtm-ga4) - how to receive events in Google.
[Meta Pixel and Conversions API](/docs/conversion-tracking/meta) - how to receive events in Meta.
[Cookie choice and reliability](/docs/conversion-tracking/reliability) - cookie notice, abandoned checkout, go-live checklist, and common issues.