Reporting on actions for workflows

[squigglebit]

I'm not sure if I'm trying to achieve the impossible. We have 3 different workflows that people get moved through depending on actions they take.

Everyone starts in workflow A, but they can be moved to B or C depending on various criteria, from CTA clicks to website actions. People can also move from B to C.

An example might be "Clicked CTA in X email" or "visited product demo page 3 times in last 7 days"

I am trying to report on the actions or criteria that moved them into the next workflow, is there any way this can be achieved or is it to complex?

[karstenkoehler]

Hi @squigglebit,

There is no out of the box reporting for this, no. However, in workflow A, as a last step before moving records to B or C, you can use branches to determine the criteria you'd like to report on - and simply create a custom property where you log these options.

In other words, before sending records to B, you would add a "Set property value" workflow action to document the reason.

This would currently be the best workaround in my opinion, it unfortunately does not work retroactively.

Best regards!

[squigglebit]

As they do not necessarily complete a workflow before moving onto the next, and the criteria that moves them can be one of several this doesn't work.

For example there is no way to capture a move based on "viewed demo page x times" as this can happen at any point, so "set property value" doesn't seem to work in this case, unless I am missunderstanding

[karstenkoehler · Accepted solution]

@squigglebit it depends on the exact criteria and workflow setup - but if it can trigger a workflow, it can also be a branch criterion, which means it's identifiable and can be documented. Could you share more detail about the criteria?

While not beautiful, you can also break the workflows into smaller pieces, each just taking care of one trigger - while not beautiful, it gives you the insights needed.

In any case, there isn't any reporting functionality which can solve this in your current configuration. You need assisting properties or separate workflows.

[squigglebit]

For example moving you to workflow B is based on you joining the list for B.

The criteria includes things such as

Clicked a CTA in email XYZ

OR

Viewed demo page x times in 7 days

OR

Downloaded whitepaper


Etc

[karstenkoehler]

@squigglebit why can these not be criteria of a branch each, before documenting the reason in a property?