Clinton_Gage3

So we ultimately went a different route. We ended up segmenting the entire page based on LCID, except for the forms. We wrote some custom code that swapped out form labels based upon LCID. This allowed us to segment the form on an additional pivot since it no longer required the LCID segmentation. W...

You might also consider doing the footer as a separate API insert, it can feed to the same program if desired. We had a similar issue, and I split the inputs so we could measure who was using the run of site form in the footer versus the in page.

I'd also have you consider mapping what you think the lifetime journey is going to be - e.g. if the individual comes through again or for another opportunity. I'm not sure if you are doing this as a master lifecycle or doing at a smaller program level. At the smaller level probably works fine to get...

Another option is to define Segments, so that your audiences are associated to them, then use that segment as a filter for inclusion or exclusion.I generally like this as it is associates them by criteria and you don't have to continually query as you would a smartlist (in essence it is built in)

Good luck - ping me if it happens again and we can take a deeper look.

Did you make any template changes - I had this happen once when the template had the default then when the team pushed the update our "standard" was different until we reimplemented (and drove desired outcome all the way back into the template).

Check in SFDC for the field and see if it has a picklist, ensure that your import values have the same selections. Additionally make sure that all SFDC required fields are not blank.

David, take a hard look at the failures and their membership status, if they error and you reset them you must also change the registration status and have that synched with the provider.

@ClintonGage