BUT: Since we changed from web based tracking to server side tracking, MS Ads purchase conversions in the webGTM are tracked, but without the real conversion value. I know that MS Ads does not support SST. That’s why everything is only set up in webGTM.
For testing purposes I created an add_to_cart conversion in webGTM, configured it accordingly and I can see the correct value in the GTM preview and in the UET Tag Helper.
What can be the issue here? What are my alternatives? Do I need a DC tag in the sGTM to pass over the purchase value? Or should I use the MS Ads Offline Conversions?
Implementing sGTM does not affect your other web tags or parameters in them in any way.
You need to make sure in preview mode that the value is passed to MS ads along with the conversion, also make sure that in the conversion settings on the MS side you have it set to get a dynamic value and not a static value for the conversion value.
Thanks for your reply.
As I was mentioning, the purchase conversion for MS Ads existed before and worked properly before, including dynamic values of course. The only element that was changed when switching to SST and the M2 Stape extension, was the conversion value DLV. We use the same that works for Google Ads, Meta Ads and LinkedIn purchase conversions, but not anymore for the MS Ads purchase conversion. As this is the only purchase conversion that is only set up in webGTM, I was wondering what the issue could be.
You should check the outgoing request in MS and make sure there is a value there - this is the easiest and most correct way to determine where the problem is.
If there is a value in the outgoing request, then the problem is on the MS side.