Processing Rules - Using Hit Attributes | Community
Skip to main content
Level 2
August 17, 2023
Solved

Processing Rules - Using Hit Attributes

  • August 17, 2023
  • 2 replies
  • 1463 views

Hello,

 

When writing a processing rule, one of the options for changing a variable's value is to choose a "Hit Attribute," among which is the value "Report Suite ID". I would like to know if this really means literally that the RSID will be inserted as a new value, or, am I missing something? I have looked through the documentation but I am not finding information about these "Hit Attributes" and how they are used.

The reason for the question is that we capture the RSID in a property, but the site code occasionally goes rogue and inserts an improper value. Yes, it would be nice if the code monkeys would fix the code, but we're overwhelmed with work and that's not going to happen soon. In the meantime, I would like to clean it up.

Help is appreciated.

Thanks.

 

mp

"He flung himself from the room, flung himself upon his horse and rode madly off in all directions." - Stephen Leacock

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 Jennifer_Dungan

I've not used the "Report Suite ID" specifically, but I have used other Hit Attributes such as User Agent.

 

In my rule I choose an eVar and set the value of it to User Agent:

 

I've never had any issues with this, I would expect the Report Suite ID to act the same.

 

For your comment:


the site code occasionally goes rogue and inserts an improper value.

 

I assume you mean just the value you are populating into the dimension (eVar or Prop) and not where your tracking is being sent? In which case, I would think that replacing the manual setting of your dimension with this will be more reliable.

2 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
August 18, 2023

I've not used the "Report Suite ID" specifically, but I have used other Hit Attributes such as User Agent.

 

In my rule I choose an eVar and set the value of it to User Agent:

 

I've never had any issues with this, I would expect the Report Suite ID to act the same.

 

For your comment:


the site code occasionally goes rogue and inserts an improper value.

 

I assume you mean just the value you are populating into the dimension (eVar or Prop) and not where your tracking is being sent? In which case, I would think that replacing the manual setting of your dimension with this will be more reliable.

nyambolAuthor
Level 2
August 22, 2023

Hello,

 

Thank you for the confirmation. We use the value in the prop to segment traffic in our rollup RS, so relatively small amounts of error can have cascading ill effects.

Now, if I could just figure out why we still get 'Unspecified', my life would be complete. But, that's a question for another day.

Thanks again.

 

mp

 

"He flung himself from the room, flung himself upon his horse and rode madly off in all directions." - Stephen Leacock

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 22, 2023

Glad to help...

 

Is it still "unspecified" even after adding this as a processing rule?

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 21, 2023

It looks like they are trying to capture the RSID into a dimension, not change it. 

 

Report Suite ID is available in processing rules for this type of request: