How to Track Multiple Form Submissions by a user | Community
Skip to main content
N
Nihal
Level 3
February 4, 2025
Solved

How to Track Multiple Form Submissions by a user

  • February 4, 2025
  • 1 reply
  • 555 views

Hello Everyone,

We’re planning a campaign in which users fill out a form to request a product trial for their customers/prospects. Since a single partner can submit the form multiple times (each time with a different prospect’s details), we need a way to track and separate each submission per partner.

Requirements:

  • The form captures prospect details (Name, Company Website, Company Size).
  • A single partner may submit multiple entries for different prospects.
  • We need to track which prospects belong to which partner for reporting.

Questions:

  1. What’s the best way to track multiple form fills from the same partner? 
  2. How can we store and report on multiple submissions per partner? 
  3. What triggers and flows should we use in Marketo to log each submission separately and associate it with the right partner?

Would love to hear how others have tackled similar use cases. Any insights or best practices would be greatly appreciated!

Best answer by SanfordWhiteman

This is the Referral Form pattern.

 

It's of intermediate complexity and we've rolled it out several times for clients.It has a few parts:

  1. Custom string fields: Last Referral Email Address and First Referred By Email Address.

    Last Referral Email Address     is continually updated on the partner's record with the email address(es) of the last person(s) they referred.

    First Referred By Email Address is updated on the referral's record with the address of the person who first referred them. It should be set in admin to block updates from form fills so the first value is not overwritten.
  2. Custom textarea field All Referral Email Addresses. This is your typical history field. Trigger on Data Value Changes for the field Last Referral Email Address and append the latest {{lead.Last Referral Email Address}}.
  3. Custom form behaviors JS as shown here: MktoForms2 :: Referral v2.1.2 (supports multiple referrals). This code posts the form on behalf of the partner and also posts the form on behalf of each referral. This makes sure Last Referral Email Address and First Referred By Email Address are updated in the right places.
  4. Optional: we sometimes write the flat string fields to custom objects using a webhook. That way each referral gets attached to the partner and it’s easier to visualize. This isn’t strictly necessary, though, as long as you have the history field going you can see (a) everyone a partner referred and (b) who first referred someone.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
February 4, 2025

This is the Referral Form pattern.

 

It's of intermediate complexity and we've rolled it out several times for clients.It has a few parts:

  1. Custom string fields: Last Referral Email Address and First Referred By Email Address.

    Last Referral Email Address     is continually updated on the partner's record with the email address(es) of the last person(s) they referred.

    First Referred By Email Address is updated on the referral's record with the address of the person who first referred them. It should be set in admin to block updates from form fills so the first value is not overwritten.
  2. Custom textarea field All Referral Email Addresses. This is your typical history field. Trigger on Data Value Changes for the field Last Referral Email Address and append the latest {{lead.Last Referral Email Address}}.
  3. Custom form behaviors JS as shown here: MktoForms2 :: Referral v2.1.2 (supports multiple referrals). This code posts the form on behalf of the partner and also posts the form on behalf of each referral. This makes sure Last Referral Email Address and First Referred By Email Address are updated in the right places.
  4. Optional: we sometimes write the flat string fields to custom objects using a webhook. That way each referral gets attached to the partner and it’s easier to visualize. This isn’t strictly necessary, though, as long as you have the history field going you can see (a) everyone a partner referred and (b) who first referred someone.
Terms & ConditionsAccessibility statement

Loading footer...