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 setup

Open Settings → Organization and scroll to Conversion tracking. Settings apply to the selected organization and its hosted checkout.

Before you start

Use a Premium, Enterprise, or Trial organization.
Sign in as owner or organization admin.
Prepare at least one destination: a GTM container, a GA4 property, and/or a Meta Pixel.
Checkout always asks for a cookie choice before analytics tags load.

Enable conversion tracking

Turn on Enable conversion tracking. Until this switch is on, checkout does not load your tags and Zevio does not send server-side conversion events for the organization, even if IDs are saved.

Cookie choice

When conversion tracking is enabled, checkout always shows a compact cookie notice before Google or Meta tags load. Continue allows analytics cookies for that visit. Necessary only keeps payment working without analytics tags. The choice is remembered for the browser session.

Google Tag Manager

Enter your GTM container ID (for example GTM-XXXXXXX). Zevio loads that container on checkout after the visitor continues. Build your GA4 and Meta tags inside GTM so they listen for the ecommerce events documented in [Events](/docs/conversion-tracking/events).

Google Analytics 4

Enter your GA4 measurement ID (for example G-XXXXXXXXXX).

If GTM is empty, Zevio can load GA4 directly on checkout.
If GTM is filled in, Zevio loads GTM only in the browser - configure GA4 inside the container.
The same measurement ID is used with the Measurement Protocol API secret for server-side GA4 events.

GA4 Measurement Protocol API secret

Create an API secret in GA4 for your data stream and paste it here. Zevio stores it write-only: the panel shows whether a secret is configured, not the secret itself. Leave the field blank to keep the current value; clear it and save to remove it. Without this secret, browser GA4 still works, but server-side GA4 events do not.

Meta Pixel

Enter your Meta Pixel ID so Zevio can load the Pixel on checkout and send standard Meta events from the browser.

Meta Conversions API

Access token - write-only, same keep / clear behaviour as the GA4 secret. Required together with the Pixel ID for server-side Meta events.
Test event code - optional. While testing, server events can appear under Meta Test Events.

Suggested production setup

Use GTM as the browser layer and map its triggers to the Zevio ecommerce events.
Add the GA4 API secret and Meta Conversions API token so purchase and payment-start still reach Google and Meta when the customer leaves Zevio immediately after paying.
Enable tracking, then run a real test payment.
Confirm the journey in GTM Preview, GA4 realtime or DebugView, and Meta Events Manager / Test Events.