Sorry, this confuses me a bit, could you add some more explanation? Basically you want users who have been to both your blog and your nonblog pages?

Yes, users who have been to both. I'm trying to come up with a clean way to match all non blog pages but with an ecommerce site with over 6,000 products that gets difficult. That's why the concept of negative look ahead is appealing by matching everything except blog. Using Google Analytics segments lets you use exclude but that defeats capturing the blog sessions.

Some background as to why I am approaching it like this. My reporting currently looks at all sessions excluding blog visits. Which gives a good picture of shopping intent but does nothing to help understand the blog's performance. I want a user based segment that captures those who have at some point visited the blog and then have viewed any non blog page. That way I can calculate the amount of sessions who have viewed both blog and non blog against my original segment that only captures non blog.

I think you want to treat a visit to your blog as an Event.
[support.google.com...]

Make "visited blog" similar to "watched video", so you can do the reporting you want.
It should be an easy thing to figure out how to embed Event triggers in just your blog pages.

Noodle around in here, see if it might work for you:
[support.google.com...]

Interesting, I will look into that. Thank you!

Hey rwilson, can you tell me why a GA users segment for users that have seen both a blog page and a non-blog page wouldn't work? You could even set up them as a sequence (blog must have preceded non-blog) if you want to assess how your blog is leading to general site traffic.

Technically, that is what I want. It's the matching the non blog pages that I'm struggling with. How do I match all pages except blog for that second part of the sequence?

Wouldn't it be something like
Filter
Users
Include
Page contains /blog/
AND
Page does not contain /blog/

?

Interesting .... I tried this as a Session segment and the results looked right. Then I changed it to a Users segment and the preview went to zero. That doesn't make sense; the Users segment probably should be a little larger than the Sessions segment. Can't figure out why it didn't work as a Users segment!

I think you should also consider using Content Grouping.

See Analytics / Admin / View / Content Grouping.

And see here:
[support.google.com...]

And here:
[moz.com...]

I know you're leaning towards Segments, but the issue I have there is the Segments can either be a subset of users, OR a subset of sessions. And I often see analysts make the mistake of forgetting this, and they slice data in very awkward ways, deriving insights that are nonsense. If you do use Segments, be careful about whether you're slicing users or sessions into subsets. :-)

RhinoFish, in this particular instance I'm trying to take advantage of segments collecting users. So those users would have sessions on the blog and sessions on non-blog. If I had content grouping set up this would likely make life easier. I could just match all content groups aside from the blog.

cgrantski, I get what you're going for but, I don't think it's working for me either. I think that mostly cancels itself out.

Content grouping used in a segment is probably the ideal route here.

It might be canceling out when the segment is users, but it works perfectly for a sessions segment. Logically, a user segment should be treating all activity like one big session, so it working correctly for one and not the other suggests a bug with user segments.

I like the Content Grouping approach too.