Derived Signals derived-signals

A derived signal qualifies site visitors for additional traits based on a trait they’ve already seen. In other words, additional trait qualification can be derived from a currently exhibited trait even if a user has never seen the new trait before.

Purpose of Derived Signals

In Audience Manager, you can create a relationship between signals (or trait rules) passed in during an event call to other, specified signals or traits. For example, assume an event call passes in a signal composed of the key-value “product = new_car” ( https://<domain alias>/event?product=new_car). Audience Manager would connect that signal to any others created with the derived signals tool. Although the associated signals can be any key-values you specify, they are most useful when linked to existing signals already set up as Trait Builder rules. For example, in the illustration below, when a user action fires the signal “product = new car” that user can also qualify for traits defined by the target key and value signals.

Location of Derived Signals

Create and manage derived signals in Tools > Derived Signals from the sidebar navigation.

Create a Derived Signal create

To create a derived signal:

  1. Select Derived Signals from the Tools menu.

  2. Provide a:

    • (Optional) Integration Code
    • Source Key
    • Source Value
    • Target Key
    • Target Value
  3. Click Add Signal.

The character limit for the Source Key, Source Value, Target Key, and Target Value fields is 228 characters.

Edit a Derived Signal edit

To edit a derived signal:

  1. Hover over the signal, then click Edit.
  2. Make the required code, key, or value changes, then click Save.

Delete a Derived Signal delete

To delete a derived signal, hover over the signal, then click Delete.