WebSDK Target A4T Reporting | Community
Skip to main content
Level 2
October 23, 2024
Solved

WebSDK Target A4T Reporting

  • October 23, 2024
  • 3 replies
  • 826 views

Hello Experts,

 

We recently migrated to WebSDK and our target activities on pages are loading just fine.

But reporting wise we see huge dip. 

 

How can we fix that and ensure reporting becomes accurate?

 

For eg. Pre go live we had 360+ unique visitors on a given day and now we have just 76. This is a big concern to business and wanted to check if you have seen something like this and how to fix it?

 

Thanks,

Nitin

Best answer by RiteshY18

@nitinct  issue seem to be due to migration of Analytics tracking to Web SDK , plz check  web sdk is correctly configured/mapped to send data to Adobe analytics along with data collection rules/action and events

3 replies

Gokul_Agiwal
Community Advisor
Community Advisor
October 23, 2024

Hi @nitinct 

Which logging method you are using for Analytics for Target (A4T) use cases... Is it Client-side Analytics logging / Server-side Analytics logging ? 

at initial stage, can you ensure the web sdk is correctly configured to send data to Adobe analytics. Check your data mappings and sendEvents action within rule. 

November 5, 2024

Hi 

 

I have the same situation when comparing the unique visitors from A4T and impressions where we can not be sure that are unique visitors from the activity.

 

It is showing more unique visitors than activity impression.

 

Does anyone solve this problem?

 

Thanks.

RiteshY18
Community Advisor
RiteshY18Community AdvisorAccepted solution
Community Advisor
November 7, 2024

@nitinct  issue seem to be due to migration of Analytics tracking to Web SDK , plz check  web sdk is correctly configured/mapped to send data to Adobe analytics along with data collection rules/action and events