Projects and lifecycles are a place to group your related Activities together. Each Project is split up into statuses to give you an overview of the stage your activities are now.
Within each project, you will notice that the activities are further organised depending on their status. This means that your active and running activities are grouped nicely into ‘Prod’, whilst your inactive activities are found in ‘In Dev’. Activities that have been sent to be quality assured are found in QA.
Let's take a closer look at each status and how you should be using them;
This is where you store activities that are in development.
These are being worked on and are not quite ready yet. It could be that you are waiting to add in translations, or to hear back from compliance regulators or still deciding when to fire the activity.
In development activities are kept together in this status and tells you and the rest of your team that this activity is a work in progress.
Here are all the things you can do from this status;
Create a new activity to add to your project
Import an activity that does not belong to another project
Clone some or all of the activities of an existing project. Perfect for reoccurring activities that happen each month such as payday campaigns.
Clone an activity that's already inside your project
Remove an activity from the project. This does not delete the activity, just removes it from the project
Archive an activity that is in the project that you no longer need
Send an activity to QA
Delete an activity from inside the project. The activity will be permanently deleted.
Work on an unfinished activity
Clone a segment that is in use inside the project
Evaluate the segment count from a segment in use in the project
Just like with the QA portal, this is where activities go to be quality assured. This is where activities only from within your project go to be QA'd.
Here's what you can do from QA status;
QA an activity
Reject an activity from QA to return to In Dev status for modification
Sign-off an activity from QA to approve the set-up
Activate an activity after sign-off to move an activity to Prod
Choose to sign-off an activity but not activate at this moment. The activity can be enabled later. This might be useful in case the person QA'ing is not the same team member who needs to enable the activity.
This is where your active and running activities are found. Once an activity has been signed-off and enabled from QA, they move to Prod. From here, you can no longer make changes to your activity. But you might still want to clone or disable it.
Here's a guide to what you can do;
Disable an enabled activity. This will send the activity back to In Dev status
Clone an activity. The cloned activity will be added to In Dev inside the same project, ready for you to make changes.
Check conversion data
Clone the segment used in the activity
Evaluate the segment count (as before In Dev)