Hi Harshi,
Here's how you can validate your SSF implementation:
Unlike the client side implementation/integration, server-side integration does not send Analytics data to demdex servers in a separate event call. Instead, there are additional parameters in the Analytics server call, both in the request and in the response.
- The additional parameters in the Analytics call can be viewed in the Digital Pulse debugger, the network tab of the browser or via a packet sniffer like Charles. The screenshot below indicates the additional parameters in the request.
callbacCookies Supported | s_c_il[1].doPostbacks |
- In addition to these parameters in the request, you will also be able to see additional data in the response of the Analytics call. Instead of just returning a 2x2 pixel, it will return a JSON response from
AAM that would include the UUID and any segment data that you have qualified for, and which has been mapped to a cookie-based destination in AAM.
- Will AAM create a data source automatically post implementing SSF? If not, what is the best way to create it manually and ensure that it is indeed fetching data from our Adobe Analytics-SSF only?
No. Data source is primarily to organize your traits and identify the source of a signal. I would recommend that you create a Cookie Data Source and all traits that you create based on the site analytics data, associate them to this Cookie Data Source.
Cheers!