Hi @Md_Monirul_Islam,
I’ve just played around a bit with this and could reproduce it. I believe that Google has changed the way sGTM Google Ads conversion tags are handling the value now.
There are 2 scenarios:
1) Value is picked up from the Event Data, when no value is set on the tag template Conversion value field.
Details
This works as usual, i.e., the value parameter is read from Event Data and put in the value parameter on the outgoing requests to Google Ads (from the server) and back to the browser.
2) Value is picked up from the Conversion value field on the tag template.
This is where things get interesting.
Details
When this happens, the Google Ads conversion tag on sGTM makes a request to
https://www.googletagmanager.com/sgtm/e?v=123.99
and get a response like this
AfCkEnYFxBCftgNqi800sy9jUSVCdmgkINgDlLdFjVjZNzCCBHBw
This response changes every time the request is made, even if using the same input value. So, I’m not sure what Google does here. But it’s definitely linked to the conversion value, as you are going to see below.
This value got in the response is put in the sg_ecv parameter in the outgoing request on the request from sGTM to Google Ads and, also on the request back to the browser.
This is the sGTM request to Google Ads (it will be sent only if you have some sort of Click ID being collected, otherwise, you will have only the browser request below).
Check the sg_ecv parameter.
Obs.: if you are using Advanced Consent Mode, the request will go to https://pagead2.googlesyndication.com/pagead/conversion[...].
This is the sGTM request back to the browser. Check the sg_ecv parameter.
Therefore, we can only conclude that this is the Conversion Value being passed in a different parameter.
