SanfordWhiteman

This is the built-in Known Visitor HTML feature (in Form Editor » Setup » If Known Visitor, show Custom HTML). Your web team doesn't need to do anything.

What (please be precise) is the Wait step for?

Hi @SanfordWhiteman , then what should be the best way to run this campaign.Like Udit said. I was pointing out that even if you didn’t need to include all the Random Samples in one place, what you were trying could never fit your needs, since you’re changing the overall population before sampling.

Hey @hbriere ran across this thread and wanted to correct/clarify a couple of things. In a nutshell, the limit of a Textarea is actually 65,335 bytes, not 30,000 bytes. The SQL datatype is UTF8MB3, meaning that can hold an absolute maximum of 65,335 ASCII (U+00-U+FF) characters32,767 2-byte (U+100-U...

That’s too bad. Well, maybe a future reader with more time will make use of it.

1. Is there a way to identify everyone who is in each of the wait steps? We have three wait steps.Not automatically. I like to set an Interesting Moment before someone enters a Wait. 2. Does using "Override Campaign Priority" help move people through the wait step faster?What do you mean by “through...

Does this remove Delete Person From SFDC flow step access as well? I’ll check this myself later unless someone has a definitive answer.

As @uditmathur notes, if you use Random Sample to split into sublists, you should use a single flow step with the different percentages. But even if this weren’t necessary, your campaigns wouldn’t make sense. The Day 2 flow is taking 30% of the people who qualify for the Day 2 campaign. That’s not 3...

Use a Custom Object! There’s no need for all those extra lead fields (ugh). Each CO record represents a Site and is related to the Site Owner (i.e. Person). It has fields Name, URL, etc. Alternately, you can use one big Textarea with JSON on it, what I’ve called a “poor man’s Custom Object.” The JS...

The webhook (more precisely, the webhook-compatible service) uses the REST API. It reads the CO list and applies the same order/filtering logic you do in Velocity. That lets you generate the same output, then write it back as attributes of a new CA.