Dear Community Members,
I have a use case where I’ve created an audience in Data Distiller that is evaluated daily. This audience will be used as a Read Audience in an AJO journey.
Business requirement:
Each day, we should send only 1,000 emails total.
Within this, we want to apply quotas per attribute. For example, I have attributes (attr01, attr02, … attr100), and I would like to ensure that only 10 emails are sent for attr01, 10 for attr02, and so on.
Questions:
1) Is it possible to enforce such per-attribute capping directly within AJO journeys?
2) If not, what are the best practices or recommended approaches?
Any guidance, examples, or workarounds would be greatly appreciated!
Thanks in advance.
解決済! 解決策の投稿を見る。
トピックはコミュニティのコンテンツの分類に役立ち、関連コンテンツを発見する可能性を広げます。
表示
返信
いいね!の合計
Other way to implement is using the data distiller to generate the audience as mentioned.
assign these attributes to profile using Data Distiller - 10 profiles have attr1, 10 profiles have attr2... and then use the Data Source condition?
表示
返信
いいね!の合計
@Akash__Saw This particular use case seems to align perfectly with the newly introduced Orchestrated campaigns feature that has recently been added in AJO.
Thanks @SatheeskannaK for the reply. currently, we don't have Orchestrated campaigns feature in our sandbox.
any other way to implement this?
表示
返信
いいね!の合計
Other way to implement is using the data distiller to generate the audience as mentioned.