Are there still any functioning GeoRSS aggregators out there?
I'm basically thinking of a blog aggregator, but specifically one that only indexes posts that have coordinates associated with them.
Related
We have a gtm-tag article_read which include parameters such as
news_id, article_title, news_id and so on.
How can I include a list of categories in the article_read-tag?
The categories are:
Electricity, Refrigeration, Sanitation, Water & sewer, Ventilation and Heat.
Each news-article can have none or several categories.
You want to make these categories available to your GTM. So you either parse every article page to get the categories or ask the front-end to push them to the dataLayer on pageviews, which would definitely be a more robust solution.
Once you have the list accessible through GTM, you want to sort it, say, alphabetically and use that in your event property.
Don't forget to register the property in GA.
Note that analysis on this will be a bit tricky. You'll have to use contains on this dimension. But it's much better than nothing. You would have more options if you did ETL, or if you used a more advanced analytics solution. GA is generally a free product, hence the limitations.
I am getting a little confused as to what is the best way to measure the amount of sessions/visits for which a particular event has happened at least once.
I am reading different options for doing this: via segments or via filters. Which one is the correct one? I am getting different numbers!
In practice I have this section of my site that has these articles people can post and they tag their article with topics/tags. Using GTM I am collecting the topics/tags whenever someone views an article. So I have this event category named "Post view - topics" and in the event label I am listing the topics.
The idea is that I can build dashboards around specific topics (ex. the topic "Analytics") and track how many articles have been viewed, how many visits/sessions led to read an article that concerned that topic, what are the most popular articles for that topic, etc...
The way I've been doing it until now is:
Apply a event-category filter on my data ("Post view - topics")
Apply a event-label filter ("Analytics")
screenshot of my filters
And then build my charts around that filtered data.
I thought this was the right way to do it, but now I'm concerned that this might not be correct, especially when I want to measure the amount of sessions. I am reading (here for instance) that it might be better to use segments?
What do you guys think?
I suggest you to use segments, in this way you can request sessions which have your event category and your event action.
For about a week, Google Analytics was erroneously reporting page views for a few request URIs, severely skewing my data. I have read that there is no way to remove data once it is reported. If this is the case, is there a way to simply hide this data from the view?
I have tried a number of things (such as creating global filters, view filters, etc.) to no avail. Using segments also doesn't work, because apparently you can only filter out visits/users (whereas my goal is to filter out page views associated with a specific page). At this point, I feel like I must be going about it the totally wrong way...
Below is a screenshot of the Behavior > Overview section. The page views I want to move are #1, #2, and #5.
Alex, unfortunately, there is nothing you can do about the historical data.
However, you can use simple filter to exclude pages you don't want to see (the filter field above the report table, not filters related to account/profiles) -- see the attached screen below.
Make sure you select exclude and then pick Page dimension. The easiest way would be to use regular expressions, like:
(a|b|c)
This one would remove any pages that contain either "a", or "b" or "c".
The expression would be probably a bit more complicated in your case and I suggest using tools like RegEx Hero (free, online). I am not sure if there is anything common for the pages you would like to remove from the reports, but regular expression can do quite a lot :).
One last thing -- be aware there is a slight difference in segments and (table) filters. If you use segments for page dimension, you would end up with ALL the pages that were seen during a visit, which includes the page you set in the segment. Might be a bit confusing, but see this article for detailed explanation.
How can one output the difference between two feeds in Yahoo Pipes?
That is to say, I want all the posts from module A which do not occur in module B (filtered by title).
I've found how to get the set union using the Unique operator, but I can't find an obvious operator for getting the set difference.
Example
Let's say a newspaper website publishes two feeds, FrontPage.rss and Politics.rss, and that the most interesting items from the politics feed are also published on the front page feed among other items. We want to subscribe to both feeds separately, and we don't want receive politics articles in our front page feed, because we're already reading them elsewhere. We can subscribe directly to the politics feed, but for the front page feed we actually want all the items from FrontPage.rss except those which also occur in Politics.rss. That is, the set difference of FrontPage and Politics (also known as the relative complement of Politics in FrontPage).
In the operators section you should be able to use the "unique" module to filter based on a unique identifier such as a url.
Put both feeds through a "Union" module, then put the output through a "Unique" module.
I am developing a web application, in which I have the following type of search functionality;
Normal search: where user will enter the search keyword to search the records.
Popular: this is no a kind of search, it will display the popular records on the website, something as digg and other social bookmarking sites does.
Recent: In this I am displaying Recently added records in my website.
City Search: Here I am presenting city names to the user like "Delhi", "Mumbai" etc and when user click this link then all records from that particular city will be displayed.
Tag Search: Same as city search I have tag links, when user will click on a tag then all records marked with that tag will be displayed to the user.
Alphabet Search: Same as city and tag this functionality also has links of letters like "A", "B", .... etc and when user clicks on any letter link then all records starting with that particular letter will be displayed to the user
Now, my problem is I have to provide above listed searches to the user, but I am not able to decide that I'll go with one page (result.aspx) which will display all the searches records, and I'll figure using query string that which search is user is using and what data I have to display to the user. Such as, lets say I am searching for city, delhi and tag delhi-hotels then the urls for both will be as :
For City: www.example.com/result.aspx?search_type=city&city_name=delhi
For Tags: www.example.com/result.aspx?search_type=tag&tag_name=delhi-hotels
For Normal Search: www.example.com/result.aspx?search_type=normal&q=delhi+hotels+and+bar&filter=hotlsOnly
Now, I feels above Idea of using a single page for all searches is messy. So I thought of some more and cleaner Idea, which is using separate pages for all type of searches as
For City: www.example.com/city.aspx?name=delhi
For Tags: www.example.com/tag.aspx?name=delhi-hotels
For Normal Search: www.example.com/result.aspx?q=delhi+hotels+and+bar&filter=hotlsOnly
For Recent: www.example.com/recent.aspx
For Popular: www.example.com/popular.aspx
My new idea is cleaner and it tells specifically everything to the user that which page is for what, it also gives him idea that where he is now, what records he's seeing now. But the new idea has one problem, In case I have to change anything in my search result display then I have to make changes in all pages one by one, I thought that solution for this problem too, which is using user-control under repeater control, I'll pass all my values one by one to user-control for rendering HTML for each record.
Everything is fine with new Idea, But I am still no able to decide that with which I dea I have to go for, Can anyone tell me your thoughts on this problem.
I want to implement an idea which will be easy to maintain, SEO friendly (give good ranking to my website), user-friendly(easy to use and understand for the users)
Thanks.
One thing to mention on the SEO front:
As a lot of the "results" pages will be linking through to the same content, there are a couple of advantages to appearing* to have different URLs for these pages:
Some search engines get cross if you appear to have duplicate content on the site, or if there's the possiblity for almost infinite lists.
Analysing traffic flow.
So for point 1, as an example, you'll notice that SO has numberous ways of finding questions, including:
On the home page
Through /questions
Through /tags
Through /unanswered
Through /feeds
Through /search
If you take a look at the robots.txt for SO, you'll see that spiders are not allowed to visit (among other things):
Disallow: /tags
Disallow: /unanswered
Disallow: /search
Disallow: /feeds
Disallow: /questions/tagged
So the search engine should only find one route to the content rather than three or four.
Having them all go through the same page doesn't allow you to filter like this. Ideally you want the search engine to index the list of Cities and Tags, but you only need it to index the actual details once - say from the A to Z list.
For point 2, when analysing your site traffic, it will be a lot easier to see how people are using your site if the URLs are meaningful, and the results aren't hidden in the form header - many decent stats packages allow you to report on query string values, or if you have "nice" urls, this is even easier. Having this sort of information will also make selling advertising easier if that's what's you're interested in.
Finally, as I mentioned in the comments to other responses, users may well want to bookmark a particular search - having the query baked into the URL one way or another (query strings or rewritten url) is the simiplist way to allow this.
*I say "appearing" because as others have pointed out, URL rewriting would enable this without actually having different pages on the server.
There are a few issues that need to be addressed to properly answer your question:
You do not necessarily need to redirect to the Result page before being able to process the data. The page or control that contains the search interface on submitting could process the submitted search parameters (and type of search) and initiate a call to the database or intermediary webservice that supplies the search result. You could then use a single Results page to display the retrieved data.
If you must pass the submitted search parameters via querystring to the result page, then you would be much better off using a single Result page which parses these parameters and displays the result conditionally.
Most users do not rely on the url/querystring information in the browser's address bar to identify their current location in a website. You should have something more visually indicative (such as a Breadcrumbs control or header labels) to indicate current location. Also, as you mentioned, the maintainability issue is quite significant here.
I would definitely not recommend the second option (using separate result pages for each kind of search). If you are concerned about SEO, use URL rewriting to construct URL "slugs" to create more intuitive paths.
I would stick with the original result.aspx result page. My reasoning for this from a user point of view is that the actual URL itself communicates little information. You would be better off creating visual cues on the page that states stuff like "Search for X in Category Y with Tags Z".
As for coding and maintenance, since everything is so similar besides the category it would be wise to just keep it in one tight little package. Breaking it out as you proposed with your second idea just complicates something that doesn't need to be complicated.
Ditch the querystrings and use URL rewriting to handle your "sections".. much better SEO and clearer from a bookmark/user readability standpoint.
City: www.example.com/city/delhi/
Tag: www.example.com/tag/delhi-hotels/
Recent: www.example.com/recent/
Popular: www.example.com/popular/
Regular search can just go to www.example.com/search.aspx or something.