Problem

Campaigns can grow very complex, very quickly. A typical onboarding journey can have:

• Multi-split branching logic
• Dynamic segment conditions
• Split tests
• Event conditions
• Attribute updates
• Time delays
• ….

You may feel confident everything is working as expected when you initially launch, but what about 2 months later? Even after a few weeks you start to forget how you set it up. Why did you have that extra condition check? Even if you have detailed annotations, what if something outside of CIO changes that your logic depends on? A third party API Key is rolled that you didn’t know about?

There are 2 main problems:

1. You forget the intricacies of the logic you (or someone else) set up quickly after launching or updating campaigns. You second guess your setup and spend time manually verifying, or periodically troubleshooting as time goes on.
2. Things out of your control (and outside CIO) can change and break how your campaign functions without you knowing.

As time goes on, it becomes difficult to know your campaigns are still working as expected. Ultimately, this can result in a broken messaging strategy affecting campaign goals and your customers.

Solution

Create API endpoints to Read and Update Actions with type of Delay. This paves a path to testing your campaigns programmatically via the API.

More specifically:

1. The ability to Read in an Action with type of Delay
2. Update an action’s conditions via the API

With this API exposed you can script a way to repeatably test campaign logic and receive immediate results.