Content Metadata and Tagging


Guidelines and recommendations for setting up content tags and metadata to make the most of your reporting dashboard.


The idea behind having tags, authors, and categories as arbitrarily fillable arrays is to give publishers the flexibility and power of using their current and unique taxonomies within the SimpleReach ecosystem. We strongly recommend including as many of these fields as possible in order to take full advantage of our content tracking capabilities.

Custom dashboards can be created from tags, categories, and authors. Tags are especially important to include, as taxonomy is always growing and changing, so they are the best choice for the creation of custom dashboards. Need a dashboard for all content tagged 'Obama 2013'? Go for it. How about a custom dashboard for 'cute puppies'? Done.

If your site doesn't have tags, we strongly recommend using categories or channels instead, as we can create custom dashboards from channels as well.

If your site doesn't have channels or categories, we recommend passing back the field in the top navigation bar that corresponds to the content piece. A piece of content about football would typically be under 'Sports' in the navigation bar. If you have sub-categories, we recommend passing those along as well for more granular reports.


We've seen a number of scenarios in which tagging is used for more than simply adding metadata to a piece of content. Some of the most common approaches are:

Category-based hierarchy: In this scenario, in addition to the tags specific to a content piece, more general terms in the hierarchy are also used. For instance, instead of tagging an article Giants, you may also want to add, NFL and NFL::Giants to ensure that you can search, filter, and create campaigns for content pieces that are specifically about the NFL Giants and not the MLB Giants.

Ad-slot Filtering: If you know what ad slots are used on various article template pages, you can use a tagging structure to group pieces of content with specific ad slots. For example, by adding a tag of slot::300x250-right_rail you can see how all content pieces with a 300x250 right rail are performing.


For sponsored content, we recommend the following:

Static Tagging: On each and every piece of sponsored content, add a static sponsored tag to the SimpleReach __reach_config tags array. This ensures that both realtime dashboards and reports are available for all of your sponsored content at an aggregate level.

Brand Tagging: Create a tag for each brand that is sponsoring or creating content. For example, if IBM is sponsoring a piece of content, then you should add a tag of ibm to the __reach_config tags array. This ensures that both realtime dashboards and reports are available for all the sponsored content on your site that is written for or by ibm. If there is a chance that non-sponsored content will be tagged with ibm, then refer to the section above on hierarchical tagging and use something more descriptive like sponsored::ibm.

Product Tagging: It's common for brands to also have products associated with them that sponsored content is being written for. In addition to tagging the brand, you can also tag the product with something like sponsored::ibm::predictive-analytics.

Completing all these steps, the __reach_config tag array for this particular piece of sponsored content would look like:

__reach_config.tags = [ 'sponsored', 'sponsored::ibm', 'sponsored::ibm::predictive-analytics' ];