Q2 SMART has added the Conversionvalue field to step 1 of the Campaign Builder, to the campaign export, and the campaign report UI.
The conversion value is the monetary amount assigned to each conversion (in USD) for a specific campaign, which assists in determining an individual campaign's return on investment (ROI).
The conversion value field is only available for the types of campaigns that allow tracking of conversions and adoptions. The conversion value field only shows after the user picks a campaign type that records conversions, otherwise a message that says conversions and adoptions are not recorded for that campaign type will display.
The total conversion value for a campaign is the conversion value multiplied by the number of conversions. The total conversion value is reflected on the campaign export and on the campaign's report page.
For more information, see Conversion values.
Note
While this is not a mandatory field, Q2 encourages FIs to begin using the conversion value field in the applicable campaign types. In the future, we will be surfacing this value with aggregate campaign reporting. We will also use this value to establish SMART's overall ROI for your institution.
(ECOM-8116, ECOM-8117, ECOM-8182)
The SMART API endpoint Campaigns by user now includes conversion-value in the response "conversion-value: <float>". (ECOM-8115)
-
Added character limits of 100 characters to user list names and 400 characters to user list description entries. These character limits are reflected in the UI. (ECOM-7537)
-
Updated user list cards to detail more information on when the list was uploaded, by whom, and when the list was last updated. This additional information is also reflected on the user list modal when uploading new users to the list. (ECOM-7997)
-
Fixed an issue where audiences included an inflated number of users when they had certain traits but did not have the corresponding Boolean trait. Now, when certain traits are assigned to an audience, the corresponding Boolean traits are automatically included, so the audience count returns accurately. (ECOM-8047)
-
Fixed an issue where duplicate users contributed to the audience size in user lists. Now, when a user list contains duplicates, the duplicates are removed from the audience size during the validation process, and the UI displays how many duplicates were removed from the validation. (ECOM-8066)