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

  • Free Affiliate tracking software
    Many companies (inlcuding YOU) search for free affiliate tracking software because they want to launch an affiliate program without committing to expensive monthly fees. The…
  • Release notes 2026/06/30
    We implemented numerous performance improvements and feature enhancements based on your feedback. We also significantly expanded the flexibility of the following features: The External Final Page…
  • 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…