Web page visit on Activity Log not showing

[Anonymous]

Why isn’t the web page where an email takes a lead showing up on their Activity Log? I thought it was just because the user's cookies were turned off, but even with internal testing we find that sometimes the webpage that is visited is not recorded in the Activity Log (and cookies are definitely on for those test leads, as they appear in some record's Activity Log).

What else should I be checking into setting-wise to make sure this is being recorded?

It's currently like we can see that someone was delivered an email, opened the email, clicked on the email, and then filled out a form. But if we run reports on who visited that page (where the form lives), nothing is showing up b/c it is not being recorded in the Activity Log.

Thanks for the help.

[SanfordWhiteman]

Is Munchkin (correctly) loading on the website?  Post the URL and I can check it out.

Open Email, Click Email, Filled Out Form will all be logged without Munchkin.  Visit Web Page and Click Link require Munchkin.

[Anonymous]

That's the other thing - I see that it automatically changes program status to "sent" when the email is sent. But if the lead opens or clicks on the email, the program status isn't changed until I have a campaign set up telling it to change. Is that normal for an email program?

Here's an example of a page where the activity log is sometimes not recording the "visited web page." http://dh2i.com/failover-clusters-in-the-cloud/

Thanks!

[Grégoire_Miche2 · Accepted solution]

And again, the munchkin you are using code is weird.

it should be :

<script type="text/javascript">

(function() {

  var didInit = false;

  function initMunchkin() {

    if(didInit === false) {

      didInit = true;

      Munchkin.init('613-YHR-953');

    }

  }

  var s = document.createElement('script');

  s.type = 'text/javascript';

  s.async = true;

  s.src = '//munchkin.marketo.net/munchkin.js';

  s.onreadystatechange = function() {

    if (this.readyState == 'complete' || this.readyState == 'loaded') {

      initMunchkin();

    }

  };

  s.onload = initMunchkin;

  document.getElementsByTagName('head')[0].appendChild(s);

})();

</script>

while your's is just :

<!-- marketo munchkin tracking plugin by 10up: www.get10up.com -->

<script src="http://munchkin.marketo.net/munchkin.js" type="text/javascript"></script>

<script type="text/javascript">mktoMunchkin("613-YHR-953");</script>

Sincerely, I would not trust the "www.get10up.com" to provide a decent Marketo tracking code.

[John_Danielson1]

Hi Gregoire,

Why would some leads capture the Visited Web Page activity while others do not? We recently created a new landing page (non-Marketo LP) for an upcoming marketing campaign and I have been testing the form on the page. When I look at my test leads, there is no activity that shows they visited the page. It just starts with 'Filled Out Form.' I just checked it again and now there are 3 leads appearing. Someone had accidentally made the page live on our site so a few of our known users went to it and I can see it in their Activity Logs. I attempted to go to the page again and I still don't see any activity for 'Visit Web Page' in my test leads. I checked the munchkin code and compared it to what you have above and it is identical (except for the Account ID). Is there any reason some leads capture this activity while my test leads don't?

Thanks

John

[Grégoire_Miche2]

Hi John,

Better ask a new question than continuing an old thread You will be much more likely to get a quick answer.

There might be quite a few reasons.

1. If this happens when you are testing, this is probably because there is a mix in cookies. You start navigation with a Marketo cookie, attach to a lead (the last one which which you filled out a form) in the DB, the you will out a form with a different email address. A new lead is created, a new Mkto cookie value is issued, but all previous navigation is attached to the previous lead
2. If you navigate from one domain to another when moving from your web site to Marketo LP's, as cookies cannot be shared accross domains, the navigation on your web site is usually attached to an anonymous lead in the DB
3. On 2 letter TLD domains, (eg. .fr, .de, ...), if the munchkin code you use is the default Marketo one, it is likely that you will hit a well know bug by which the cookie is placed at sub domain level (e.g. www.mydomain.fr and pages.mydomain.fr, in which case your web site and your Marketo LP do not share cookies.

-Greg

[Anonymous]

Thanks, Grégoire. I will talk to our web team about some of those mistakes and also the munchkin code that we are using. Perhaps that is contributing or causing our problems.

The reason we can't embed the Mkto forms and instead are using iframes is that we want to use the "prefill" function - like where the form would fill out the lead's name, etc. for them when they are returning users. That function doesn't work on embedded forms but only on Marketo forms on Marketo pages, I was told.

[Grégoire_Miche2]

Hi again Alison,

This is correct, embedded forms do not allow for prefill.

Why are'nt you just using a Marketo LP instead. You page is not that complex and creating a Marketo guided LP template should not be a big deal and would a better job 🙂

-Greg

[Anonymous]

Good point - that is another option we'll have to consider!

Thanks.

[Grégoire_Miche2]

Hi again Alison,

Just tested you page, and the Marketo code seems to be loaded correctly. But the page html code is not complete. The </body> and </html> tags are missing, as well as may be one </div>. Plus there are quite a few html mistakes in the code (such a <img> not closed.

These may explain the fact that the page does nor execute correctly on certain bowsers.

Also, you should avoid iframes for Marketo forms and use embedded forms instead.

-Greg

[Grégoire_Miche2]

Hi Allison,

Program statuses never change automatically. YOu will need to add a trigger campaign set as is :

• trigger : email is sent (equals [your email])
• flow : change program status -> email sent

And activate it.

[Anonymous]

Ok, that makes sense. I guess it's just setting the status to "sent" automatically b/c that is the default/lowest-level status that a member can have in that email program. If we want to set additional statuses, I'll have to create that trigger campaign.

Thanks, Grégoire!