Katja_Keesom

I would actually not request the campaign, I would make it an executable campaign, where you can make use of the tokens of the original campaign to make sure the correct message goes out. Less burden on the platform as well.

I was thinking along the same lines. You could go down the route of specific emails being sent depending on the value in the field, but I would also suggest exploring putting the content of the alert in a program token in each campaign, with the alert being a standard one in the send alert program, ...

Technically, it's not a new lead. It remains the same person record. When talking about CRM approach, I would actually suggest to create a new task rather than a new lead. Of course that also depends on how your CRM is set up and what the preference of the Sales organization is.

True enough, well caught. And at that level they are called simply folders again instead of Campaign folders. So indeed Campaign folders can have tokens.No idea btw why we can't set up tokens at the workspace level...

There is no real difference. In your Marketing Activities tab it is called a Campaign folder, in all other tabs simply a folder. The only difference I am aware of is that you cannot have two campaign folders with exactly the same name.

Sanford is absolutely right and this is a topic that is really difficult to fix. The only way to bring the information together properly is to merge the records.

From the whole conversation I would suggest you do a little deeper research on how query strings, query parameters and related topics actually work. I find this a pretty comprehensive explanation: https://measureschool.com/how-to-use-query-strings/From there, decide what the relevant information is ...

Totally agree. If we understand what it is you are trying to ensure, we can point you to the best appropriate solution, so zooming out a bit will help you get to the best possible answer.

Couldn't have explained it better. The fuzziness of course gets bigger when you take into account that family members would use partly the same and partly individual devices.

Indeed, a typical use case of duplicates. The good news is, that with an order confirmation the correct record will receive the correct confirmation for the situation you describe. The bad news is that duplicates will cause all sorts of unintended behaviour, as your single real person will be seen a...