1. Default Values
When creating an export format you can now assign default values to individual fields in the export. If a respondent being exported doesn't have an explicit value for a field -- e.g., a value that was either collected from a form submission, a rule to save it in the database, or a variable read from the incoming query string -- then the default value will be substituted instead.
So for example, if an export requires a LeadSourceCode, you might normally assign the LeadSourceCode explicitly in each path. However, you can also have a default value in the export so that if a path DOESN'T set LeadSourceCode -- either intentionally or by accident -- the default value in the export will be substituted as a fallback.
2. Export of Internal Conversions
Working with campaigns that have both internal and external conversions? You now ave the option of using a new "Internally converted respondents" scope on your exports.
So, if you collect data on respondents when they convert inside LiveBall -- but not when they convert externally -- you can have an export configured that deals with those internal conversions as their own group.
If you want to export both internally and externally converted respondents, you can continue to do so with the "Converted respondents" scope -- just make sure that there are no required fields in the export that an externally converted respondent wouldn't have.
Questions? Email me or your dedicated LiveBall account manager!
--Jessica Frobel
jfrobel@ioninteractive.com