Campbell et al v. Facebook Inc.

Filing 199

NOTICE by Facebook Inc. Joint Notice of Refiling of Documents Accompanying Class Certification Briefs and Evidentiary Objections (Attachments: # 1 Ex. 1 - Replacement for Dkt. 178-1, # 2 Ex. 2 - Replacement for Dkt. 183-4, # 3 Ex. 3 - Replacement for Dkt. 179-1, # 4 Ex. 4 - Replacement for Dkt. 184-3, # 5 Ex. 5 - Replacement for Dkt. 179-2, # 6 Ex. 6 - Replacement for Dkt. 179-3, # 7 Ex. 7 - Replacement for Dkt. 179-4, # 8 Ex. 8 - Replacement for Dkt. 179-5, # 9 Ex. 9 - Replacement for Dkt. 179-6, # 10 Ex. 10 - Replacement for Dkt. 179-7, # 11 Ex. 11 - Replacement for Dkt. 179-10, # 12 Ex. 12 - Replacement for Dkt. 179-11, # 13 Ex. 13 - Replacement for Dkt. 179-12, # 14 Ex. 14 - Replacement for Dkt. 179-13, # 15 Ex. 15 - Replacement for Dkt. 179-14, # 16 Ex. 16 - Replacement for Dkt. 179-15, # 17 Ex. 17 - Replacement for Dkt. 179-16, # 18 Ex. 18 - Replacement for Dkt. 179-17, # 19 Ex. 19 - Replacement for Dkt. 179-18, # 20 Ex. 20 - Replacement for Dkt. 179-20, # 21 Ex. 21 - Replacement for Dkt. 180-2, # 22 Ex. 22 - Replacement for Dkt. 180-3, # 23 Ex. 23 - Replacement for Dkt. 184-9, # 24 Ex. 24 - Replacement for Dkt. 180-7, # 25 Ex. 25 - Replacement for Dkt. 180-9, # 26 Ex. 26 - Replacement for Dkt. 180-12, # 27 Ex. 27 - Replacement for Dkt. 180-17, # 28 Ex. 28 - Replacement for Dkt. 180-18, # 29 Ex. 29 - Replacement for Dkt. 180-19, # 30 Ex. 30 - Replacement for Dkt. 180-20, # 31 Ex. 31 - Replacement for Dkt. 180-21, # 32 Ex. 32 - Replacement for Dkt. 180-22, # 33 Ex. 33 - Replacement for Dkt. 180-23, # 34 Ex. 34 - Replacement for Dkt. 178-5)(Chorba, Christopher) (Filed on 6/15/2016)

EXHIBIT 5

From:

Sent:
To:

Cc:
Subject:

on behalf of Alex Himel
Friday, February 11, 2011 6:54 PM
Kristin Thayer
Aryeh Selekman;
Re: [fdn-insights] URL stats for Demand Media

FYI, new realtime insights supports top 10 right now, and will support top 100 after adding pagination to the UI.
http://www.intern.facebook.com/insights/?sk=lt 10150102618235061
(add yourself to insights_dashboard gatekeeper if you do not see this)
-Alex
On Feb 11, 2011, at 2:41 PM, Kristin Thayer wrote:
>Thanks Jonathan!!

>
>-----Original Message----> From: Jonathan P. Hsu
> Sent: Friday, February 11, 20111:54 PM
>To: Jonathan P. Hsu; Kristin Thayer;
> Cc: Aryeh Selekman
>Subject: RE: URL stats for Demand Media

>
> It came back, but I had forgotten to cast it... Try this ...

>
>from dim_shares
>select ds, url, tracking_info, cast(split(tracking_info,',')[O] as
>int) as shares where ds>'2011-02-03' AND ds<'2011-02-10'
>and url like '%ehow.com%'
>and split(tracking_info,',')[0]<1000000
>order by shares desc limit 1000

>
>it takes about 40 minutes ...

>
>~~~~~~~~~~~~~~~~~~

>From: Jonathan P. Hsu
> Sent: Friday, February 11, 20111:50 PM
>To: Kristin Thayer;
> Cc: Aryeh Selekman
>Subject: RE: URL stats for Demand Media

>
>Currently, the only thing that shows metrics for several urls from a single domain ala link.getStats is in the "most liked
and shared" list in Insights.

>
> http://www.dev.facebook.com/insights/?sk=do 10150102618235061

>
>Other than that, the data is scraped into dim_shares but is not currently collected into mysql in any fashion ...

>
> Unfortunately also, dim_shares has share objects from re-sharing that
>are separate from the initial share event and don't have these

Highly Confidential

FB000008489

>numbers. In any case, what you want is the tracking_info field for
> urls in dim_shares where the tracking_info field isn't holding an
> fbid. The easiest way is something like this

>
>from dim_shares
>select url, tracking_info, split(tracking_info,',')[O] as shares where
> ds='2011-02-05'
>and url like '%ehow.com%'
>and split(tracking_info,',')[0]<1000000
>order by shares desc limit 100

>
>The split() clause is there to ensure that you're only looking at original share objects which have the share tracking
numbers in tracking_info.

>
> For those rows, tracking_info contains these numbers in a comma delimited string ...

>
> share_count, post_count, like_count, comment_count, click_count

>
>This query takes a very long time because the table is too big. I started running it, but it hasn't come back yet ...

>
>
>
>
>
>
>
>~~~~~~~~~~~~~~~~~~

>From: [e-mail]
>[
] On Behalf Of Kristin Thayer
>[
]
> Sent: Friday, February 11, 201111:58 AM
>To:
> Cc: Aryeh Selekman
>Subject: [fdn-insights] URL stats for Demand Media

>
>Is it possible to get daily data, for each URL in a domain (cracked.com, ehow.com, and livestrong.com), of the
cumulative stats that are exposed in link.getStats:

>
> https://api.facebook.com/method/links.getStats?
> urls=http%3A%2F%2Fwww.ehow.com%2Fhow_7739881_make-chocolate-valentines
>-day-candy.html&
> access_token= ...

> {
>
>
>
>
>
>

"url": "http://www.ehow.com/how 7739881 make-chocolate-valentines-day-candy.html",
"normalized_url": "http://www.ehow.com/how 7739881 make-chocolate-valentines-day-candy.html",
"share_count": 4,
"like_count": 24,
"comment_count": 17,
"total_count": 45,

> }
>l
>
>

Highly Confidential

FB000008490

> Please let me know if you need more information.

>
>Thanks,
> Kristin

>
>
> kristin thayer

I platform partnerships I facebook

>*
>
>

*
* 1601 s. california ave Ipalo alto Ica 94304

>
>

Highly Confidential

FB000008491