PremiumCheckout Suite.

AcyMailing must be installed, active and have at least one active list. Newsletter consent is disabled by default.

1. Open Premium Checkout Suite – Settings – Newsletter.
2. Enable Newsletter consent.
3. Keep Newsletter provider on AcyMailing.
4. Under Newsletter list by shopper group, choose the list for each relevant VirtueMart shopper group.
5. Save and test with a customer in that group.

The unchecked consent appears only when the provider and a mapped active list are available. Subscription runs after order creation and only after explicit consent.

Verify the result inside AcyMailing. If the checkbox is missing, confirm that AcyMailing is active, the list is active and the current shopper group has a mapping.

Optional post-purchase account is enabled by default, while the customer checkbox remains unchecked.

1. Open Premium Checkout Suite – Settings – Account creation.
2. Enable Optional post-purchase account.
3. Set Successful order status to the native VirtueMart status that authorizes account creation. The default is C.
4. Place a guest order and opt in.
5. Move the order to the configured successful state if the payment flow does not do so automatically.

Joomla sends a secure password-setup link. No plaintext password is created or sent. If the email already belongs to an account, duplicate creation is safely skipped. An account-creation failure must not roll back or hide the native order.

Open Components – Premium Checkout Suite – Trust content and create a concise, accurate store assurance.

1. Enter a short Title and plain-language Body.
2. Choose the language.
3. Select shield, truck, refresh or headset, or choose a local image through Joomla Media Manager.
4. Select Checkout or Order completion placement.
5. Choose device visibility, optional link, ordering and publication state.
6. Save and inspect the relevant storefront page.

Custom images must be local Joomla Media files. External image URLs are rejected. Safe variables can use the values configured in Settings, including returns days, support phone, support hours and free shipping threshold.

Enable Locked checkout in General settings to use the distraction-free shell only on cart and checkout routes.

• Active template logo: uses the logo configured by the active Joomla template. If no file exists, the site title is used.
• Separate checkout logo: uses the local image selected in Checkout logo image.
• Locked checkout footer: accepts safe basic formatting and links. Leave it empty to render no footer.

The separate checkout logo takes effect only when that source is selected. Confirm the result at desktop and mobile sizes and ensure the logo remains readable.

Choose the analytics connection that your store uses. The default Internal event model only sends nothing to an external analytics service. Tracking never controls checkout or order success.

Connect Umami to checkout completion

The Umami connection sends an event named checkout_completed when an eligible order reaches the completion page. You do not need to write JavaScript to create this event.

What you need

• A working Umami website and tracker on your store.
• The same tracker loaded on the order confirmation or payment-return page, as well as cart and checkout.
• The exact analytics-consent cookie name and accepted value used by your store’s cookie banner, when consent is required.

Premium Checkout Suite does not install the Umami tracker. Set up the tracker separately before connecting it here.

What to select and enter

1. Open Components → Premium Checkout Suite → Settings.
2. Select Tracking. The panel is headed Consent-aware tracking.
3. Set Tracking adapter to Umami — checkout completion.
4. In Retail groups for the Umami funnel, select all shopper groups that belong to your retail audience. Include your store’s guest group if you want guest orders to count.
5. Keep Require analytics consent enabled when analytics consent is required for your store.
6. Enter the exact cookie name from your cookie banner in Analytics consent cookie.
7. Enter that banner’s exact accepted value in Granted cookie value.
8. Click Save.

Which shopper groups count?

An empty group selection sends no completion events. A customer who also belongs to any unselected group is excluded, even if they belong to a selected retail group.

For example, select your Guest and Retail groups and leave Wholesale unselected. A retail-only customer can qualify. A customer assigned to both Retail and Wholesale does not qualify. Use the equivalent groups in your own store.

When is an order counted?

• An accepted order using a supported offline payment method can qualify. This does not mean that you have received payment.
• An online order qualifies after a verified successful payment outcome. Failed, cancelled or unconfirmed online payments do not count as completed.
• Refreshing the confirmation page or returning again does not create a second completion event for the same order.

The checkout_completed event contains no customer details, order number, amounts, products or payment-return details. It is a completion signal, not a revenue or product report.

Missing consent, a blocked tracker or leaving the page can prevent recording. Analytics cannot guarantee that every order appears in Umami.

Build an Umami funnel

A funnel shows how visitors move through the steps before completion.

1. Open the correct website in Umami and go to Funnel.
2. Click Add funnel.
3. Use Add to create the earlier steps. Choose Viewed page for your store’s actual cart and checkout URLs. If you already track an add-to-cart event, you can add it as a Triggered event step.
4. Add a final step of type Triggered event.
5. Enter the exact event name checkout_completed.
6. Set a suitable Window for the time allowed between steps, then click Save.
7. Run the insight after eligible events have been recorded.

Steps must occur in order; visitors may visit other pages or events between them. The Umami connection does not create earlier funnel events. You do not need a new /success.html URL, and payment URLs stay unchanged.

See the official Umami Funnel guide for the current report options.

Check the result

1. On a test store, place a new test order using a supported offline method or your payment provider’s test mode. Do not make a real charge just to check analytics.
2. Use a shopper in the selected retail groups and grant analytics consent through the store’s cookie banner.
3. Complete the order and keep its confirmation or payment-return page open long enough for the tracker to load.
4. Open the same website in Umami and check for checkout_completed. Then check the funnel for the chosen time range.
5. Refresh the confirmation page. It should not add another completion event for that order.

If no event appears, check:

• Is the correct Umami tracker loaded on the completion page?
• Is Umami — checkout completion selected, and were the settings saved?
• Are all of the customer’s shopper groups selected? Is the guest group included when needed?
• Has the required consent been granted, with the exact cookie name and value?
• Does the order meet the completion conditions described above?
• Are you viewing the correct Umami website and time range?

GA4/GTM dataLayer (Beta)

1. Select Consent-aware GA4/GTM dataLayer (Beta) as the Tracking adapter.
2. Keep Require analytics consent enabled when required.
3. Enter your consent platform’s exact Analytics consent cookie and Granted cookie value.
4. Save and test both denied and granted consent states.

When consent is required, an empty, invalid or mismatched cookie mapping keeps tracking disabled. Events use a minimized allowlist and must not contain customer names, email addresses, postal addresses or payment secrets.