<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Glide Technologies Blog &#187; journalist communication</title>
	<atom:link href="http://blog.glidetechnologies.com/tag/journalist-communication/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.glidetechnologies.com</link>
	<description>Our blog on digital PR, corporate communications, social media and measuring social media</description>
	<lastBuildDate>Tue, 17 Jan 2012 20:18:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='blog.glidetechnologies.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>Glide Technologies Blog &#187; journalist communication</title>
		<link>http://blog.glidetechnologies.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://blog.glidetechnologies.com/osd.xml" title="Glide Technologies Blog" />
	<atom:link rel='hub' href='http://blog.glidetechnologies.com/?pushpress=hub'/>
		<item>
		<title>Who’s the real culprit here?</title>
		<link>http://blog.glidetechnologies.com/2010/01/11/who%e2%80%99s-the-real-culprit-here/</link>
		<comments>http://blog.glidetechnologies.com/2010/01/11/who%e2%80%99s-the-real-culprit-here/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 17:12:46 +0000</pubDate>
		<dc:creator>Glide Technologies</dc:creator>
				<category><![CDATA[Our thoughts and musings]]></category>
		<category><![CDATA[glide technologies]]></category>
		<category><![CDATA[journalist communication]]></category>
		<category><![CDATA[media database]]></category>
		<category><![CDATA[pr software]]></category>

		<guid isPermaLink="false">http://www.blog.glidetechnologies.com/?p=116</guid>
		<description><![CDATA[Following on from my last post on how journalists are becoming increasingly frustrated at the levels of PR Spam they receive, we now dig a little deeper to find out who the real culprits of this mega spam are. Whilst &#8230; <a href="http://blog.glidetechnologies.com/2010/01/11/who%e2%80%99s-the-real-culprit-here/">Continue reading <span class="meta-nav">&#8594;</span></a><img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.glidetechnologies.com&amp;blog=23279804&amp;post=116&amp;subd=glidetechnologies&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>Following on from my <a href="http://www.blog.glidetechnologies.com/press-releases-%E2%80%93-can%E2%80%99t-live-with-them-can%E2%80%99t-live-without-them/">last post</a> on how journalists are becoming increasingly frustrated at the levels of PR Spam they receive, we now dig a little deeper to find out who the real culprits of this mega spam are.</p>
<p>Whilst it’s true that if you are in the media it comes with the territory but what we’re talking about is a level and frequency of PR spam that is doing nobody any favours.  And whilst it’s also true that ultimate responsibility for sending spam is down to the person who hits the ‘send’ button, we must also not overlook the role that the <a href="http://www.glidetechnologies.com/pr-products/glide-pr/Index.aspx" target="_blank">PR software</a> industry has to play in the whole process.  (Yes, that’s us)</p>
<p>Unlike most of our competitors, we don’t create media lists ourselves.  Instead, we prefer to partner with providers of lists so clients have more control over their contacts (we partner with PR Newswire and Gorkana, two of the more responsible and accurate list providers). However, barely a day goes by without us getting an enquiry from someone asking us if they can get media lists from us and how much they cost.</p>
<p>This is because many PRs see lists as a quick and easy (and lazy!) way to get a release out and get at least some coverage to show their boss (or client).  Maintaining a proper CRM, analysing click-through rates and providing a proper opt-in/opt-out process or (heaven forbid!) actually creating a journalist-friendly media centre all seems too much like hard work.</p>
<p>When we explain we don’t offer a media database only solution, it tends to be a case of ‘oh never mind, I just want a database [so I can send out my email to 1000 people]’.</p>
<p>What’s happened recently is that media lists are becoming cheaper due to two main factors</p>
<p>1)    the outsourcing of the management of these lists to places with cheaper labour costs<br />
2)    (far more worrying) the use of bots to scrape profile information from the web (badly) to create automated ‘profiles’ of journalists and bloggers based on the content they write for their online publications and blogs.  This can also include LinkedIn and other online personal profiles.</p>
<p>This means that more junior and part-time PR people can get their hands on them without having the rest of the PR skillset that’s needed to make the right use of what can be a very powerful tool.  And as a result, the level of PR spam has increased.</p>
<p>Many of our clients are large companies with large PR teams so we’ve seen how, in the hands of an experienced PR practitioner, lists can be a really useful instrument in a PR’s toolbox.</p>
<p>In the case of some list providers it’s also very difficult for journalist/bloggers to remove themselves from the central list, having instead to go to each sender individually.</p>
<p>Sadly it’s also often the case of quantity not quality when it comes to shopping for media databases (from the perspective of someone who speaks to people wanting to buy such lists).  “How many contacts do you have for topic X in country Y?”  “oh, never mind then, that other provider said they had 2,000.”  Oh dear.<br />
<strong><br />
What can be done?</strong></p>
<p>Seeing the frustration that still exists is quite disheartening.  Where technology should be used to ease communications between PRs and the media (and this is certainly our philosophy) in many cases, it’s only serving to exacerbate the problem by making it even easier for PRs to continue their bad habits.</p>
<p>A lot of what needs to be done rests with the PRs themselves. What I want to do here is list a few suggestions from the perspective of a web technology provider:</p>
<p>Integrate your email distribution strategy with your website/media centre!</p>
<p>This makes it much easier to:</p>
<p>1)    <strong>Let journalists/bloggers opt-in themselves</strong>. If you get coverage for something you’ve done quite often other journalists and/or bloggers will read it and may want to know more about what you are doing in the future.  Providing RSS, the ability to subscribe via email, or receiving updates via twitter, means the journalist is in control of how and what information they receive from you.</p>
<p>2)   <strong>Let journalists/bloggers opt out.</strong> Every email sent should have an automated process for the journalist to modify what kind of information they want to receive or remove themselves entirely.  Having a manual unsubscribe process also makes more work the PR, so automate if you can.</p>
<p>3)    <strong>Allow the journalist to see what profile you have for them.</strong> If you integrate parts of your CRM with your website when you distribute an email, the journalist can see for themselves what you think they are interested in.  If the journalist is able to easily clarify what information they want this will make both your lives easier.</p>
<p>4)  <strong> Track what journalists are doing with the information you send them. </strong>Technology exists now that let’s you see whether journalists are opening your emails and even what they are clicking on.  If you’re repeatedly sending out emails that have very low open rates or you’re sending releases to journalists that never open what you’re sending them you’re probably doing something wrong!</p>
<p><a href="http://themediablog.typepad.com/the-media-blog/2010/01/kevin-braddock-.html?cid=6a011570c131b2970c0120a7a9df09970b#comment-6a011570c131b2970c0120a7a9df09970b" target="_blank">Fran Molley</a> says “I applaud PR companies that keep good databases and target their releases more effectively. CRM technology is so easy &amp; cheap these days, I don’t understand why it isn’t a fundamental part of every PR&#8217;s toolkit.”  Well, Fran, neither do we!  Point people our way and we’ll sort them out </p>
<p>If any journalists or PRs reading this have ideas for how a PR software provider like us can help in this we’d love to hear your thoughts.</p>
<p>Alistair</p>
<br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/glidetechnologies.wordpress.com/116/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/glidetechnologies.wordpress.com/116/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/glidetechnologies.wordpress.com/116/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/glidetechnologies.wordpress.com/116/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/glidetechnologies.wordpress.com/116/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/glidetechnologies.wordpress.com/116/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/glidetechnologies.wordpress.com/116/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/glidetechnologies.wordpress.com/116/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/glidetechnologies.wordpress.com/116/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/glidetechnologies.wordpress.com/116/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/glidetechnologies.wordpress.com/116/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/glidetechnologies.wordpress.com/116/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/glidetechnologies.wordpress.com/116/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/glidetechnologies.wordpress.com/116/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=blog.glidetechnologies.com&amp;blog=23279804&amp;post=116&amp;subd=glidetechnologies&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://blog.glidetechnologies.com/2010/01/11/who%e2%80%99s-the-real-culprit-here/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/2ab241a5264482a1ec781acaca9d6c9b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">blogglide</media:title>
		</media:content>
	</item>
	</channel>
</rss>
