Segment container - consistent across all segments?

[zming_744]

If we have multiple segments at the top of the free form table, should we have the same segment container across all the segments?
Eg: I am setting segment: country version as Japan (Visit), Page ID (Visit).
Instead of Country version: Japan (Visit), Page ID (HIT)

[RobertBlakeley · Accepted solution]

Depends on what you want. There is no container-consistency rule I can think of.

Remember that hit containers look at one call at a time. Visit containers find all the activity in the visit where any call in that visit matches the segment.

Use Case:

A Japanese visitor sees the following in a visit :

• Page ID 1
• Page ID 2
• Page ID 3
• Page ID 4

For these segments:

• The Japan segment: Visit Country=Japan
• The Page ID segment: Hit pageID = Page ID 3

Your segment would find Japan and Page ID 3.

For these segments:

• The Japan segment: Visit Country=Japan
• The Page ID segment: Visit pageID = Page ID 3

Your segment would find Japan and all the pages in the visit (Page IDs 1 through 4).

[Jennifer_Dungan]

I agree, use the segments that make sense to pull the data you need. If one of them is Visit and the other is Hit, so long as they aren't exclusive of each other (which these ones should not have issues), then they will stack their logic.

[zming_744]

If there are no segment set on the freeform table, are the metric results shown on the table produced by 'hit' results?