Project

General

Profile

Enhancement #4563

DDB Widget

Added by Tue Gaston 5 months ago. Updated 3 months ago.

Status:
Need more info
Priority:
Normal
Estimated time:

Description

Med de nuværende statistik-muligheder for DDB Widgetten er vi i stand til at spore:

-Hvor og hvor mange gange widgetten er blevet vist
-Hvor og hvor mange gange den er blevet foldet ud
-Hvor og hvor mange gange den er blevet klikket på

MEN!
Vi mangler at kunne spore, hvor der bliver klikket hen.
Dette forudsætter kode-ændring i selve widgetten.

History

#1 Updated by Tue Gaston 5 months ago

  • Assignee changed from Tue Gaston to Sidsel Andersen

#2 Updated by Tue Gaston 5 months ago

Så vidt jeg har forstået, skal host-header'en indeholde en referer som denne:

... men det gør den ikke.
Her er den på ereolen efter der er navigeret fra litteratursiden vha widgetten:

Se: Ingen referer.

#3 Updated by Tue Gaston 5 months ago

  • Description updated (diff)

#4 Updated by Piotr Birketoft 4 months ago

Dear team,

 

As promissed, here is an explanation of the issue we see, and a best guess for a solution:

 

Currently our challange is that we wish to see what pages users clicked towards from the Widget.

In Web analytics this is done, by looking at the destination pages (the one that users land on) referrer.

So when you go to https://litteratursiden.dk/, open the widget, click on "eReolen", you can see on www.ereolen.dk that that user came from litteratursiden.

Unfortunatly the referrer gets removed when you use the widget (see Tues screenshots above). This means that we have no way of tracking the traffic back to litteratursiden.

 

If you ask me, there are 2 ways of resolving this issue. The most correct one is to "fix" whatever is clearing the referrer in such a way that it once again becomes part of the HTTP headder. My best guess is that its some kind of java script issue in regards to the way the link from the widget is executed.

The second way, and this would be a workaround, is to add 1 more parameter to the link stating where the users came from. This is possible, but not recomendable, as it would eat up 1 more parameter and require implementation on both the website and the WebTrekk end of things.

Please let me know if you have any questions, I will be happy to help.

 

- Piotr

#5 Updated by Tue Gaston 3 months ago

  • Status changed from Ready for development to Need more info
  • Assignee changed from Sidsel Andersen to Piotr Birketoft

Also available in: Atom PDF