Flow Builder: Starting Point

What does the Starting point do?

The Starting point holds the entry logic of the whole Flow in one place. Keaz describes it as deciding when and how a Flow begins with your contacts, and that is exactly the split worth keeping in mind: the trigger event is the when, and the labels and filters are the who. Every other block in a Flow sends or waits; this one selects. For the structure a Flow is built from, see what a Flow is made of.

Which trigger event can you choose?

The trigger event is the only required field, and there are five, grouped by where the event comes from.

• Shopify event — Contact purchase for an order placed in your shop, and Abandoned checkout for a checkout that was started and never finished.
• Keaz solutions — Smart activation, where Keaz works out the moment to reach each contact, and Webhook, where another system calls Keaz.
• WhatsApp event — Chat-in, where the contact writes to you first.

Pick the trigger before anything else. It decides which filters make sense: order value only means something on a Shopify event, and a Chat-in Flow is reacting to a message rather than to a purchase.

How do labels and filters narrow who enters?

Contact labels are optional. Pick one or more from the dropdown, which has a search field, and only contacts carrying that label enter the Flow. If you have not used them before, how labels work explains where they come from.

Filters are also optional and match on customer activity in your store. The important rule is that everything you set has to be true at the same time. The trigger fires, and then each label and each filter has to agree before the contact enters — so a long list of conditions is a narrow Flow, not a thorough one.

Which filters can you use?

• Contact type — an existing contact or a new one.
• Opt-in level — a minimum level the contact must have reached. What each level permits is set out in how subscribing and unsubscribing works.
• Order count and Order value — how many times the contact has bought, and for how much.
• Product name, category, type and tag — what was in the order, at four levels of precision.
• Customer country — where the customer is, which is how you keep a language-specific Flow to the right market.
• Email and SMS marketing consent — the consent the contact has given on the other channels.

Add filter adds another condition and Reset all clears them again. Because the product filters combine shop data with contact data, one Flow can address buyers of a single product line differently from everyone else — our guide to targeting Flows by product works through when that is worth doing.

How do you add revenue tracking?

Revenue tracking is optional and lives in the Starting point too. You give the discount code an internal title, choose whether it is a percentage or a fixed amount, and set the value. Keaz then creates the code, and once it is active the Starting point shows it on the canvas so you can see at a glance that the Flow is being measured.

The code is what lets Keaz attribute orders to this Flow rather than to your shop in general, and you can pull its details into your messages as variables instead of typing them out. Give every Flow its own code — one discount code per Flow explains what a shared code costs you in reporting.

What is the Tips badge?

A Tips badge appears on the Starting point block with hints for the trigger and the conditions you have chosen. It reacts to your configuration rather than showing the same advice every time, so it is worth opening when a Flow is not entering the contacts you expected.