Using Known Visitor to Show Gated Content | Community
Skip to main content
P
plane
New Participant
July 26, 2023
Solved

Using Known Visitor to Show Gated Content

  • July 26, 2023
  • 1 reply
  • 1733 views

My team is looking to gate our content with a single form across our entire site. No matter where you submit the form, we want to then show the ungated content across the site. I'm hoping we can use KV for this, but I can't find a way for us to see that Marketo recognizes the user as a KV.

Ideally our flow would be:
1. Unknown user visits site, clicks link for a gated asset
2. Modal with MKTO form pops up, user Submits form
3. User gets direct access to the asset
4. User returns to the site, MKTO recognizes them as a KV
5. We are able to see that MKTO recognized them as a KV and when they click an asset we just bypass the modal and give them direct access. 

Is it possible to see in the browser storage/cookie data when MKTO recognizes a KV so we can use that as a point to show certain content on our end (NOT using the custom HTML WYSIWYG editor in MKTO), or does KV recognition happen on MKTO's end when the form embed populates? @sanfordwhiteman I know you've probably got the deepest knowledge here so tagging you. Thanks in advance everyone!

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 SanfordWhiteman
Is it possible to see in the browser storage/cookie data when MKTO recognizes a KV so we can use that as a point to show certain content on our end (NOT using the custom HTML WYSIWYG editor in MKTO), or does KV recognition happen on MKTO's end when the form embed populates? @sanfordwhiteman I know you've probably got the deepest knowledge here so tagging you. Thanks in advance everyone!

No, there’d never be a browser record of this without loading a form.

 

“Known Visitor” is usually defined as an associated Munchkin token (regardless of what fields are on the record) but for the purposes of KV HTML, “Known Visitor” means an associated token and a non-empty Email Address, First Name, and Last Name field. If those fields are not filled in, again for KV HTML purposes only, the person is not sufficiently “known”.

 

If you want to know if the forms library considers someone known, you can load the form and check if it contains the KV HTML box (which has a distinct CSS class .mktoTemplateBox). Then unhide/modalize it as necessary.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
July 26, 2023
Is it possible to see in the browser storage/cookie data when MKTO recognizes a KV so we can use that as a point to show certain content on our end (NOT using the custom HTML WYSIWYG editor in MKTO), or does KV recognition happen on MKTO's end when the form embed populates? @sanfordwhiteman I know you've probably got the deepest knowledge here so tagging you. Thanks in advance everyone!

No, there’d never be a browser record of this without loading a form.

 

“Known Visitor” is usually defined as an associated Munchkin token (regardless of what fields are on the record) but for the purposes of KV HTML, “Known Visitor” means an associated token and a non-empty Email Address, First Name, and Last Name field. If those fields are not filled in, again for KV HTML purposes only, the person is not sufficiently “known”.

 

If you want to know if the forms library considers someone known, you can load the form and check if it contains the KV HTML box (which has a distinct CSS class .mktoTemplateBox). Then unhide/modalize it as necessary.

    P
    planeAuthor
    New Participant
    July 28, 2023

    Thanks @sanfordwhiteman, this is exactly the info I was looking for. Appreciate your help in clarifying!!

    Terms & ConditionsAccessibility statement

    Loading footer...