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/02/27
    After months of work, our Integration Builder has a fresh new look and a lot more power. We redesigned it to be easier to use,…
  • 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…