Hi,
So I'm creating a data normalization campaign for leads in our database to change state/province fields from abbreviations to the full state/prov name so they can be synced to SFDC.
Does anyone know the maximum number of "Add choice" options I can use in a Data Value Change, before it either doesn't work or is too taxing on the system and does something bad?
With my state/prov pick-list, there's 63, and it looks like I've been able to add all 63 add choice fields, but when I started choosing "state" from the if/attributes, it takes a few moments before it selects. If this isn't a great idea, wanted to check if there was another more efficient way to do this? Maybe split into a group of campaigns?
Thanks!
Hi David,
We have a case working with 250 choices.
-Greg
Thank you Gregoire, that's helpful to know. I just ran the campaign, and it worked quicker than expected with 63 choices, so that's awesome.
That's impressive. Does it load in the UI ok? That's the biggest issue I have with more than 5 choices.
Yes it does, but better do in the morning in Europe
This is a flow that converts country codes. Hence the 250.
-Greg
BTW, I did not do it. I would have used a webhook instead
Yeah, good call- Update: Our Marketo rep advised me that best practice is to have no more than 20 add choice amounts.
Hi Grégoire, a few years later but thought I'd give it a shot! 🙂
How would you use a webhook to achieve this? Would you mind sharing a few details?
Best,
Ricky
I suppose Greg meant passing the person's State/Province data over to a webhook-compatible service which would then send the corresponding normalized value back. You can also use Sandy's Flowboost for this.