Search signals by key-value pairs

Search for one or multiple signals, based on their respective key-value pairs.
To search for more than one signal, click the Add button. Enter the key-value pairs that you want to search for, then use the following filters to narrow down your results.

  • Signal status: search for signals included in traits, unused signals, or both.
  • View records for: select the time interval in which to search for received signals.
  • Minimum counts: display only signals with the specified minimum total count in the selected interval.
IMPORTANT
For a streamlined user experience, key-value pair search results are based on data sampling. See Data Sampling and Error Rates for details on how Audience Manager uses data sampling and why slight result variations may appear when comparing key-value search to general searches.

When searching for signals using multiple key-value pairs, Audience Manager links the pairs using the logical AND operator. For instance, let’s say you’re performing a search with the following key-value pairs:

  • c_creative == “12345”
  • c_product == “smartphone”
  • c_location == “europe”

This search will return only results that qualify for all three filters on the same call: c_creative == "12345" AND c_product == "smartphone" AND c_location == "europe".

Signals excluded from signal search

Key variables used by Audience Manager and prefixed by the d_ and h_ prefixes are not surfaced by Signals Search. See Prefix Requirements for Key Variables for details.

Case sensitivity and search auto-completion

The key and value search fields are case sensitive. The key search field includes auto-completed suggestions.

Let’s say Audience Manager received the following signals:

  • productCategory == smartphone
  • newProduct == iPhone
  • PRODUCT == phone
  • product == PHONE

When you enter product in the key search field, you receive auto-completed suggestions for productCategory and product.

Similarly, when you search for product == PHONE, Data Explorer returns results only for product == PHONE.

Backfilled trait realizations are also case sensitive. A trait containing the signal with the key-value pair PRODUCT == SMARTPHONE does not qualify the signal with the key-value pair product == smartphone.

de293fbf-b489-49b0-8daa-51ed303af695