A4T — Tracking Server mismatch causing underreported unique visitors

Question

Hi,We're running A4T (Analytics for Target) and seeing significantly underreported unique visitor counts in Target reports compared to Adobe Analytics.Our tracking server was confirmed working correctly (HTTP 200) a couple of months ago. However, we've now identified a possible mismatch between the tracking server configured in Target and the one showing in Analytics console logs. We've reported it to Adobe but wanted to ask the community in the meantime.Note: Target's reporting console is currently down (Adobe is aware), so we can't fully confirm the numbers from that side either.Questions:Can a tracking server mismatch between Target and Analytics cause A4T visitor counts to be significantly underreported?	Any other A4T config parameters worth checking while we wait for Adobe's response?Thanks

Gokul_Agiwal · Answer

Hi ​@paula.gomezYes, a tracking server mismatch is definitely worth investigating and could contribute to A4T reporting discrepancies, especially if Analytics and Target are not consistently stitching data through the expected Analytics configuration. However, a successful HTTP 200 response alone does not guarantee that A4T integration and visitor attribution are working correctly. A4T depends on proper Analytics-Target integration, provisioning, and identity stitching.While waiting for Adobe's response, I'd recommend checking the following:ECID ImplementationVerify that both Analytics and Target are using the same Experience Cloud Organization ID.Confirm ECID is consistently present in both Analytics and Target requests.https://experienceleague.adobe.com/en/docs/id-service/using/implementation/ecid-a4t-targetSDID StitchingA4T relies on SDID (Supplemental Data ID) to stitch Target and Analytics calls together.If SDIDs are missing or not aligned, activity impressions may not be correctly attributed in Analytics reporting.https://experienceleague.adobe.com/en/docs/target/using/integrate/a4t/before-implement#section_2C1F745A2B7D41FE9E30915539226E3AReport Suite ConfigurationVerify the activity is using the expected Analytics Report Suite.Check whether any recent Report Suite or datastream changes were made.A4T ConfigurationConfirm Analytics is still selected as the reporting source for the activity and that A4T provisioning is intact.Activity qualification vs. Analytics visitorsRemember that not every Analytics visitor necessarily qualifies for a Target activity.Compare the same date ranges, segments, and audience criteria when validating counts.So please check this all configrather than the tracking server alone. And please validate the mismatch you've identified for tracking server with Adobe.Hope this helps till you getting any response from Adobe team.Thank you.

Sign up

Login with SSO

Login to the community

Login with SSO