- How does web sdk support event forwarding through edge network for cookieless tracking?
By itself, Web SDK doesn't. Instead, Web SDK is the client-side JavaScript library that sends data to what is called a "datastream", which is setup in Adobe Experience Platform. This datastream is like a pipe that sends data to other Adobe products, like Analytics and Target. It also sends data to Event Forwarding, an AEP product that you have to purchase separately.
Note, though, that I suspect your developers' understanding of "event forwarding" is different from this AEP Event Forwarding product. AEP Event Forwarding is to help you send server-to-server data, for example, to Facebook via its Conversions API.
Using Web SDK will still result in a cookie being set in your users' browsers, though that cookie is an HTTP server cookie, not a JavaScript cookie.
- What are deliverables from the dev team if we migrate to web SDK ? for example changes in the source code by implementing a new header script etc
Take a look at these articles:
https://medium.com/adobetech/adobe-experience-platform-web-sdk-migration-scenarios-for-adobe-analyti...
https://alex-bishop010.medium.com/migrating-to-the-adobe-experience-platform-web-sdk-67cd0e5c727b
- What about support for API for FB, DV360, Google Ads if we migrate to web SDK?
Those will be done through Event Forwarding. However, if your organisation does not buy Event Forwarding, you can still send these via client-side using their own JavaScript libraries (or a compatible extension, if you're using AEP Data Collection Tags, aka. Adobe Launch).
- What about Google Analytics, do we implement it using the connectors in web SDK? or through Adobe Launch extensions?
As above, you can use Event Forwarding, or GA's own client-side library (or if using AEP Tags / Adobe Launch, then with Acronym's Google Site Tag extension).
