How Do I Change the Order of the Data Fields on My Form?

In your form library, simply drag and drop the fields into order. Please note these changes will take place globally and in real time.

Can I Use Our Existing Form Instead of a LiveBall Form?

Yes, you can! While LiveBall forms are recommended so you can take advantage of advanced rules and easily create different forms for your landing experiences, you can also use an existing form when necessary—this is especially useful for secure forms, like credit card applications.

Any existing or secure form can be easily integrated with LiveBall by displaying it inside an iFrame on the LiveBall page—an iFrame allows an externally-hosted page to be embedded and displayed inside another page. The URL of the form is simply published in the widget/iFrame editor in LiveBall, along with the necessary iFrame width and height specifications (up to 1200x1200 pixels). When a respondent views this page, the secure form is seamlessly pulled in and appears to be part of the LiveBall page.

To track the steps of a multi-page form, just add LiveBall's ready-to-use Javascript to each of the pages of the form—by doing this, you'll be able to tag various steps that occur on the externally-hosted form so the tags and even conversions are logged back in LiveBall. At the end of the process, it's also possible to automatically send the respondent to another LiveBall page—this is also accomplished using Javascript provided by LiveBall.

What's the Difference between Assigning a Default Value to Data Field vs. the Export Field?

While assigning a default value in either of these cases would appear to serve the same purpose, it does not—there are specific cases for each:

• the default value for a data field will only get stored if the data field is actually presented to the user in a form that they submit.
• the default value in the export field will always be included with the export, whether or not the user touched or saw that field—or even submitted a form at all—in the path.

Why Are Multiple Tags Separated by Columns in My Delimited File-Format Export?

This is likely occurring because the 'use quotes' option on the export is set to 'No'.  Without quotes around the field, when the 'tags' column has multiple tags, it separates them with a column—this causes additional tags to appear as extra columns when you open the file in a program such as Excel.  

To solve this, simply click on the pencil to the left of the export name and set the 'use quotes' option to 'Yes'. This will result in the tags column being bounded (e.g., "tag1, tag2, tag3").

If I Setup Two Exports - One for Converted, One for Non-Converted Respondents - Will a Lead Be Included in Both Exports?

Yes. The export for converted respondents is exclusively for lead data; the export for non-converted respondents is inclusive of both leads (converted respondents) and other data collected on the respondents (e.g., geolocation, tags, etc.)—even if they didn't convert.

Do I Need to Associate My Scheduled Export With a Campaign?

Yes! This is an important step and cannot be overlooked.

Scheduled exports are assigned at the campaign level...

1. Navigate to a campaign whose data you would like to export.
2. Click on ‘Scheduled Exports’ in the Campaign Resources.
3. Choose your export.
4. Click the ‘Export’ button to begin scheduled export.

Do LiveBall Exports Support Mashups?

Yes.

Mashups make it easy for you to map data from LiveBall into your system via CSV, vCard, post-to-web form or Salesforce.com integration.

You can include “mashup” fields (combination of one or more database fields), using the same @@DataName format that you use for email templates and passing along data in URLs, as well as including any static text, via a mashup template.

This is easiest to demonstrate with an example. Say that you have three data fields that you collect with the following data names: FirstName, MiddleInitial, LastName. You could create a mashup template to combine these into a single name like this:

Mashup template: @@FirstName @@MiddleInitial @@LastName

As a special feature, if a @@DataName variable is empty and it is followed by a space in the template, LiveBall will automatically skip the following space. So in the example above, say FirstName = “Jessica” and LastName = “Frobel”, but MiddleInitial is empty, then the mashup would output:

Jessica Frobel <== note only one space between first and last name

You can also include line breaks in your mashup templates. For example, let's say you have a Salesforce export that you want to mashup Address1, Address2, and Address3 fields into a single Address field in Salesforce.com. Your template would look like this:

Mashup template:
@@Address1
@@Address2
@@Address3

Have additional questions or need a step-by-step walkthrough? Submit a support request or contact your Liveball account manager for details!