Re: Track Marketo Form Submissions from Wordpress Webpage Footer

Anonymous
Not applicable

Track Marketo Form Submissions from Wordpress Webpage Footer

We are rolling out a new website next week.  The platform we're moving to is Wordpress, and we have a footer across the entire site that includes a "Request a Demo" form that opens in a lightbox.  I have a campaign set up in Marketo to send a lead alert to us when someone fills the form out.  Since it is part of the footer, is there a way to indicate which webpage the person was on when they filled out the form?  I tried adding the {{lead.Original Referrer}} token thinking that would work, but it just pulls website URL (www.unifysquare.com vs. the specific page I was on: www.unifysquare/uc-consulting-services).  Is there anything I can do, given our footer set up?

Tags (2)
2 REPLIES 2
Grégoire_Miche2
Level 10

Re: Track Marketo Form Submissions from Wordpress Webpage Footer

Hi Lisa,

You will have to capture the page in a hidden field using a bit of JS code added to the form standard embed code. That JS will capture the page URL or Title (or both) and post it to a hidden field in the form (you probably will have to create a specific field for this). Then you will be able to use that field as a token in the alert email.

Some code examples are provided in the forms 2.0 API here: http://developers.marketo.com/documentation/websites/forms-2-0/

-Greg

SanfordWhiteman
Level 10 - Community Moderator

Re: Track Marketo Form Submissions from Wordpress Webpage Footer

You only need a separate field:

  • if you're going to save the data to the Lead record
  • if your site uses query params to distinguish pages in a meaningful way

Within the ​Filled Out Form ​trigger context, the built-in {{Trigger.Web Page}} token is the URL of the page that hosts the form, including the hash.  However, it does not include the query string. Looking at the Unify Square site, content is navigated using pathnames (http://www.unifysquare.com/technology , http://www.unifysquare.com/busy-on-busy) so the built-in token will work.