24 Replies Latest reply on Nov 20, 2017 6:33 AM by Dan Stevens

    Undesired behavior when using Personalized URLs PURLs

    Dan Stevens

      I had some members of my team participate in a series of PURL test and came up with the following findings: 

      1. If the user has been previously cookied AND known, but enters a PURL intended for someone else, Marketo will correctly identify the user based on their cookied data and NOT based on the PURL.
      2. If the user has been previously cookied (and known), when they enter the PURL, they will be identified using the data in their lead record in Marketo - and a personalized landing page experience can be used.
      3. [EDIT 11/20/2017]: If the user has an associated cookie on their browser (e.g., visited your Munchkin-enabled web page) but is not yet KNOWN, when they access their PURL-enabled LP, the page will not be personalized (tokens will remain blank) - even though a lead record had been created in Marketo to support the creation of their PURL.
      4. If the user has does not have an associated cookie on their browser, when they enter their PURL, the personalized tokens will render properly on the LP.

      1, 2 and 4 is the desired behavior.  And our desire for #3 would be to have the user identified by the data that was used to create the PURL.  Does Marketo have any plans to improve upon this?  We're using this approach for a direct mail campaign - and as a result of #3's outcome, I don't think we can rely on Marketo PURLs for appropriate tracking purposes and personalization via tokens.