Unused Signals Report - What Exactly is the Count? | Community
Skip to main content
G
glennb29356951
Level 4
August 30, 2018
Solved

Unused Signals Report - What Exactly is the Count?

  • August 30, 2018
  • 3 replies
  • 3211 views

Good morning,

I have a question about the unused signals report. If I look at this report:

It shows by Loyalty ID the count against any particular user for a single day correct?

What exactly is count? For the first line what was counted 222 times for that particular Loyalty ID?

Please advise. Thanks. Glenn

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Tof_Jossic

This is the frequency count of the signal being passed to AAM.

The c_ prefix is usually customer specific so it would need to be looked into at your end to check maybe in Analytics if this is coming from a unique user. This is a suggestion, you may also log a ticket with Customer Care to see if there is any other way to troubleshoot this.

3 replies

Tof_Jossic
Adobe Employee
Tof_JossicAdobe Employee
Adobe Employee
August 30, 2018

Hi Glenn,

looking at this, my understanding is that you are collecting these signals but they have not been mapped to a trait.

See Unused Signals Report

Is that first value in the image part of a trait expression in your AAM UI?

G
glennb29356951Author
Level 4
August 30, 2018

I understand that. But it “loyalty ID” is specific to a single user and on a given day the count of that signal is 500 what is being counted. 500 what? Hits, server calls, pages viewed, etc…

Tof_Jossic
Adobe Employee
Tof_JossicAdobe EmployeeAccepted solution
Adobe Employee
August 30, 2018

This is the frequency count of the signal being passed to AAM.

The c_ prefix is usually customer specific so it would need to be looked into at your end to check maybe in Analytics if this is coming from a unique user. This is a suggestion, you may also log a ticket with Customer Care to see if there is any other way to troubleshoot this.

Terms & ConditionsAccessibility statement

Loading footer...