Zoominfo trigger In Marketo Landing pages | Community
Skip to main content
C
Chanel2702
Level 2
February 4, 2026
Question

Zoominfo trigger In Marketo Landing pages

  • February 4, 2026
  • 2 replies
  • 42 views

We have a ZoomInfo tracking snippet installed on our Marketo landing pages. ZoomInfo is integrated with Marketo, and we’ve configured it to de-anonymize specific job titles from the company-level data captured when users visit a Marketo landing page. Once those contacts sync, we trigger a campaign for them.

While I can see traffic to the landing page, ZoomInfo is not showing any visitor information—it indicates that there is no data available to de-anonymize. Is there a known issue with using the ZoomInfo tracking snippet on Marketo landing pages, or is there a specific placement requirement for the snippet? The snippet is working as expected on our website pages.

    2 replies

    giriprasathb
    giriprasathb
    Level 3
    February 4, 2026

    Hi ​@Chanel2702 ,There isn’t any known incompatibility between the ZoomInfo tracking snippet and Marketo landing pages. If the snippet is working on your main website but not on Marketo LPs, the issue is typically related to implementation or configuration rather than a platform limitation.
     

    A few areas I would recommend reviewing:
     

    Snippet placement: Ensure the ZoomInfo script is added at the landing page template level, specifically within the <head> section (Edit Template → Head HTML). It should not be placed inside a rich text or HTML content block. After adding or updating the script, re-approve both the template and the landing page.

    Script validation: Check the published page source and use browser developer tools (Network and Console tabs) to confirm the script is loading properly and not being blocked by CSP, security settings, or other errors.

    Domain configuration: If your Marketo landing pages are hosted on a different subdomain than your main website, confirm that this domain is properly configured or allowlisted within ZoomInfo.

    IP-based de-anonymization: ZoomInfo primarily resolves company-level data from corporate IP addresses. Traffic from home networks, VPNs, or mobile carriers may not return identifiable data, even if the page is receiving visits.

    In most cases, when ZoomInfo shows “no data available,” the cause is related to snippet placement, domain configuration, or IP resolution—not a compatibility issue between ZoomInfo and Marketo landing pages.


    Thanks,
    Giriprasath B

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    February 4, 2026

    🠶 It should not be placed inside a rich text or HTML content block.

     

    Putting <script> tags inside RTAs or editable blocks is fine. Let’s not spread FUD.

     

    And you can’t simply move all scripts to <head>. For example, on Marketo LPs w/named Marketo forms, the MktoForms2 global doesn’t exist until the forms library loads, which is always in the body! So naïve forms JS that assumes MktoForms2 is available* cannot be in the <head>. It must be in a footer area after the main content, near the closing </body> tag.

     

     

    * ideally, code would wait for MktoForms2 regardless of its placement, but most people don’t know how to do this correctly

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    February 4, 2026

    Please link to sample pages on your main site and on your Marketo domain so we can inspect them live rather than theoretically.

     

    Marketo LPs are just webpages and any 3rd-party JS is supported. (Naturally, features like form events need to be properly captured, but this is true of embedded Marketo forms outside of Marketo LPs as well.)

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    February 13, 2026

    ​@Chanel2702 please return to your thread.

    Terms & ConditionsAccessibility statement

    Loading footer...