Site Entry Page

[JuneGa]

Hi,

I want to create a Dimension for Entry Page.

I have created a derived field, but it seems wrong, and I cannot see a Function that lets me just say "If this, then that". No else. 

For example, I want the field to be the Page Name of the first page on the website visited. 

Then I can have a field in the table of another Dimension, or a filter, and see what the Entry Pages are.

I am getting alot of No Value, which doesn't make sense. Every website visit has an entry page.

I have attached screenshots, sorry I have blanked out page name, because i want to keep the website anonymous.

But the idea is that I can use it as a breakdown, so I can cross reference if X is the page/s I am interested in, what was the First page on the site they visited that got them there?

[SamuelPaulPeter]

Your derived field is correct in logic… but it’s using the wrong scope.
That’s why you’re getting a huge amount of “No value.”

Session starts is visit-scoped,
but your derived field is being evaluated at the hit level, not the visit level.
So only the first hit in each visit gets the Page Name — every other hit becomes “No value.”

That’s exactly what you’re seeing.

Change the derived field scope to "Session"

Edit your derived field → in the top right, set Scope = Session (not Hit).

When you do this the following happens:

• When the session starts → CJA picks the first Page Name

• That value is then carried for the entire session

• No more “No value,” because the dimension is no longer evaluated on every hit

If you want it even simpler:

Use Entry Page (built-in)
In many CJA connections, Entry Page already exists.
Search for it first — it works perfectly and avoids needing a custom rule.

The reason why your rule created "No value" is because:

• You only set the value on the first hit

• Every other hit in the visit has no Page Name set → so your “Otherwise = No value” takes over

• When you break down Sessions by the derived field, most visits show “No value” because you’re accidentally counting every non-first hit

Session scope fixes that immediately.

[JuneGa]

Thankyou, that was a really good point.

I have gone back and checked the Scope on the DF settings, and made it Sessions.

But I am still getting alot of unknown.

We do not have a field called Entry Page (Or Exit Page) in our instance. Is this something that is usually in the Web data from WebSDK? Our view is based on Stitched data set with offline data as well, so maybe it is a field that wasn't included in the stitched data schema?

I have dropped "session starts" as a counter with nothing but the default days in as well below, and it is perplexing that we could have 414k session starts, but 743k sessions. I would expect some difference in numbers, because some sessions may have started before the reporting period, but still been an active session, but the number is too large for that to be the reason.

Also re-attaching the DF I  created now I have worked out to embed images instead!

[JuneGa]

I checked the Web behaviour XDM and the is no Entry Page field there either.

[SamuelPaulPeter]

You fixed scope — good.
But many sessions lack the Session Starts flag or pageName on the true first hit (offline/stitching, server events, or missing client-side data).
So your rule only sets the entry page when Session Starts is present; every other session becomes “No value”.
That also explains the weird counts (414k session starts vs 743k sessions) — a large portion of sessions don’t have a session-start hit.

Fast fixes (try in this order)

>>Use hit number instead of Session Starts
Edit DF: If Hit Number = 1 THEN Page Name (Scope = Session).
This picks the first hit in the visit regardless of whether a session-start flag exists.

>>Validate landing hits for pageName

Build a temp table / segment: Entry Page (No value) and show earliest hit fields (pageName, hitNumber, sessionStart).
If earliest hits often miss pageName, fix the data collection (pageName not set on landing).

>>Check stitched/offline imports

If you use offline or stitched events, they may create sessions without sessionStart or with bad timestamps.
Filter those sessions and inspect sample hits.

>>Compare a known session (working vs broken)

Pick one session that shows a valid entry page and one that shows No value. Compare the first hit payloads in Assurance/raw events. That reveals whether the flag or pageName is missing.

>>If you want a resilient solution:

Create a session-scoped DF that chooses the first non-null pageName in the session (HitNumber=1 fallback to earliest non-null). Or build the entry-page via a small AEP query that snapshots the first page per session and write back as a dataset/derived field.

I hope this should resolve!