End trigger

The End step is required to mark how the flow ended:

  • Successful – the counterparty accepted the request
  • Unsuccessful – the counterparty rejected the request
  • Error – an unexpected error occurred (default)

You can also define the rejection reason and view it in reports. Any rejection reasons sent by advertisers can be mapped into your own consolidated set of reasons.

Because Error is the default state, we strongly recommend marking rejected flows explicitly. It makes debugging easier, since real errors stay visible in logs and can trigger notifications.

Insights that
helps you grow

  • Release notes 2026/04/30
    Based on your feedback, we’ve pushed the Integration Builder even further. We’ve rolled out a massive wave of UX fixes and performance updates. Here’s the…
  • Lead Distribution Software
    Lead distribution software is a platform used to route and deliver leads to one or more lead buyers (advertisers) in real time. Instead of sending…
  • Ping tree software and ping (pick) post distribution
    A ping tree (sometimes written as pingtree) is a lead distribution method used to sell a single lead to the right advertiser in real time.…