Skip to main content

Manage Signals

Signal list​

From the Signals list page you can see all signals in your workspace, along with:

  • Target — one icon per destination platform (e.g., Google Ads). Hover an icon for the destination's account, conversion, connection and current status, with a plain-language explanation when something went wrong (see Reading a status). An icon with a warning marker flags a destination whose last run completed but rejected a significant share of its events.
  • Last Run — when the most recent sync ran.
  • Active — whether the signal is enabled.
  • Status — current state of the signal (Draft, Ready, Running, Complete, Partial Complete, Error, Suspended).

Available actions​

Edit​

Click a signal to open the editor. You can change the name, trigger filters, user match criteria, and destination settings.

Changes do not affect past sync runs. Future runs will use the updated configuration.

Enable / Disable (Suspend)​

Toggle Enabled to start or pause scheduled runs.

  • Enabling a Draft or Suspended signal activates the daily sync schedule.
  • Disabling a Ready signal pauses it. Past runs and their history are preserved.

Duplicate​

Clone a signal to use as a starting point for a new one. The copy is created in Draft status. Rename it and adjust its configuration before enabling.

Delete​

Deleting a signal stops all future runs and removes it permanently, including all its sync history.

Use Suspend instead if you want to keep the configuration for future use.

Monitoring runs​

At the top of a signal's detail page, next to the name, the status badge describes the signal as a whole. Click it to jump to the run that explains it in Execution History. Below the subtitle, a row of small pills counts the destinations by status — for example 1 Error · 2 Complete — so you can see at a glance whether every destination is in the same state.

The detail page has three tabs:

  • Configuration — the signal's name, trigger filters, user match criteria, and value formula.
  • Destinations — one row per destination, with its Account Name, the conversions recorded by the platform over the last 7 days (Recorded · 7d, the analysis cell), the Last Successful Push Date, and its Status. Click a destination's status to open the run that produced it in Execution History.
  • Execution History — every run of this signal, grouped by execution. See Execution History.

Choosing the trigger timestamp​

Every signal needs a trigger table and an explicit timestamp field on that table — the column that marks when the event happened. This is chosen per signal, not during onboarding: two signals on the same event table can each use a different timestamp column without affecting one another.

If you change a signal's trigger table, its timestamp field selection is cleared — you'll need to choose the new table's timestamp column again before you can save.

Use Run Now on the detail page to trigger a run outside the schedule (5 per hour per signal).

Going deeper than the status​

A destination reporting Complete means BPP delivered the events — not that the platform recorded them. Click a destination's analysis cell to open Conversion Analysis, which reads the platform's own conversion figures back: the reconciliation rate, conversions recorded against events sent, Meta's Event Match Quality, Google's own upload jobs, and the error codes behind rejected events.

Handling errors​

When a signal destination shows Error status, or Complete with a warning icon:

  1. Hover the status. The tooltip explains in plain language what happened and what to do — see Reading a status. Show technical details reveals the original error message; Copy for support copies it, with its category and time, ready to paste into a support request.
  2. Common causes:
    • Identifier fields are missing or empty for many event rows — check identifier coverage.
    • The Conversion Action name in Google Ads does not match — verify the Conversion Action ID.
    • The value formula references a field that is not numeric or is missing — check the formula.
    • The connection credentials have expired — re-authenticate the connection.
  3. Fix the issue and the signal will retry on the next scheduled run. You can also re-enable the signal after fixing to trigger a retry on the next schedule cycle.
Last updated on