Every scenario begins with a Start node. It is the entry point: the flow starts here and runs immediately.
The Start node itself does nothing to the data. It marks where the flow begins and what kind of flow it is.
The type follows the scenario
A Start node belongs to one of the four contexts: Integration, Structure, Tracking or Feed. That decides what data the flow receives and what it is expected to give back. See Where Connection Creator is used.
Everything the scenario starts with is available from the Start node onwards: the fields of the structure the lead came from, the system parameters, and whatever arrived in the incoming request.
One Start, except in integrations
Most scenarios have a single Start node. Integrations can have several, because an integration is really several separate flows sharing one canvas.
In an Offer pingtree you choose a pingtree type on the Start node:
- Ping asks the advertiser whether they want the lead, and at what price.
- Post submits the lead.
If you do not choose one, the Start node is a Post.
Each of these is an independent path with its own Start and its own End. Never connect them.
Some advertisers add a third step, where the lead has to be confirmed with a code sent to the customer. That verification also gets its own Start node.
It runs straight away
Once the scenario starts, the Start node runs immediately. There is nothing on it to delay that. If the flow needs to wait before doing anything, put a Wait node right after it.
