From b77da57fc5f596ef3e5eaea206f919b22002990f Mon Sep 17 00:00:00 2001 From: Thomas Steur Date: Sun, 14 Sep 2014 17:38:11 +0200 Subject: refs #4996 in case we are in an overlay session we should not track. Check could be maybe moved to trackCallback in general? --- misc/internal-docs/content-tracking.md | 2 -- 1 file changed, 2 deletions(-) (limited to 'misc/internal-docs') diff --git a/misc/internal-docs/content-tracking.md b/misc/internal-docs/content-tracking.md index f09a237aa1..37cadc0005 100644 --- a/misc/internal-docs/content-tracking.md +++ b/misc/internal-docs/content-tracking.md @@ -429,8 +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 -* Would content impressions be tracked in overlay session? - * Overlay session should not trigger a content impression * Cache allowed site urls for redirects * 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 -- cgit v1.2.3