If the vendor requires data (like a vendor-specific unique ID, for example) that can only be generated or accessed by their own client-side tag, then that vendor tag is likely not a good candidate to move. Attempting to reverse-engineer a client-side tag with the idea of moving that data collection to event forwarding without the appropriate APIs is discouraged.
@NitinCT You can do that in fact that's one of the main feature of the server side event forwarding. Note that Event forwarding is a paid feature that is included as part of the Adobe Real-Time Customer Data Platform Connections, Prime, or Ultimate offerings. May want to check with client suport.
nhanced conversions leverage the Google Ads API to add first-party data to a conversion that happened on a client device, usually a website. This means that there are two steps to implement enhanced conversions:
Send a conversion from the client.
Use event forwarding to send additional first-party data that enhances the conversion data sent from the client.
Since sending conversion events involves both a client-side and server-side implementation, this document covers the prerequisite steps for setting up the client-side Google Global Site Tag (gtag) extension in addition to the Enhanced Conversions extension for event forwarding.
If the vendor requires data (like a vendor-specific unique ID, for example) that can only be generated or accessed by their own client-side tag, then that vendor tag is likely not a good candidate to move. Attempting to reverse-engineer a client-side tag with the idea of moving that data collection to event forwarding without the appropriate APIs is discouraged.
