Anyone using interest group opt-in/opt-out data to generate respective solicit codes in RE?

Zef Ferreira · April 3

Hi folks, we are planning on using Luminate to send emails from our organization. We currently use NetCommunity for this function. Thinking of using interest group opt-ins/opt-outs to generate the respective solicit codes in RE. Does anyone have any experience doing this? We are currently working with Omatic on a formula that would interface with the RE consent module, however, I am having trouble exporting interest group opt-in/opt-out data from LO. Has anyone been able to export the constituent data along with a date when the opt-in/opt-out took place? Any help or alternate solutions would be much appreciated. Thanks!

Szymon Zaleski · April 28

@Zef Ferreira
At Fred Hutch we are using interest groups to update consents in RENXT. I created a custom sync application that pulls the information from LO using SOAP API https://developer.blackbaud.com/lo-api/web-services/types/constituent
into an on-site data warehouse and then updates the record in RENXT using Communication Preference SKI API
https://developer.sky.blackbaud.com/api#api=communication-preference&operation=ListConsentCategories
We are linking records using LO ConsID as an alias in RENXT.
Happy to connect to share more details.

Zef Ferreira · April 28

@Szymon Zaleski, thanks for your reply! Szymon, would you mind sharing how you are pulling the data from the SOAP API? Is there a date associated with a constituent opting-in/out of a specific interest group? Thanks again - would be interested in connecting to learn more about your process.

Szymon Zaleski · April 28

@Zef Ferreira
There are two constituent groups associated with each interest - Opt-In and Opt-Out group. When you add an interest to a constituent record, that record is being added to the Opt-In group. when the constituent opts out from an interest, the interest stays on their records, but they are being moved to the interest Opt-out group.

While I don't believe there's a history of opt-ins and opt-outs in LO (on the other hand, RENXT consents preserve it), with the daily download and the use of the data warehouse you can detect when the change happens and apply it to the system. It works both ways - for example if someone calls to inform us that they would like to opt out from a specific , we can mark that in a consent in RENXT and the sync will detect the change and update the interest on their LO record

MaryAnn Coyle · May 5

@Zef Ferreira When we deployed the Luminate Connector, we were not able to sync consents. Instead, we toggle the solicit and interest codes through virtual fields and dictionaries. This file shows how the virtual fields are mapped:

LO Connector toggle interest and solicit codes.csv

Zef Ferreira · May 5

@MaryAnn Coyle, thank you very much for sharing the CSV file that you use for mapping interest groups/solicit codes. MaryAnn, with what frequency does your organization run this formula?

MaryAnn Coyle · May 6

@Zef Ferreira We sync Luminate and Raisers Edge weekly, on Friday morning. We started with weekly at a time when the plug in profiles were taking up to 24 hours to run. Over the past several years, improvement to plug-in profiles and using omatic cloud for for opt-ins has significantly reduced run time, but even, as a cloud formula, appeals can still run over the weekend.

Zef Ferreira · May 6

@MaryAnn Coyle, thanks for your reply. MaryAnn, is there a particular report that you use to generate the list of opt-ins/opt-outs, or are you dumping data and running a script to identify the changes and when they took place?

MaryAnn Coyle · May 6

@Zef Ferreira This is all happening through a plug-in profile importing from LO to RE and an omatic cloud formula pushing data from RE to LO. The first happens to be limited to a group in LO, but that was done just to cut the volume to active donors. The second is based on a web view Constituent List which we chose to build through a database view static query in part because we already had the query built for a plug-in that the formula replaced. Omatic cloud formulas must pull from a List and it may be possible to build the List directly if you can get all the parameters you need that way.

Zef Ferreira · May 7

@MaryAnn Coyle, this is very helpful, thank you. Would you be able to connect via teams/zoom to further discuss, or perhaps do a quick walk-through of your process? Thanks again!

Venky Immadisetty · June 18

@Szymon Zaleski
Hi Szymon, I would like to connect with you to discuss the process of storing information in the data warehouse. I have already sent you a personal message with my email address to check your availability.
Thanks!

Anyone using interest group opt-in/opt-out data to generate respective solicit codes in RE?

Comments

Categories