Page View Processing Rule

Question

I have an evar for Page Name, but because I don't have a prop, I can't get Entry Page Name.

Is there a best way to set up a processing rule to set the prop whenever the evar is set but only if its a page view?

Right now, I have a rule that says if my Page Type prop is set then run the rule to create the Page Name prop, so I think it should work, but just want to make sure I'm doing it the best way.

JayGr · Accepted Answer

Hi Jay,

Using Launch would be a lot easier than Processing Rules.... If you want the Prop to be set on Page Views (and the eVar to be set on Page Views and Actions), why don't you just add the prop to your Page View rules? (the rules that trigger the s.t beacon).

I suppose you could try to create conditions on your Processing Rules for your eVar to be set, but "customlink" to not be set (I think customlink would be your action link names... but confirm this....)

I normally only do stuff like this on mobile apps, so I use a.action is set / not set (which might still work for web... )... but I've never attempted to identify a page view from an action on the web.... (Activity Map is part of the "a" context data.. so a.action is likely also available on web)

Next question is... do you really need the "Entry" and "Exit" variants of the dimension? Cause on your eVar, you can pair with different metrics to get all, just page views, and just where the eVar is explicitly set without tracking a new dimension....

Page A
- eVar1 not set
- eVar2 set to "Page A"
Page B
- eVar1 set to "X"
- eVar2 set to "Page B"
Page C
- eVar1 maintains value "X" (but not set)
- eVar2 set to "Page C"
Action 1
- eVar1 maintains value "X" (but not set)
- eVar2 set to "Page C"

In this scenario:

		Page View	Occurrence	eVar1 Instance
eVar2 (Page)		2	3	1
	Page A	0	0	0
	Page B	1	1	1
	Page C	1	2	0

Only Pages B and C have a value set to eVar1, and in Page C's case, it has both a page view and an action...

The Page Views are limited to just the page views, the Occurrences capture Page Views and Actions, and the "eVar1 Instance" is only where the value of the eVar was explicitly set.

Thanks for your response.

I totally agree that doing this via Launch would be much easier, but I don't have the IT resources available to implement for me in the short-term, which is why I'm looking for the processing rules short cut.

And the main reason I want to create this entry version of the dimension is for the simplicity of general business users in finding the right values.

I went with the below method and it seems to be returning the correct results in my development account.

Thanks for all your feedback!

bjoern__koth · Answer

Hi @jaygr

if you want to store the initial page name, I don't think this can be easily achieved with processing rules without adaptations in your tag management system.

Options

- you can send the page name once in a dedicated eVar upon the first page view execution and map this value via processing rule to your prop

- you can ask your dev to place a small piece of custom code in your tag manager rule that persists the initial value locally (e.g., through _satellite.setVar("pageNameInitialValue", "page name value") and make sure it is only executed once. This variable can then be referred to in the tracking request's prop through %pageNameInitialValue%

In Launch, I would do it like this

// check previous value
const prevValue = _satellite.getVar("pageNameInitialValue");
if (!prevValue) {
    // set with your initial value, in this case it was stored in another data element "Page Name"
    _satellite.setVar("pageNameInitialValue", _satellite.getVar("Page Name"));
}

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded