XML to JSON power-up

The XML to JSON power-up automatically converts incoming XML webhook data into JSON format inside your sGTM container. This is useful because sGTM works natively with JavaScript, making JSON the preferred data format. Enable it once, and all XML requests sent to the designated endpoint are converted without any custom code.

XML to JSON is available on the Business subscription plan and higher. To check your current plan or upgrade, go to your sGTM container settings.

1. Log in to your Stape account and select your sGTM container from the dashboard.

2. Go to the Power-ups tab.

3. Click Use next to the XML to JSON panel.

4. Toggle the XML to JSON switch to enable it, and click Save changes.

1. 1.
   Send an XML request to https://ss.example.com/stape/xml/ (replace https://ss.example.com with your tagging server URL)
2. 2.
   Open your sGTM container preview and confirm the incoming request is in JSON format.

To implement these steps, follow the instructions in Debug incoming webhooks in Google Tag Manager.

You can also append a custom path after /stape/xml/. For example, 
https://ss.example.com/stape/xml/data, and the converted JSON will be forwarded to /data inside your container. 

A sample scenario is a team using a CRM that sends webhook notifications on every new deal, for example, when a lead converts to a customer. The CRM only outputs XML, but their sGTM container is set up to process JSON, so the webhooks arrive but no tags fire and no conversion events are recorded. 

You can identify this problem and fix it this way:

1. 1.
   In your sGTM container preview, check whether incoming webhook requests appear but result in no tag activity. If the request reaches the container but nothing fires, open the raw request body and confirm it’s XML rather than JSON.
2. 2.
   Enable the XML to JSON power-up and update the CRM webhook URL to <your-url>/stape/xml followed by the path your Data Client is listening on.
3. 3.
   Trigger a test webhook from your CRM and confirm in the sGTM preview that the payload now arrives as JSON and the expected tags fire.