For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tuning your signals

Every signal in your feed comes from a signal config. A config is a standing rule, such as "any job post at my accounts that mentions Kubernetes", with a filter over technologies, job functions and other attributes. A config that matches too much fills your feed with signals you skip. One that matches too little goes quiet for weeks. This page explains how to tell which is which and what to change.

You can ask Ask Sumble "which of my signals are noisy?" or "why am I getting so many Snowflake signals?". It reads the same numbers described here and points you to the config to change.

What to look at

Ask Sumble reports these numbers for each config over the last 12 weeks by default:

Number
What it tells you

Delivered

How many signals the config sent.

Share of feed

This config's part of everything you received.

Click rate

Delivered signals you opened, favorited or gave feedback on.

Positive rate

Delivered signals you opened, favorited or marked relevant, without marking them not relevant.

Not relevant rate

Delivered signals you marked not relevant.

Not relevant reasons

The reasons you picked, such as Not my geography, with the most common values, such as Germany.

Weekly delivered and zero-signal weeks

How steady the config is, and how many weeks it sent nothing.

Reps see only the signals delivered to them. A customer admin whose configs are all shared across the company sees totals for everyone at the company. Otherwise the numbers cover only the admin's own signals.

Compare configs with each other

There is no single good click rate. A first-mention technology signal is rare and usually worth a look. An any-mention signal at a large account fires every week and most of those posts are routine. So compare each config with your other configs rather than with a fixed number. A config with half the click rate of your others and a third of your feed deserves a look. The same click rate on a config that sends two signals a month probably doesn't.

Give a new config a few weeks before judging it. A handful of signals is not enough to say much.

Too broad

Signs:

  • A large share of your feed with a click rate well below your other configs.

  • A high not relevant rate, especially when one reason dominates.

The dominant reason usually tells you what to change:

Reason
Likely fix

Not my geography

On the account list, set Countries to use for Signals for the whole list or for one organization in it. The most common values show which countries to drop.

Not my account

Check that account ownership in your CRM is current, since signals follow the account owner. To stop signals for an organization or its subsidiaries, turn off Include this organization in Signals or Include subsidiaries in Signals for it on the account list.

Not a relevant tech

Remove that technology from the config's filter. If the technology is relevant but the volume is too high, switch the config from any mention to first mention by company or team.

Not a relevant project

Remove that project from the config.

Not a target persona or Not a target team

Narrow the job functions or job level in the config's filter.

Not a useful signal type

Lower the config's priority or delete it.

When the feedback is free text, read the most common values. They often name the exact technology or team that doesn't belong.

Too narrow

Signs:

  • Many zero-signal weeks.

  • Steady weeks followed by a long run of nothing, which can mean the filter no longer matches anything.

Possible fixes are adding related technologies or job functions, adding organizations, or using a longer lookback window. A first-mention config is quiet by design, so weigh zero-signal weeks against how rare the event is.

Low value

A config that delivers every week but almost never gets a click or a relevant mark is still costing you attention. If nobody acts on it, narrow it or delete it. If your plan has a signal limit, a config that sends most of your feed can also use up the limit before your other configs run. Lowering its priority doesn't change that, so narrow the filter instead.

Making the change

Open the config from My Team > Configurations > Signal configurations, or follow the link Ask Sumble gives you. Your company's admins can edit configs shared across the company, and you can edit configs you own. If you can't edit a config, send the change Ask Sumble suggests, with the numbers behind it, to one of your admins. Signal configurations covers every field.

Last updated