This plugin hasn’t been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Subscriber Inbound Traffic Tracker

Description

THE PROBLEM

I can’t directly attribute traffic to my subscribers because they aren’t segmented in my web analytics.

Why? Subscribers coming from offline applications get categorized under “(direct) ((none))” in Google Analytics. I can’t simply attribute “(direct) ((none))” to only subscriber traffic because “(direct) ((none))” could include browser bookmarks, direct URL entry, or other apps (such as Twitter apps).

THE SOLUTION

Automatically tag my RSS permalinks with UTM campaign tags. Then my subscriber traffic will automatically be segmented in Google Analytics!

Screenshots

  • This is what it looks like in Google Analytics (a small screenshot taken from a portion of my blog's day :))

Installation

  1. Upload track_subscriber_traffic.php to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress

FAQ

Why should I use this?

Because you want to track how much traffic is attributed to your feeds and what subscribers do on your site.

How does it work?

Splices some Google Analytics campaign tags into your RSS permalinks automatically. Keep reading if that didn’t make sense 🙂

What is Google Analytics

A free service from Google that tracks your visitors. See Google Analytics page for information and to signup.

What is Google Campaign Link Tagging?

Attaching parameters to a URL that tell Google specific information about a visitor. See this blog post for a helpful explanation.

Will this mess up my analytics?

Not really. Google Analytics keeps campaign tracking under a separate category. Choose “Campaigns” on the left-side navigation inside Google Analytics.

Contributors & Developers

“Subscriber Inbound Traffic Tracker” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.0

  • This blog was published at this version.