Uninstall Legacy Integration
If you have previously implemented the legacy manual client-side integration, this guide will help you properly remove the old implementation. After uninstalling the legacy integration, you should implement one of our current integration methods to continue sales tracking.
| After completing the uninstallation process, choose and implement one of our current integration methods: Server-Side GTM, Manual Server-Side, Client-Side GTM, or Manual Client-Side. |
Identifying Legacy Integration
The legacy manual client-side integration uses a specific JavaScript pattern that you can identify in your checkout/order confirmation pages. Look for code similar to this:
<script type="text/javascript">
var _mo = _mo || [];
_mo.push(['_key', 'XXX']);
_mo.push(['_sales', 'X.XX']);
_mo.push(['_shippingcosts', 'X.XX']);
_mo.push(['_articlelist', 'XXX,YYY']);
_mo.push(['_orderid', '']);
(function() {
var mo = document.createElement('script');
mo.type = 'text/javascript';
mo.async = true;
mo.src = 'https://service.moebel.de/api/1.0/moebel/de/sale/asyndic.js';
// or similar URLs for other portals
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(mo, s);
})();
</script>Legacy Script URLs to Remove
The legacy integration loads scripts from these URLs. Remove any references to:
Step-by-Step Removal Process
1. Locate Legacy Code
Search your checkout/order confirmation pages for:
-
The
var _mo = _mo || [];variable declaration -
Any
_mo.push()calls -
Script loading code that references the legacy service URLs above
2. Remove JavaScript Code
Delete the entire legacy JavaScript block from your order confirmation pages. This includes:
-
All
_movariable declarations and array pushes -
The dynamic script loading function
-
Any related legacy tracking code
3. Clean Up Template Files
If you’re using a template system or CMS, ensure you remove the legacy code from:
-
Order confirmation page templates
-
Thank you page templates
-
Any checkout success page templates
-
Email templates (if the tracking code was included there)
4. Remove Legacy Parameters
If you have any server-side code that was preparing data for the legacy _mo array, you can remove:
-
Code that formats data for
_sales,_shippingcosts,_articlelistparameters -
Any legacy-specific data processing logic
5. Verify Removal
After removing the legacy code:
-
Test your checkout process to ensure it still works correctly
-
Check browser developer tools to confirm no legacy script requests are made
-
Verify no JavaScript errors are thrown due to missing legacy code
-
Prepare to implement one of our current integration methods
Common Locations to Check
Legacy integration code is typically found in:
-
Order confirmation pages (
/checkout/success,/order/complete, etc.) -
Thank you pages after purchase completion
-
CMS templates for e-commerce platforms
-
Custom checkout implementations
-
Email confirmation templates (less common but possible)