diff options
author | Thomas Steur <tsteur@users.noreply.github.com> | 2014-08-21 18:17:23 +0400 |
---|---|---|
committer | Thomas Steur <tsteur@users.noreply.github.com> | 2014-08-21 18:17:23 +0400 |
commit | 86b23773301a7259f613b3c1d3fb69d8d7feb8dd (patch) | |
tree | 5042d0df2fea7c0ac8db447086394574c26f1388 /misc/internal-docs | |
parent | d079edfc7eaf000e9e9d1f71cf0b7cc12dff6e8c (diff) |
fix plugin name [ci skip]
Diffstat (limited to 'misc/internal-docs')
-rw-r--r-- | misc/internal-docs/content-tracking.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/misc/internal-docs/content-tracking.md b/misc/internal-docs/content-tracking.md index 63dc1762ee..9b031d9a88 100644 --- a/misc/internal-docs/content-tracking.md +++ b/misc/internal-docs/content-tracking.md @@ -3,7 +3,7 @@ This is the technical concept for implementing content tracking. We won't plan anything to death but a little bit of thinking upfront makes sense :) Feel free to contribute and let us know if you have any objections! If your thoughts are not technical please comment on the actual issue [#4996](#4996). ## Naming -* Plugin name: Content +* Plugin name: Contents * Content name - The name of the content visible in reports * Content piece - eg a video file, image file, text, ... * Content target - a clicked url, a started video, any "conversion"... @@ -47,4 +47,4 @@ Of course everything goes kinda in parallel: * Make tracking of impressions work * Make a report work * Make tracking the clicks work -* Piwik.js and tagging of the content of pieces
\ No newline at end of file +* Piwik.js and tagging of the content of pieces |