As Mandy said, your segment won't work, because there is no "Page" value on your click, and if you change that to Visit, any visit that captures "page starts with Https://example" and then separately "Site section equals xyz" (not in the same hit, in any order in the visit, the entire visit will be returned... and every instance of your "click event" would be counted)
Visit 1
- Page A
- Click 1
- page will not exist (even though you see it sending data, this is removed during processing)
- site section = aaa
- "click event" triggered
- Page B
- Click 2
- page will not exist (even though you see it sending data, this is removed during processing)
- site section = xyz
- "click event" triggered
You are trying to get back "Click 2" only, but your segment won't work because there is no page value...
On the other hand, when you change the segment to Visit, all the hits above are returned as part of the segment (Page A, Page B, Click 1 and Click 2)... and because your freeform table is limited to the custom event "click event", then you are getting both Click 1 and Click 2.....
The best way to overcome this is to update your tracking with a custom eVar for a replicated page name value like so:
Visit 1
- Page A
- page = https://example.com/pagea
- site section = aaa
- eVarX (hit expiry) = https://example.com/pagea
- or you can use "D=g" (this will replicate the value without having to send the entire string)
- or you can set up a Processing Rule to set the value of eVarX to Page Name
- Click 1
- page will not exist (even though you see it sending data, this is removed during processing)
- site section = aaa
- eVarX (hit expiry) = https://example.com/pagea
- or you can use "D=g" (this will replicate the value without having to send the entire string)
- or you can set up a Processing Rule to set the value of eVarX to Page Name
- "click event" triggered
- Page B
- page = https://example.com/pageb
- site section = xyz
- eVarX (hit expiry) = https://example.com/pageb
- or you can use "D=g" (this will replicate the value without having to send the entire string)
- or you can set up a Processing Rule to set the value of eVarX to Page Name
- Click 2
- page will not exist (even though you see it sending data, this is removed during processing)
- site section = xyz
- eVarX (hit expiry) = https://example.com/pageb
- or you can use "D=g" (this will replicate the value without having to send the entire string)
- or you can set up a Processing Rule to set the value of eVarX to Page Name
- "click event" triggered
With this you can create the segment:
HIT [
eVarX starts with https://example
AND
site section equals xyz
]
While you could attempt to try and do a complex sequential segment, if there are potentially multiple actions tracked on your page then you won't get all the data back... for example, this complex segment:
HIT [
click event exists
AND
VISIT container (ONLY After Sequence) [
HIT Container [
Page starts with https://example
AND
Site Section equals xyz
]
THEN within 1 hit
click event exists
]
]
Will only return the "click events" that directly follow the page you specified, but if there are any hit between the page view and the click you are trying to capture, this will exclude it because it wasn't "within 1 hit" any more...
