Defining Your Own Lead Source with Uberflip CTA's

By default, Uberflip will try to populate the Lead Source field inside of Marketo for new Leads or in situations where that field does not currently have a value. However, it's also possible to define your own static or dynamic Lead Source value by using hidden fields in combination with Marketo's block field updates option.

When a net new Lead converts on a Form CTA, Uberflip will pass a value of UF-CTA-12345-CTAName to the Lead Source field inside of Marketo (if a value for Lead Source already exists, Uberflip will not overwrite that value).

While this approach makes it easy to understand which CTA drove a conversion, you may already have your own predefined Lead Source terminology or framework in place, meaning you'll want to ensure Uberflip passes along the proper predefined values as visitors to your Hub convert. 

There are several approaches you can use to push customized values into your Lead Source field in Marketo while not overwriting any original values that may exist. 

Follow the process below to customize your Lead Source values. 

 

(1) Block Field Updates in Marketo

To define your own static or dynamic Lead Source in Marketo, you'll first need to enable Marketo's Block Field Updates option. This will ensure that existing Lead Source values are not overwritten but will still allow Uberflip to set the field value for net new Leads.
 
To block field updates, log in to Marketo and from the Admin page, click on the Database Management option in the left menu.
 
Search for the Lead Source and Lead Source Detail fields, click the field names, and click Block Field Updates from the Field Actions menu. On the popup that appears, select the Web Service API option from the Input Sources list.
 

 

(2) Customize Hidden Field Values in Uberflip

There are several approaches that you might want to take when customizing the Lead Source values from your Hub.

 

Passing Simple Lead Source Values 

To pass something as simple as "Uberflip" or "Content Hub" as the Lead Source, start by logging in to your Hub and ensuring that you've added the Lead Source field to your Form CTAs.

Once the field is on your Form CTAs, you'll be able to edit the field -- and specify the hidden values -- by clicking on the pencil icon beside the name of each field.

Set the "Field type" to Hidden and specify the "Hidden value" to any static value that you prefer, such as "Content Hub" or "Download". This is the value that will populate the Lead Source field in Marketo when a user submits the Form CTA.

 

Passing Dynamic Lead Source Values

To pass a dynamic Lead Source into Marketo, you'll need to rely on query string parameters or Custom JavaScript to populate the Hidden Field. Again, you'll need to start by logging in to your Hub and ensuring that you've added the Lead Source field to your Form CTAs.
 
Set the "Field type" for Lead Source to Hidden and check the box to "Allow query string values to populate this field". From there, you'll be able to specify which query string parameter should be listened for. The value for that parameter will then be passed into Marketo as the Lead Source.
 
For example, imagine a visitor to your Hub came in through a URL like hub.website.com/ebooks/ebook-name?utm_source=Email1. The value "Email1" would then be passed into Marketo as the Lead Source, as per the screenshot below.
 
 
Note: If you would like additional information about a conversion passed into Marketo (for example, you may want to pass the name of the Item a user converted upon into the Lead Source Detail field) you can add Custom JavaScript to your Hub. Please content Uberflip's Support Team for assistance.
Previous Article
Pro Tips: Getting the Most Out of Your Marketo + Uberflip Integration
Pro Tips: Getting the Most Out of Your Marketo + Uberflip Integration

Three tips for optimizing your Marketo + Uberflip integration so it works and you get the most out of it.

Next Article
Setting Up Form CTAs with Marketo
Setting Up Form CTAs with Marketo

When creating a Form CTA, you will be directed to the service configuration portion of the CTA (first tab)....