Skip to main content
Automate Banking connects to Q2 SMART so automations can target online banking users using the same audiences and traits your marketing team already works with in SMART. An automation reads users from a SMART audience, narrows them down using SMART traits, and then updates traits on the users who match.

​
Key Concepts

Trait A single data point that Q2 stores about an online banking user, such as whether they hold a CD, when they last logged in, or their ZIP Code. Traits are stored per user, not per customer, so two users under the same customer can have different trait values. See Supported Traits for the full list. Audience A saved group of users built from one or more traits in Q2 SMART. Audiences are created and managed in Q2 SMART by your institution or provided by Q2. User trait update A value that Automate Banking writes to a trait on a specific user. Updated traits become available in Q2 SMART, where they can be used to build new audiences or drive targeted content.

​
How Automate Banking Uses Q2 SMART

Source group — SMART audience Each automation starts from a SMART audience selected as its source group. Automate Banking pulls the current list of audiences from Q2 SMART, and only users in the selected audience are evaluated. Audiences are read-only in Automate Banking — they are never created, edited, or deleted. Criteria — SMART traits Trait-based criteria filter the users in the source group. Each criterion compares a trait against a value you configure, such as Last login date more than 90 days ago or Bill Pay enrolled equals No. A user must match all configured criteria to be included in the run. Action — Set User Trait For every user who matches the criteria, the Set User Trait action writes a configured value to a user trait. This is the only change Automate Banking makes in Q2 SMART.

​
How a Run Works

  1. The automation loads the users in the selected SMART audience.
  2. Each user is evaluated against the configured trait criteria.
  3. Users who match all criteria have the configured trait value set on their profile.
  4. The run report lists each user processed and whether the trait update succeeded or failed.

​
Example

An institution wants to flag users who are good candidates for a savings promotion.
  • Source group: a SMART audience of all retail users
  • Criteria: Savings accounts equals No, and Receives payroll equals Yes
  • Action: Set User Trait — set the custom trait Savings account prospect to Yes
The marketing team can then build an audience in Q2 SMART from that trait and target those users with a banner or offer.

​
Things to Know

  • Not every trait in Q2 SMART is enabled for every institution. Contact your Q2 Customer Experience Manager to confirm which traits are available to you.
  • Traits calculated by Q2, such as those listed in Supported Traits, are read-only. The Set User Trait action writes to custom traits set up for your institution.
  • Custom traits can hold a Yes/No, text, number, date, or list value. The value configured in the action must match the trait’s type.
  • Changes to audiences and trait values made in Q2 SMART are picked up the next time the automation runs.