Configure test/live payment details and validate the complete payment return.
Configure payment settings
Select the correct widget and open Payment Settings with an authorized account user.
Choose the intended Adyen environment and enter the API key, client key and live endpoint prefix where required.
Confirm the merchant account code and submerchant ID with Apaleo. Review the allowed-domain instructions shown in the editor.
Make sure the actual booking origin is allowed for both the widget integration and the payment provider.
Run a test payment, including its redirect/return, and verify the resulting reservation and payment status.
Guarantees, invoices and failures
If company invoice booking is enabled, check that the selected offer’s rate plan uses Company guarantee; enabling the option does not make every booking an invoice booking.
If payment fails, record the stage and visible error and inspect whether an order, reservation or payment already exists before retrying.
For a real charge or uncertain payment result, send support the order/reservation IDs and timestamp through the support channel.
Do not place API keys, card details or payment return tokens in support chat. Payment settings and origins need separate review when moving from test to live.
Publish the correct widget using its generated integration instructions.
Get the correct integration
In Widget Settings, select the saved IBE ID and check its name, languages and presentation.
Copy the generated embed or booking URL from that widget’s instructions; standard, URL and popup integrations have different entry points.
Add every host origin, including protocol, to the allowed origins list. Review www/non-www, staging and production separately.
Insert the generated integration into the host website, then test opening, searching, checkout and the payment return.
For popup integrations, test the trigger button, closing behavior and mobile layout.
Diagnose an embed issue
Open the booking URL directly to separate widget configuration from host-page integration.
Check the IBE ID, script URL, allowed origin and browser errors.
Review host-page CSS/layout and popup behavior when the direct booking URL works.
Copy integration code from your current environment. A test script or test IBE ID should not be assumed to use production settings.
WordPress and website optimizers
Paste the generated snippet into a Custom HTML block; no Simultem WordPress plugin is required.
Replace the script tag as well when updating an existing embed, preserving the generated optimizer-exclusion attributes.
Clear the website’s page and optimization caches once after replacement.
Check that the browser loads the intended hosted widget script. If an editor strips attributes or an unsupported optimizer rewrites the script, configure an explicit exclusion.
The generated snippet includes exclusions for WP Rocket, Cloudflare Rocket Loader, Autoptimize and LiteSpeed Cache. Host analytics and consent remain controlled by the website.
Inspect funnel behavior and integrate booking-completed events with the host site.
Use booking reports
Open the booking reports view and choose the property, dates and language/filters offered.
Review stage counts from landing and search through checkout, payment, success and failure.
Inspect reservation and service amounts when comparing completed bookings.
Compare the same date and property scope before drawing conclusions from funnel counts.
Compare periods, cancellations and campaign results
The built-in reservation query uses the IBE channel and reservation creation-date range. This is different from stay dates, payment dates or task due dates.
The reservation count/amount calculation does not explicitly exclude canceled reservations. Check current source status and amendments before treating these figures as cancellation-adjusted revenue.
For cross-hotel or campaign comparisons, define the date basis, status treatment, currency and refresh point before comparing totals.
These screens do not automatically attribute bookings or task workload to a Bulk campaign. Use an explicit campaign-to-reservation linkage and a defined reporting measure for that analysis.
Use funnel stage counts to locate drop-off. A stage count does not establish the cause of each failure; check the actual booking/payment outcome separately.
Configure website tracking
Open IBE Booking Reports → GA4 & Google Ads setup instructions, also available in onboarding.
In the host website’s GTM container, add a Custom Event trigger named purchase and a GA4 Event tag named purchase with Send Ecommerce data → Data Layer enabled.
For an Ads tag, map ecommerce.value, ecommerce.currency and ecommerce.transaction_id and set your own conversion ID and label.
Test in GTM Preview/GA4 DebugView with a completed test booking.
If using the independent simultem:booking-completed event for custom integration, register the listener before checkout completes and avoid creating a second purchase path.
Events indicate booking creation, including pay-later bookings; they do not prove that every folio payment has been collected.
GA4 value is the full confirmed booking net revenue excluding VAT/city tax, not just today’s deposit. Items represent reservations including booked extras, with quantity 1 per stay. Incomplete financial reconciliation can suppress purchase while the independent completion event remains available.
Host tags and consent control delivery to Google. Do not forward both native purchase and the custom completion signal as duplicate purchases.