diff options
| author | Thomas Steur <thomas.steur@googlemail.com> | 2014-09-15 16:13:06 +0400 |
|---|---|---|
| committer | Thomas Steur <thomas.steur@googlemail.com> | 2014-09-15 16:13:06 +0400 |
| commit | 3ba8453c121521586345f36258f99cd4e27b6a25 (patch) | |
| tree | 2a5e3fc7609e493cb775401c39946f66771bcda8 /misc | |
| parent | 76cef69bee1727ca5a165810594476584e6bdd62 (diff) | |
refs #4996 do not fallback to GET if POST fails otherwise we might track twice
Diffstat (limited to 'misc')
| -rw-r--r-- | misc/internal-docs/content-tracking.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/misc/internal-docs/content-tracking.md b/misc/internal-docs/content-tracking.md index dcddee78a0..503252dbb8 100644 --- a/misc/internal-docs/content-tracking.md +++ b/misc/internal-docs/content-tracking.md @@ -429,9 +429,6 @@ Yes it seems most logical to create an action entry for each Content. Nothing special here I think. We would probably automatically detect the type of content (image, video, text, sound, ...) depending on the content eg in case it ends with [.jpg, .png, .gif] it could be recognized as image content and show a banner in the report. ## TODO -* When a user clicks on an interaction, we should check whether we have already tracked the impression as the content is visible now. If not tracked before, we should track the impression as well - * There can be a scroll or timer event that detects the same content became visible as well. This would not be a problem since we do not track same content block twice - * Maybe v2 * Content piece undefined vs Unknown? * UI / PHP tests @@ -442,6 +439,11 @@ Nothing special here I think. We would probably automatically detect the type of * We need to check all parent elements of a content block whether it is scrollable and if so connect an event to this * We could have in V2 or V3 an attribute data-content-interaction="submit" to tell Piwik to listen to the submit event and to use "submit" as an interaction * Provide more reports like which interactions, which targets, and more possible +* Do not track the same interaction twice unless trackPageView is called? + * For instance if target=_blank used interaction would be tracked multiple times currently + * Alternatively provide "interactions" and "unique interactions" +* When a user clicks on an interaction, we should check whether we have already tracked the impression as the content is visible now. If not tracked before, we should track the impression as well + * There can be a scroll or timer event that detects the same content became visible as well. This would not be a problem since we do not track same content block twice ## Open questions |