Skip to main content

Manage Signals

Signal list

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

  • Target — the destination platform (e.g., Google Ads).
  • Last Run — when the most recent sync ran.
  • Status — current state of the signal (Draft, Ready, Running, 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

Open a signal's detail page to see:

  • Destination status cards — per-destination status (Ready, Running, Complete, Error) and last push date.
  • Status message — detailed error information if a destination is in Error state.

For a complete history of all sync runs across all signals and audiences, use Sync History.

Handling errors

When a signal destination shows Error status:

  1. Open the signal and read the status message on the destination card.
  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.