Closed mhkeller closed 9 years ago
will check on this after refreshing finishes
Refreshing fixed it.
I'm still getting them. It looks like there were just two bad articles from migration. You can find them with this query:
select *
from content_metric_summary
where content_item_id in (
select content_item_id from (
select content_item_id, (metrics->>'ga_exits')::numeric as ga_exits
from content_metric_summary
where org_id=2
) t
where ga_exits < 0
);
as you can see, the per_2_5
field is still positive:
if they aren't like that in GA, wouldn't the refresh take care of it?
On Sat, Sep 12, 2015 at 7:23 AM, Brian Abelson notifications@github.com wrote:
as you can see, the per_2_5 field is still positive:
[image: screenshot 2015-09-11 18 23 19] https://cloud.githubusercontent.com/assets/1621721/9827657/4487fb6e-58b2-11e5-9928-1147ff22ff66.png
— Reply to this email directly or view it on GitHub https://github.com/newslynx/opportunities/issues/125#issuecomment-139675657 .
@mhkeller mhkeller.com
my thought was that it was bad data from the prototype that hadn't been overwritten.
k, i might delete those content items and re-add them manually