Split popolation

Hi,

Campaign users should not worry about "temp" tables and just focus on using the activity nodes. I believe if the customer can receive different personalized messages during the journey, there should be different delivery nodes and not trying to make one delivery do everything. It is the preferred method for campaign execution and post execution reporting. You use the split activity node to segment your universe for each touch and assign the proper segment code for ease of reporting.

Thanks.

Yes, you can use any activity here.

Hi Jon,

thanks, I thought so. Would this scenario work, if I used an enrichment before the splits to update the temp table?

Best regards

Niels

Hi Pierre,

the recipients receive several emails within a workflow, but they should receive different versions of the emails based on their profile. The profile can change while they pass through the journey and I want to filter the population directly before sending out the delivery.

Best regards

Niels

Hi Niels,

could you give a bit more context?

What are you trying to accomplish?

Kind regards,

Pierre