Skip to main content
A
Anonymous
April 16, 2013
Solved

Marketo smart list does not recognize URL on website avialble only to logged in users

  • April 16, 2013
  • 5 replies
  • 2031 views
Hi,

I want to use a URL that is available only to logged in users on our website to trigger a campaign.

I'm not able to activate the campaign because there is warning displaye din the smrt list.

Does Marketo recognize only public facing URLs on the website?

Thanks
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jep_Castelein2

Jennifer: remove the "http://" from the URL you type in. If it still doesn't recognize it, verify that that internal page has the Munchkin tracking code installed. If that still doesn't work, activate the campaign with another URL and change the URL with the Campaign activated (of course: make sure the URL is correct, and test it afterwards to see that it works). 

@Elliott: I'm fairly sure that HTTPS Munchkin article you reference is outdated. You can use the standard munchkin on HTTPS pages nowadays. 

5 replies

A
Anonymous
April 17, 2013
Thanks Jep, Steven and Elliot!
A
Anonymous
April 17, 2013
Jep - now that you mention it, we did use the standard munchkin code on our community pages which are HTTPS. Someone should remove that help article.  :0/

Jep_Castelein2
Jep_Castelein2Accepted solution
New Participant
April 17, 2013

Jennifer: remove the "http://" from the URL you type in. If it still doesn't recognize it, verify that that internal page has the Munchkin tracking code installed. If that still doesn't work, activate the campaign with another URL and change the URL with the Campaign activated (of course: make sure the URL is correct, and test it afterwards to see that it works). 

@Elliott: I'm fairly sure that HTTPS Munchkin article you reference is outdated. You can use the standard munchkin on HTTPS pages nowadays. 

A
Anonymous
April 17, 2013
You need to use a different munchkin code on HTTPS (SSL) pages.  The HTTPS Munchkin help article describes this.
A
Anonymous
April 16, 2013
It sounds like an unrelated issue. Troubleshooting:
  1. Check and fix the warnings in the smart list
  2. If the issue persists, delete the smart campaign and create a new one
Terms & ConditionsAccessibility statement

Loading footer...