Trigger

Trigger elements define how a scenario or integration flow is started. Every flow must begin with a trigger.

Start

The Start element is the default starting dot of a flow.

  • It runs automatically whenever the scenario is executed.
  • In an Offer pingtree, assigning a Pingtree type makes it possible to define multiple independent start points within the same flow (for example, separate starts for Ping and Post requests). If no pingtree type is chosen, the default type is Post.

Start on Action

The Start on Action element begins a flow when an some event occurs. Examples include:

  • Receiving a lead (e.g. affiliate postbacks).
  • A webhook delivered from a third-party service.
  • Other incoming signals that initiate processing.

Email Triggers

For email-based flows, dedicated triggers can start the scenario when an event happens in the contact list, such as:

  • Subscription
  • Unsubscription
  • Other defined email events

Insights that
helps you grow

  • Release notes 2025/12/19
    We added country-based categorization. You can now categorize offers, integrations, and other items by a specific country, or keep them global across all markets. We also…
  • Release notes 2025/12/17
    More flexible lead rejection: based on validation rules, filters, or pingtree sales results, by source (iframe, API) or by partner (include / exclude). It is now possible to…
  • Case study: How Lender Orka Ventures Scaled Affiliate Operations
    Orka Ventures, an online lending group that wanted to scale fast across countries and onboard affiliates quickly. Their custom affiliate API and tracking layer soon…