Kapost analytics often aren't the same as Google's. Here's a quick explanation as to why this is and what parts of your content this impacts. We do not intend to replace Google Analytics, but we do record our analytics slightly differently and seek to provide unique data that Google Analytics doesn't.
Google Analytics Versus Kapost:
To recap: If you do a URL to URL comparison between Kapost and Google Analytics, Kapost should be the same. However, Google Analytics track more pages than we do (because of where their analytics code is on the site itself, we just TRACK that one page) so they capture more page views. In Kapost, we only capture the pages you publish whereas Google captures many more such as your homepage so their number will always be higher.
In terms of what you care about, there's a lot Kapost provides that GA doesn't. Here's more of a breakdown.
- For each individual piece of content, the page views for Kapost and GA should be the same. You could look in Kapost or at GA.
- For aggregate views of how your website, as a whole, is doing, in terms of page views and uniques, then GA is a better place to look as it is more comprehensive (since the code is installed on the whole site, we just install on that individual blog post because we want to track how and where it's shared).
- For stats around links pointing back to your content, both Kapost and GA have this data. However, we do some things beyond just listed the URL such as (a) providing the name of the site, (b) categorizing it as social, search or website, (c) storing over time how many links a site has provided so you can see aggregate number.
- For engagement stats such as Facebook and LinkedIn, we capture this data for each piece of content and it will reveal how and where your content is being shared and interacted with. GA doesn't provide this information or a breakdown of social channels and how your content is being consumed across the web.
- For aggregate content stats such as best author, best categories, best business unit, persona, buying stage, etc. - this is all in Kapost and not in GA. The more custom fields you add in Kapost, the more you can slice and dice.
- Kapost shows how your content is doing in production. In the "Grid" view in the analytics you can slice and dice to see where you have holes, which content isn't being produced enough, which content types, which authors are doing the most, etc. GA doesn't provide this view.
- If you use marketing automation, Kapost provides interesting lead generation stats for any client that connects either Marketo or Eloqua into Kapost for another deeper ROI layer of stats. We also provide on each piece of content whether it was the first-touched or last-touched content before that user became a lead. GA doesn't do this.
To sum up:
- The only issue is between page views if you see a difference with GA and Kapost.
- This issue is not an issue on the individual page - only on the aggregate page
- The aggregate page is an aggregate of content pages and not all other pages