Hi everyone! I hope this is the correct place to ask this question. We are in the process of moving to Wordfly from another ESP and have run into some issues with exporting our Contact Point Purposes as data elements using the process recommended by Wordfly. We use Contact Point Purposes to manage subscription status (for example, we have a CPP for News & Events, and one for Support Us, both of which are only used on email addresses). This is how we manage mass-email preferences in Tessitura, in addition to global unsubscribe. Since the integration between Wordfly and Tessitura is one-way, you have to include output set elements for these CPPs if you want to update any existing data in Wordfly. Wordfly requires that you have a CPP column for each email, with a 0 or 1 value returned depending on if the email is subscribed or not. They also have a custom view, LV_WF_Contact_Purpose, which they recommend you use.
The issue is that this view only references primary email addresses, whereas we have tons of records in our system where more than one email exists with CPPs, and sometimes the CPPs are different to what's on the primary email. When we pull multiple emails, the output set elements just return whatever subscription values exist on the Primary email. However, when we tried editing LV_WF_Contact_Purpose to remove the reference to primary email only, we got exponential duplicates in our output set elements, because it was referencing all available email addresses, and not just the ones we selected for the list.
Have any other Wordfly users found a way around this problem, or do you only use Primary emails for Wordfly lists? Or did you end up building your own view/query elements and query element group? I would really appreciate any insight here as our team is kind of at a loss! It seems that we should be able to pull more than one email per constituent if applicable, and that there should be a way for the CPP outputs to match with what's on that email and not just the primary email.
Thanks,
Katie
The solution to the multiple emails per constituent problem is to design a view that puts all of the subscription-specific information into the same query element group. Your list output will multiply every time it joins multiples from one group together with another. You need this to happen once in order to potentially return multiple emails per constituent, but if you join an additional group with multiples, then each email will get multiplied.
So, you will need to write a single view that returns one row per subscribed email address, and includes columns for all of the email-specific subscription and preference data. Then create a query element group for that view, and use ONLY those elements plus constituent-specific (one row per constituent) elements in your output set. (This means you can't use the out-of-the-box contact point purpose or email address elements -- you have to get this data from your view.)
Hi Nick,
Thank you so much for your reply! We did end up creating our own query element group and query elements, although we were able to get the information we need by applying filters to the query element group rather than setting up an entirely new view. This has allowed us to get the correct CPP information for different emails, and we do not reference LV_WF_Contact_Purpose at all. We do get duplicate eaddress_no when using Extraction Manager (for some reason, duplicates have not been appearing in List Manager), particularly when we use the Communication Management section to allow multiple contact points per constituent and remove duplicate email addresses. It is probably due to the issue you pointed out, where we are joining more than one group so the eaddress_no gets multiplied. But since Wordfly automatically suppresses duplicates when emails are imported, it does not cause any issues with actual functionality.