Forums / Maintenance / Report Problems

27,881 total conversations in 1,745 threads

+ New Thread


Limited timespan choices for Google Trends graph embeds in entries

Last posted Apr 18, 2017 at 10:05PM EDT. Added Apr 18, 2017 at 09:41PM EDT
2 posts from 2 users

Six months ago, there was a bug that affected the embed code for Google Trends graphs. A temporary workaround was made, which changed all affected graphs into graphs that covered a time span from 2004 to present. In many entries, it makes sense. However, other entries don't need graphs with long time spans.

I made the entry for Digg v4. The embedded Google Trends graph is supposed to cover only the weeks before and after Digg's disastrous transition and the resulting movement to Reddit. Data from outside the relevant time period is useless for the article. Also, there are several articles for flash-in-the-pan memes and events (r/place being one of them), where long-period graphs won't make much sense. In similar cases, the graphs generated using only the provided timespan choices fail to demonstrate the notability the subjects. A one-month Google trends graph for r/place, for example, doesn't work as of now. Meanwhile, a 7-day or 1-day Google trends graph for it won't show the moments mentions of the subject peaked.

All possible time range options work, they just aren't provided in the embed helper on KYM.

You can just take the date value from the official Google trends embed code and use it in the time value for the KYM version.

For 6/1/2010 – 12/31/2010 the official embed code shows 2010-06-01%202010-12-31 as the date value. %20 is a space so it's 2010-06-01 2010-12-31.

<div class="google-trends-embed" data-time="2010-06-01 2010-12-31" data-queries="[&quot;reddit&quot;,&quot;digg&quot;]"></div>

Skeletor-sm

This thread is closed to new posts.

Old threads normally auto-close after 30 days of inactivity.

Why don't you start a new thread instead?

Greetings! You must login or signup first!