You can use a read audience to target the intended profiles >> wait for x days >> condition to check if there is a click event ("interactionType":"click") against the respective CTA label / URL and also check if there was a purchase event in the last x days (This will be an inSegment check).If it ev...

It will be a single shot journey with read audience > business criteria (if any) > profile cap > email > wait for x days > profile cap > email > wait for x days etc.,

Can you share the use case ?

Hi, Take a look at the below highlighted note - https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/condition-activity#profile_cap   Couple of options ->> Create 1 journey for every day where you exclude the people you sent the day before>> ...

Take a look at the below guard rail called out in documentation https://experienceleague.adobe.com/en/docs/journey-optimizer/using/get-started/guardrails#:~:text=General%20journey%20guardrails,in%20readability%2C%20QA%20and%20troubleshooting.   Instead, you can explore dataset export option https://...

This conversation https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/create-segment-abandon-cart/td-p/581110  has reference details which should help. (Time duration is configurable & Any event can be added as an exclusion not looking for a specific event type) Other referenc...

Kindly take a look at the following documentation links which has examples on comparison.https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/building-advanced-conditions-journeys/syntax/operators https://experienceleague.adobe.com/en/docs/journey-optimizer/using/c...

You can use the time condition to check for the respective day of week https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/about-journey-building/condition-activity#time_condition    

In the screenshot shared earlier, all of this happens in a single custom action & header ( -H "Authorization: Basic <base64 enconded username:password>") gets appended automatically when the custom action is invoked.

If the end point you are trying to hit supports basic authentication, you don't need custom authorization.