Gambio monitoring from cart to checkout
XICTRAQ checks the homepage, cart, checkout path and admin login of your Gambio shop from the outside and keeps an eye on offline mode and the cron job. The cookieless tracker reads product views, add-to-cart clicks and the order completion from the Gambio markup; you add the revenue with one call in the template.
Check these Gambio pages first
- Uptime monitoringHomepage with a keyword against the offline page
/ - API monitoringCart: status and fixed page text
/shopping_cart.php - Browser monitoringFrom product page via cart to checkout
/checkout_shipping.php - Browser monitoringLogin with a test customer
/login.php - Uptime monitoringAdmin login as a subpage
/login_admin.php
Why the homepage is not enough for Gambio
A Gambio shop guides customers through its own PHP pages: shopping_cart.php for the cart, checkout_shipping.php and checkout_payment.php for shipping and payment, login.php for the customer account. The template, modules and updates also hook into these pages. The homepage can keep answering with HTTP 200 while the cart shows an error or the add-to-cart button stops responding.
On top of that come states the shop switches itself: the “Inhalte > Shop online/offline” setting (Content menu) puts an offline page in front of the shop, behind which, according to the manual, no content is visible and no orders can be placed, optionally on a schedule via a cron job at the hosting provider. And without a custom error page, Gambio redirects pages that are not found to the advanced search instead of showing an error.
XICTRAQ therefore spreads the checks across several modules: uptime monitoring with a keyword and subpages for the homepage and admin login, API checks with text assertions for the cart and product pages, browser checks for the path to checkout, a heartbeat for the cron job and the security scan for publicly accessible files.
Uptime, API and browser checks treat a Gambio shop like any other website: what gets checked is determined by the paths, keywords and steps you set up. Let browser checks end before an order is submitted so that no real orders are placed.
What can fail in Gambio shops
Shop left switched offline
According to the manual, the offline page blocks content and orders. If it answers normally and lacks the keyword configured for the homepage, the keyword check fires. If it comes with HTTP 503 and a word such as “Wartungsarbeiten” (maintenance) in the text, XICTRAQ records maintenance: start and end appear in the changelog, outage and content alerts pause, while SSL, domain and blacklist alerts stay armed. Another error status generally counts as an outage.
Cart returns an error or a blank page
After updates or module installations, the cart can show errors while the homepage and product pages keep loading. An API check requests /shopping_cart.php, follows redirects and checks a status code and a text that you set as assertions, such as the page heading. If an error status comes back or the text is missing, XICTRAQ reports the failed check.
Add-to-cart button stops working
An error in the template or a module can break the add-to-cart button even though every page answers with HTTP 200. A browser check opens a product page, clicks the button, opens the cart and verifies by text that the product is listed there. If a step fails, XICTRAQ reports the run as failed and, if the capture succeeds, keeps a screenshot of that step.
Deleted product ends up on the search page
According to the manual, Gambio redirects pages that are not found to the advanced search if no custom error page is set up. A deleted product that ads or search engines still link to can therefore slip past a plain availability check. An API check on the product URL follows the redirect and verifies a text that appears on the product page but not on the search page. If it is missing, the check fails.
Cron job for the shop status does not run
According to the manual, scheduled offline and holiday switching needs a cron job at the hosting provider that calls the shop’s cron job URL. If it does not run, a planned switch does not happen. Append a call to your heartbeat URL to the cron entry: if the ping does not arrive according to the interval or cron schedule, XICTRAQ reports a missed run. Whether Gambio actually processed the call is not visible to the heartbeat.
Database backup exposed in the web root
After a move, an update or troubleshooting, files such as dump.sql, backup.sql, phpinfo.php or adminer.php are sometimes left in the root directory. The security scan requests a fixed list of such file names in the shop’s root directory, including .env and .git/config, and lists the files it finds with their severity in the report. If the shop answers every unknown URL with HTTP 200, the scan only checks files whose content it can recognise, such as .git/config or phpinfo.php, but not dump.sql. Files with other names or in subdirectories are not found by this probe.
How XICTRAQ recognises Gambio
Two components recognise Gambio independently of each other: the tracker in the visitor’s browser and the website scan. Uptime, API and browser checks do not distinguish Gambio; they check what you configure.
- The tracker switches to its Gambio branch when the page contains Gambio widget attributes such as data-gx-widget or data-gx-extension, or elements such as .gx-container or #gm_products_detail.
- If these markers are missing, for example in a heavily customised template, only the tracker’s generic detection for cart buttons, checkout and thank-you pages applies.
- The scan lists Gambio as the shop system when the HTML contains traces such as gambio.php, GambioHandler or /gambio_installer. In addition, the extended technology detection recognises Gambio by the script gm_javascript.js.php.
- The monitoring agent itself does not recognise Gambio. So that a later technology check does not erase the result, the shop system found by the scan is kept.
- Monitoring does not depend on detection: uptime, API and browser checks test the paths, keywords and steps you set up, even if the template no longer carries any Gambio markers.
What the tracker captures in Gambio
When the tracker finds Gambio markers in the markup, it reads product view, add-to-cart click, checkout start and order completion straight from the shop pages. It sets no cookies for this.
Captured by the tracker on its own
- Page views with referrer and UTM parameters, plus Web Vitals such as LCP, CLS and INP.
- Product views with name, price and the product ID from the products_id field, as far as the page outputs them.
- Add-to-cart clicks with the product data carried by the markup around the button, such as name, price and quantity.
- The start of checkout as soon as a visitor reaches checkout_shipping.php or checkout_payment.php.
- The order completion as a purchase event without an amount, provided the confirmation page contains a .checkout-success or #checkout_success element, with the order number if it appears in the .order-number element.
- JavaScript errors from real visits with message, file and line.
Not captured automatically
- Revenue from the Gambio markup: the order completion arrives with an amount of 0, and tax, shipping costs and line items are missing. The reports only receive an amount if you pass it or the shop writes a purchase with a value to the dataLayer.
- Signed-in customers: the tracker has no Gambio-specific way to link them, so without a change to the template they stay anonymous.
- Removing items and changing quantities in the cart. The Gambio branch does not handle them, and it has not been verified that the generic cart observation can read the Gambio markup.
- Whether a product actually landed in the cart: what is counted is the click on the button.
- Cancellations and refunds made in the shop administration. There is no automatic event for them.
- Orders created without a confirmation page in the shop, for example orders entered in the shop administration.
Pass missing values through the JavaScript API, called after DOMContentLoaded because the tracker loads deferred: xictraq.revenue(amount, "EUR", orderNumber, { tax: tax, shipping: shipping }) in the order confirmation template, amounts in euros. Link signed-in customers with <meta name="xictraq:user-id" content="CUSTOMER_NUMBER"> or xictraq.identify(customerNumber, { type: customerGroup }), and refunds with xictraq.refund(orderNumber, amount, "EUR"). The automatic completion without an amount keeps being sent alongside: after adding the call, check the first orders in the reports for duplicate or empty purchases.
The right modules for Gambio
Frequently asked questions
Does XICTRAQ recognise my shop as a Gambio shop?
In two places, provided the shop carries the matching markers. The tracker recognises Gambio by template markers such as data-gx-widget and then switches to its Gambio branch, and the scan lists Gambio as the shop system when it finds traces such as gambio.php or the script gm_javascript.js.php. Uptime, API and browser checks do not distinguish Gambio; they check the paths and keywords you configure.
Why is there no revenue for Gambio orders in the reports?
The tracker reports the order completion on the Gambio confirmation page without an amount, because it does not read the amount from the markup there. Add the revenue with xictraq.revenue(amount, "EUR", orderNumber) in the order confirmation template. The automatic completion without an amount keeps being sent alongside, so check the first orders in the reports after adding the call.
What does XICTRAQ report when I switch my Gambio shop offline?
That depends on how the offline page answers. If it comes with HTTP 503 and a word such as “Wartungsarbeiten” or “Wartungsmodus” (maintenance) in the text, XICTRAQ records maintenance, pauses outage and content alerts and logs start and end in the changelog. If it answers normally, a keyword check on a word that only appears on your homepage fires, and another error status generally counts as an outage. Which status code your shop sends is shown in the uptime history after switching it offline.
Can a browser check test the Gambio purchase path without placing an order?
Yes. A browser check can open pages, click, fill in fields, wait for elements and verify text, URLs or status codes. Let it end before the order is submitted, for example on checkout_shipping.php or checkout_payment.php. For the login at login.php, use a dedicated test customer rather than a real customer account.
How do I link signed-in Gambio customers?
The tracker has no built-in Gambio-specific way to do this. Output <meta name="xictraq:user-id" content="CUSTOMER_NUMBER"> in the template for signed-in customers or call xictraq.identify(customerNumber, { type: customerGroup }). Pass a customer number, not an email address or a real name.
Why is monitoring only the homepage not enough for Gambio?
In Gambio, cart, checkout and customer account live on separate PHP pages such as shopping_cart.php, checkout_shipping.php and login.php. If one of them fails, the homepage can keep loading normally. In addition, according to the manual, Gambio redirects pages that are not found to the advanced search if no custom error page is set up, so a deleted product can slip past a plain availability check. Check these pages individually for that reason.