Skip to main content

Condition Nodes

Deliver different supporter journeys based on behaviour, data and timing

đŸ‘©â€đŸ’» At a Glance

Condition Nodes let you branch supporters into different experiences based on their behaviour, data or timing.

When a supporter reaches the node, Social Sync checks the condition and sends them down either the Yes or No branch.

Use Conditions to adapt journeys based on things such as fundraising progress, activity, registration status, event, tags or supporter information.

This allows one Pathway to deliver different experiences to different supporters based on what is true for them at that moment.


Adding a Condition Node

Select the point in your Pathway where you want the journey to branch and choose Condition.

Build the rule or rules that determine which route the supporter should follow.

If the condition is met, they move down the Yes branch. If it is not met, they move down the No branch.

You can also give the node a clear title so its purpose is easy to understand on the journey canvas.


Building Your Conditions

You can add multiple rules to the same Condition Node and combine them using AND or OR logic.

For example:

AND – Amount raised is more than £50 and less than £100.

OR – Segment is Lead or Applicant.

The options available depend on the information you are checking. Numeric fields can use rules such as more than, less than or equal to, while text, lists and segments provide options relevant to that type of data.

This gives you the flexibility to create anything from a simple split to more detailed behavioural logic.


Using Conditions in Your Journeys

Conditions are useful whenever supporters should receive a different experience based on what they have done or what you know about them.

For example, you could check whether someone has started fundraising before sending the next communication:

Yes – They have raised more than £0 → send a congratulations message.

No – They have not raised anything yet → send a fundraising activation message.

Because the condition is checked when the supporter reaches the node, the journey responds to their current behaviour and data at that moment.


Adding a Condition to an Existing Pathway

You can insert a Condition Node into a Pathway you have already built.

If you insert it above existing nodes, the existing journey below it will move onto the Yes branch by default. You can then build the No branch separately.

Always review both branches after inserting a Condition into an existing Pathway to make sure supporters will continue down the intended route.


Editing a Condition

You can update the rules in an existing Condition Node when needed.

For a live Pathway, the updated rules will apply to supporters who reach the node after the changes are published.

Supporters who have already passed through the Condition will not be re-evaluated.


Deleting a Condition

Deleting a Condition Node can affect the journey built beneath both branches.

Social Sync will ask whether you want to keep the Yes branch, keep the No branch or delete both branches.

Review both branches carefully before deleting a Condition, particularly on a live Pathway.


Creating More Relevant Journeys

Conditions let a single Pathway adapt to different supporters instead of sending everyone through the same experience.

Use them to respond to fundraising progress, activity, timing and supporter data so each person receives the next step that is most relevant to them.

Build journeys that respond to the supporter, rather than asking every supporter to follow the same path.

Did this answer your question?