Automatically tracking shared url from Facebook, as GA already does

You're welcome!

I don't have access to processing rules for now, but will look into it.

In the meantime, I am going to double check all the eVars I have looking for a way to get the info. And sometimes look at GA if necessary.

Thank you so much for your time and effort. This truly helps me understanding how all variables work together.

Yeah. . . you want downstream Page Views. . . I should have caught that. There are a few ways to get it, although I'll admit that none of them is ideal as they involve a bit of work. If you have access to Processing Rules, you could add a rule which says: "If referring domain is facebook.com, set Page Name in eVarN" (where N is the number of any available eVar). This basically reproduces the GA report that you mentioned without segmentation: Instances would equal click-throughs from FB to the page, and Page Views in that report would show all of the downstream Page Views associated with that page. As a bonus, you would be able to associate conversions with that click-through as well. 

I am not sure if I created the segment as you suggested. Here's how it looks :

I also tried without the path length equals 1.

In the pages report, it only gives me the total pages views of that page, not of all the pages in this visit. Could this be achieved by using another report?

Thank you for helping me with this,

Ah, that's a great question. You would probably need to use a separate segment. A Visit container containing the Page View container shown above should give you "downstream Page Views." 

Great, thanks for all those quick anwwers today. I truly appreciate the time and effort you put in making my life easier.

But let's say I want to push this a step further. GA provides the landing page, a visit count (but I prefer Omniture's instances), and total page views of the visit which started from this landing page. The solution you gave me provides page views of this landing page only.

I realize that what I am trying to do is consider those landing pages (from facebook or any other social network) as single campaigns, so I can track what traffic they brought, video views, pages per visit, etc., but withouth having to put a tracking code on every single url that was shared.

Any thoughts on this?

That's what the "Path Length = 1" is supposed to accomplish. It's also very important that you use the Page Views container, not the Visits container, since using Visits would include all subsequent PVs during the visit. 

It seems to work. I just have a quick question relating to this way of getting the info :

It appears that by using that segment and using it in the pages report, I get visits that included this page, not necessarily visits that started with this page. Is this correct?

Actually, come to think of it, you might not want Path Length = 1 in that segment. Some users may click through from a Facebook link multiple times in a visit, and the segment described above would exclude any clicks that did not create a new visit. 

Yes, I think so. Try building this segment: 

Then apply it to the Pages report. Bookmark that report or create a Custom Report and you should be all set. However, I'd like to still see how many people are interested in having this report available out of the box. So your idea is still very interesting, but hopefully you can address the need immediately via workaround!