Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Incorrect Browser Name and Operating system in Tracking logs

muralipraveenr1
Level 2
Level 2

Hello,

We are facing the following issue in the tracking logs,

the browser name and operating system are not populating correctly, we have opened the mail and links in Chrome and Windows 10, but below is the data we got its populating firefox- windows XP for Open and Any other email Click Chrome - Windows NT

1737716_pastedImage_5.png

Is there anything we have to update in userAgent schema?

Please help us on this. Thanks in Advance

1 Accepted Solution
Venu_Reddy
Correct answer by
Community Advisor
Community Advisor

Hello,

Most of the time we see that count in tracking logs are consolidated this may have happened because of numerous reasons, such as automatic workflow to update this schema is behind the tracking logs by 5 minutes or it was failed or was not successful because of a system restart, etc.

To fix this, select the concerned delivery in the Adobe Campaign Explorer, right-click and choose Action>Recompute delivery and tracking indicators. Select the highlighted option, Click Next, then click Finish.

1738291_pastedImage_0.png

Please may you tell if it is a recent delivery, within the purge delay scope?

Please check the xtk.options values:

NmsCleanup_TrackingLogPurgeDelay

NmsCleanup_TrackingStatPurgeDelay

(or use the menu Tools>Advanced>Deployment wizard and go to the purge delay page).

Then, it is within the right purge delay scope, and you see some differences, please check technical processes.

The tracking log entry captured in the redirection log file may be corrupt. Many times it can happen because of the end user's machine/device.

Short term solution is to get hold of this file from the tracking server and then delete this line, followed by a restart of tracking workflow.

There is no clear reason known as corruption of information happens on end user's machine which is not in control of Campaign.

End user is using a browser with add-ons or extenders that hinder with the data being passed to Campaign redirection server.

These are all hypothesis and hence we really don't know what causes it as a result we have made the system capable of handling more of these situations

Regards,

Venu

View solution in original post

1 Reply
Venu_Reddy
Correct answer by
Community Advisor
Community Advisor

Hello,

Most of the time we see that count in tracking logs are consolidated this may have happened because of numerous reasons, such as automatic workflow to update this schema is behind the tracking logs by 5 minutes or it was failed or was not successful because of a system restart, etc.

To fix this, select the concerned delivery in the Adobe Campaign Explorer, right-click and choose Action>Recompute delivery and tracking indicators. Select the highlighted option, Click Next, then click Finish.

1738291_pastedImage_0.png

Please may you tell if it is a recent delivery, within the purge delay scope?

Please check the xtk.options values:

NmsCleanup_TrackingLogPurgeDelay

NmsCleanup_TrackingStatPurgeDelay

(or use the menu Tools>Advanced>Deployment wizard and go to the purge delay page).

Then, it is within the right purge delay scope, and you see some differences, please check technical processes.

The tracking log entry captured in the redirection log file may be corrupt. Many times it can happen because of the end user's machine/device.

Short term solution is to get hold of this file from the tracking server and then delete this line, followed by a restart of tracking workflow.

There is no clear reason known as corruption of information happens on end user's machine which is not in control of Campaign.

End user is using a browser with add-ons or extenders that hinder with the data being passed to Campaign redirection server.

These are all hypothesis and hence we really don't know what causes it as a result we have made the system capable of handling more of these situations

Regards,

Venu

View solution in original post