Accelerator 24.3.2 Release Notes

Initiatives Released

Profile Lookup

Use Case

Currently Accelerator offers multiple ways to query your data and see returns for segmentation, but does not provide a specific view to meet the needs of looking at individual customer profiles. Profile Lookup will allow data admins to setup a flexible query to return a single customer into a view to help with marketers. That view can contain highly unique data points for individuals, and historical context for touch points with that customer across the Accelerator platform. Marketers can use simple preset search criteria, like email address or name/ID, to see results - all entirely based on your own custom data structure, and all without having to touch any SQL.

Goals

• Using a highly flexible SQL query, give data admins the ability to build a unique set of data points to surface to marketers looking for buying habits and historical information on a single customer
• Give campaign admins a way to enter a unique ID and surface the associated profile in an easy to read view

Capabilities

Build a Profile and History View

Data admins can build out 2 highly specific queries for the same view - Profile and History. Each powers the Profile Lookup feature to display the output in a dedicated card or table, and each requires the shown Unique ID and Start/End date parameter within the query. Select the copy button for each parameter above the SQL window to copy the correct syntax to your clipboard for ease of use.

Once your queries are setup, you can test these using the Preview feature. Enter the parameters you’d like to test against for each query, you can ensure the query output is meeting your expectations. This will be the output the marketer sees when searching from the Profile Lookup screen.

Use search criteria to query the Profile and History

Using the new Profile lookup screen, marketers can now use a simple search entry screen which references the builder page to see the associated profile. Using the 3 data points required from the builder, users can enter the specifics of the profile they’d like to see.

The profile displays in two separate cards, representing the two distinct queries which were used to build this profile. The profile card contains a single return with all the associated data points mapped into a card display. The history should have numerous returns, and is mapped onto a table up to 100 rows. Users can see the description provided for this feature at the top, the parameters used to find query the profile, and can refresh at any time. To respect PII securities, no search is stored or saved, and leaving the page will remove the profile display until searched again.

SCIM with Okta

Use Case

Accelerator user profiles and access are currently disconnected from the customer’s identity service provider (Idp) and require the system admin to add and remove users manually in Accelerator. This process is tedious and error prone, and does not align with how enterprise companies manage user access across their tech stack today. The SCIM (System for Cross-domain Identity Management) integration will allow customers to automate the exchange of user identity data between Okta and Accelerator, so joint Okta <> MessageGears customers' IT departments can manage the Accelerator user’s provisioning lifecycle through a single system of record (Okta).

Goals

• Allow Okta customers to push user data from Okta and Accelerator
• Lay the foundation for supporting other SCIM capabilities (roles / permissions, groups)

Capabilities

Add and remove employees to Accelerator through Okta

When a new user is assigned to an Accelerator app (aka “activated”) in Okta, the user is automatically created in Accelerator. Similarly, if a user is unassigned from an Accelerator app in Okta (aka “deactivated”) the user’s Accelerator access is locked, blocking them from signing in and using the application.

Update profile data

When a user’s attribute is modified in Okta - email address, first name, last name - that change is pushed to Accelerator and the user’s Accelerator profile is updated accordingly.

Improved Error Messaging

Use Case

Job analytics in Accelerator are difficult to read, don’t clearly communicate if the error affected message sending, and don’t provide users a quick way to identify the cause of a failure. This enhancement is going to solve all of these by boldly and clearly indicating if messages were sent or not, and telling the user which asset caused the failure and including a link to that asset. This improvement affects the job analytics page and the error notification emails.

Goals

• Improve the error message diagnosis experience

Capabilities

Improved error messaging

Job analytics now display which asset caused a job failure.

Error notification emails include the same messaging that is presented on the job analytics page.