AAM is registering more server calls from Adobe Target than Adobe analytics, huge concern
Dear Adobe Community,
We are using web sdk extension on our websites and through which we have integrated AA, AT & AAM tools in our setup.
In Target, we have activities configured mostly with Reporting source as AA and very few have configured for Target reporting.
On our websites, every data sent to AA will be forwarded to AAM which is fine, however on every pageload web sdk request, Target will be fetching offers and qualified experiences will be sent back to browser and will be rendered on website. All experiences are shown on pageload request only. A4T is implemented.
Whenever page request is made to server from browser, upload rendering page, single call will be initiated to Edge which will carry data to edge, from Edge Target request will be made automatically to fetch personalisation, web analytcis data wil be sent to AA and sametime data also sent to AAM.
We understand once Target receives request for that page, it makes call to AAM to fetch AAM segment data, so in reality 2 calls are going to AAM,
1. Target to AAM to get or fetch segment to make personalization decision for that page
2. Edge will send analytcis data to AAM
Ex.
That mean if user is browsing 100 pages on websites, 200 calls should be going to AAM (100 from Edge to AAM, 100 from Target to AAM)
However in AAM usage shows 220 calls going to AAM. (100 from edge to AAM, 120 from target to AAM)
we are not sure about 20 extra calls which are going from Target to AAM?
Any clue on this?
Thanks