We collect all content were any of our widget script is placed. All content for the head domain is stored in a big bucket and no filtering is possible in this stage.
When content is collected we can then filter it in different ways. On some sites the best solution is to combine different filtering types. Sometimes we use separate widgets for the top 10 biggest blogs in a network and use same widget with script filter for the rest.
Filter with many widgets (Statistics separated)
If a site has multiple subdomains, we can set up a widget to display content from one single sub-domain, multiple, or all sub domains simultaneously. Then we create one channel for each subdomain to separate the statistics.
Filter in script (Statistics not separated)
The customer can also choose content to display in the widget. They can do this by adding source code in the script. You can select the source by adding the main or sub domain.
<div data-spklw-source = "Widget-1122334455" data-spklw-source = "strossle.com"> </ div>
<script src = "http://widgets.sprinklecontent.com/v2/sprinkle.js" async> </ script>
<div data-spklw-source = "Widget-1122334455" data-spklw-source = "blog.strossle.com"> </ div>
<script src = "http://widgets.sprinklecontent.com/v2/sprinkle. js "async> </ script>
This is good for big networks where the customer wants same widget design on many sites, but just want different content for each.
Custom filters (Only latest, Most shared, Statistics not separated)
In some cases, we can filter content based on elements in url or meta tags in the code.
Some sites have category name in the url
Some sites have category in metatag (We can ask publisher to place this if it does not exist)
<meta property="og:type" content="fotboll"/>
Then we can in a separate widget add custom filter /football/ and only show that category. But in these cases, you can only show content from one category.