Wistia videos not tracked despite successful API response | Community
Skip to main content
A
Anonymous
August 25, 2014
Question

Wistia videos not tracked despite successful API response

  • August 25, 2014
  • 3 replies
  • 1160 views
Our Youtube videos are tracked properly with a querystring ?video=play,stop,pause,end.

however, this technique is not working with Wistia videos despite a successful API response.
the Wistia. the video is here on the homepage:
similar.graystyle.hu/knowledgebase/

Here's the succesfful response, it's not registered in the user's activity log, any idea why?

http://891-vey-973.mktoresp.com/webevents/visitWebPage?_mchNc=1408639066762&_mchRu=&_mchQp=video%3Dplay&_mchId=891-VEY-973&_mchTk=_mch-similar.graystyle.hu-1408449796243-46856&_mchHo=similar.graystyle.hu&_mchPo=&_mchPc=http%3A&_mchVr=147&_mchRe=http%3A%2F%2Fsimilar.graystyle.hu%2Fknowledgebase%2F
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

A
Anonymous
August 25, 2014
A couple things to check:
  • Are you sure the call is actually firing for the lead?
  • Are you sure you're checking the right lead in Marketo?
  • If you manually make a visit web page call from the console is that working for you?
A
Anonymous
August 25, 2014
When I look in the console on the page you linked to, I am getting a 200 status from Marketo, and I can't spot any errors in the code.

Was the code below provided by Wistia? 

<script>
  wistiaEmbeds.onFind(function(video){
    video.bind("play", function(){
        var a= Munchkin.munchkinFunction('visitWebPage', {
            url: '',
            params: 'video=play'
        });
        _paq.push(['trackPageView', 'Video-play']);
      return this.unbind;
    }).bind("end", function(){
        var a= Munchkin.munchkinFunction('visitWebPage', {
            url: '',
            params: 'video=end'
        });
        _paq.push(['trackPageView', 'Video-end']);
      return this.unbind;
    });
  });
</script>
 
A
Anonymous
August 26, 2014
Alright we managed to solve it, the URL parameter wsa not delivered for some reason, only the query parameter.
tx 
Terms & ConditionsAccessibility statement

Loading footer...