Skip to main content
yunseng94
Level 2
Oct 27, 2022 9:31 AM UTC
Solved

Visited web page filter [starts with]

Hi everyone, basically I have a website example.com/software/procurement/ and I have a smart list with filter of "Visited web page" [starts with]: example.com/software/ ONLY. May I know if my smart list is still able to capture anyone if they visited example.com/software/procurement/ ??

 

Looking forward for your favorable reply.

 

Thanks in advance.

Darshil_Shah1
Darshil_Shah1Accepted solution
Adobe Champion, Community Advisor, UG Leader
Oct 27, 2022 10:35 AM UTC

Yes, your SL should be able to capture any web page hits starting with the "https://example.com/software/" string in the constraint, and the link "https://example.com/software/procurement/"  does start with what you have in the SL.

 

The "contains" operator is a superset of the "starts with" operator. If the link that you want to trigger off the campaign upon web page visit is always guaranteed to start with a value, then you can very well use the "starts with" operator. And AFAIK, "contains" is always the slowest of all the operators. 🙂

 

View in thread

7 replies

Disha_Goyal6
Community Advisor
Disha_Goyal6Community Advisor
Community Advisor
Oct 27, 2022 10:25 AM UTC

Hi @yunseng94,

 

If you use 'contains' in place of 'starts with' works better.

 

Thanks,

Disha

Translate
    yunseng94Author
    Level 2
    Oct 31, 2022 1:46 AM UTC

    Thanks for the suggestion Disha

    Translate
      Darshil_Shah1
      Adobe Champion, Community Advisor, UG Leader
      Darshil_Shah1Adobe Champion, Community Advisor, UG LeaderAccepted solution
      Adobe Champion, Community Advisor, UG Leader
      Oct 27, 2022 10:35 AM UTC

      Yes, your SL should be able to capture any web page hits starting with the "https://example.com/software/" string in the constraint, and the link "https://example.com/software/procurement/"  does start with what you have in the SL.

       

      The "contains" operator is a superset of the "starts with" operator. If the link that you want to trigger off the campaign upon web page visit is always guaranteed to start with a value, then you can very well use the "starts with" operator. And AFAIK, "contains" is always the slowest of all the operators. 🙂

       

      Translate
        yunseng94Author
        Level 2
        Oct 31, 2022 1:49 AM UTC

        Hi Darshil, appreciate for your reply and your explanation on "starts with" filter. I believe you made a typo on the first link (should be  example.com/software/ ? ) 😃

        Translate
        Darshil_Shah1
        Adobe Champion, Community Advisor, UG Leader
        Darshil_Shah1Adobe Champion, Community Advisor, UG Leader
        Adobe Champion, Community Advisor, UG Leader
        Oct 31, 2022 2:54 AM UTC

        Ahh, yes! I just updated it. Thank you for letting me know.

         

        Translate
        Katja_Keesom
        Adobe Champion and Community Advisor
        Katja_KeesomAdobe Champion and Community Advisor
        Adobe Champion and Community Advisor
        Oct 31, 2022 6:18 AM UTC

        In general the answers provided are correct, with the caveat that in my experience, web page visits are stored in the activity log without the protocol at the start, so you should remove the https:// in your value to make it work. Tripped me up more than a few times before I understood the logic...

        Translate
          Darshil_Shah1
          Adobe Champion, Community Advisor, UG Leader
          Darshil_Shah1Adobe Champion, Community Advisor, UG Leader
          Adobe Champion, Community Advisor, UG Leader
          Oct 31, 2022 6:54 AM UTC

          Yes, that is true Katja, and thank you for mentioning it here! 

           

          In Marketo, the Visits Web Page activity defines "Web Page" as the original hostname + pathname + hash, but not the protocol nor the query string.

           

          For everyone's reference, here's the link to Sandy's comment where-in he explains this along with all the components of an URL in detail.

           

          Translate
            Terms & ConditionsAccessibility statement

            Loading footer...