Why I cannot see context variables in my processing rules.

Avatar

Avatar
Level 1
davidw50065164
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
davidw50065164
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
davidw50065164
Level 1

04-10-2019

1840048_pastedImage_0.png

Hi, I created a new report suite yesterday and I sent context variables to the report suite. However, I cannot see any of them.

I also check other report suites that I created months ago. Some have context variables, some do not.

Can anyone help me about this?

I try to using processing rule to copy the out-of-box link tracking values to eVar and prop.

Replies

Avatar

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

538 likes

Total Posts

973 posts

Correct reply

264 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile

Avatar
Shape 25
MVP
Andrey_Osadchuk
MVP

Likes

538 likes

Total Posts

973 posts

Correct reply

264 solutions
Top badges earned
Shape 25
Bedrock
Coach
Boost 500
Affirm 250
View profile
Andrey_Osadchuk
MVP

04-10-2019

Hey David,

Not sure why the variable does not appear in the drop down menu. As far as I remember, the list should display the vars that have been passed to the report suite for the last month.

I would advise to not wait, just type in the variable name in the field and hit Enter. It will allow you to configure the processing rules right away.

Avatar

Avatar
Level 1
davidw50065164
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
davidw50065164
Level 1

Likes

0 likes

Total Posts

6 posts

Correct reply

0 solutions
View profile
davidw50065164
Level 1

04-10-2019

I figure it out myself. You need to enable Activity map for that report suite to show the context data in processing rule (However, I am not able to see any real data right now)

Can some of you add this to the document in the processing rule, as none of the material mention this and it is pure misleading!