Skip to main content

#Webform Values2 utenti parlano di questo argomento

We have a client who is looking to run a number of marketing campaigns across LinkedIn, Instagram and Facebook. 

 

When someone signs up to their newsletter via one of the ads, they want the lead to be created in Salesforce, but they also want to be able to identify which specific ad or campaign the lead originated from. 

 

Our current thinking is that each ad would direct users to a web form on the client's website, which would then submit the information into Salesforce using Web-to-Lead. However, we're not 100% sure of the best way to track which ad the submission came from and pass that information into Salesforce.

Could someone advise on the best approach? Alternatively, if there's a better way of achieving this with little to no additional cost, we'd really appreciate any recommendations.

 

Thanks!  

 

 

#Web-to-lead  #Webform Values  #NPSP  #Leads  #UTM Parameters  #Automation

1 risposta
  1. 28 lug, 23:57

    Hi Philippa, a way to tell which ad a lead came from is UTM parameters captured via hidden fields on your Web-to-Lead form, plus a hidden Campaign Id field to auto link leads to a specific Campaign. This should be of no additional cost and is low complexity.

0/9000

Looking for help on creating a mapping for webform values to values within SFDC. We use ISO codes as integration values for state and county but want to leave the full name State and County on our webforms. Then map to the ISO codes when syncing to SFDC

1 commento
  1. 28 ago 2020, 20:47

    I do this often and have a few different ways to do this.

    Start by looking at that form. You can have the full names as the form LABELS and the ISO codes as the form values. Standard practice for form dropdowns.

    Other options:

    Automation rules work, but you end up using them all to solve this.

    It takes me about 6 hours to build an Engagement Studio program to do the if this value, change to that value pairs. (Super secret trick, engagement studio doesn't need to send email at all - I use it like process builder but for Pardot)

    I also wrote API code to solve this issue.

    https://thespotforpardot.com/2019/02/14/a-v-day-gift-fixing-state-country-mismatches-between-salesforce-pardot/

    I have a much more advanced version of this code that my clients use to solve this - plus a lot of other little nuances that we encounter with Pardot data.

0/9000