Skip to main content
Blog

How do I give users a reason to open my product every day?

Give each user their own alert feed, built from one saved search per user with a webhook for new and closed jobs. Live counts, costs and limits.

Xoel LópezXoel López•November 6, 2026•Updated: November 10, 2026

Tell each user when something new shows up at an account they follow. A company in their territory has just posted the role they sell into, or a role they were watching has just closed. A feed scoped to one user's niche sends a few alerts a week, each about an account that user cares about. It won't fire every day for every user, but each alert gives them a reason to open your product on a day something changed for them.

Why a monthly data refresh gives users nothing to come back for

If the data in your product changes once a month, a user who logged in on Monday has nothing new to see on Tuesday. Personalizing alerts on that data won't make it change more often. Hiring at those accounts changes every day. In the TheirStack data, direct employers posted 393,482 jobs at 160,144 companies today and yesterday, as of 6 Nov 2026. Add a stream of new and closed job posts and send each user only the part that matches their search. Sending everyone the same digest of those changes doesn't work either. A recruiter who places nurses gets the Snowflake hires, a security vendor gets the nursing jobs, and both learn to ignore the email.

An alert brings someone back when it is about something they already asked to follow. Give each user their own search (their accounts, their roles, their countries) and send them only what matches it, which cuts the alerts about accounts and roles they don't follow. A user who follows mid-sized UK financial services companies then gets a few events a week, and every one is about a company they could sell to.

What one user's alert feed looks like

Say one of your users sells security tooling to UK financial services companies with 200 to 2,000 employees. Their search looks for security engineering and security leadership roles at those companies. It found 22 job posts from 17 companies in the last 30 days, about five a week, as of 6 Nov 2026. Six of those posts had already closed.

Using the TheirStack MCP, find the job posts for one user's alert feed with these filters:

  • Job title (any of): security engineer, head of security, ciso
  • Job title excludes: intern
  • Industry: Financial Services (industry id 43)
  • Employees: 200 to 2,000
  • Job country: GB
  • Company type: direct employer
  • Date posted: last 30 days

Return the count of jobs and companies, then the first 10 jobs with title, company size, date posted, closed date and URL.

curl -X POST 'https://api.theirstack.com/v0/saved_searches' \
  -H 'Authorization: Bearer <YOUR_API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
    "type": "jobs",
    "name": "User 1042: security roles at UK financial services",
    "body": {
      "posted_at_max_age_days": 30,
      "job_title_or": ["security engineer", "head of security", "ciso"],
      "job_title_not": ["intern"],
      "industry_id_or": [43],
      "min_employee_count": 200,
      "max_employee_count": 2000,
      "job_country_code_or": ["GB"],
      "company_type": "direct_employer"
    }
  }'

curl -X POST 'https://api.theirstack.com/v0/webhooks' \
  -H 'Authorization: Bearer <YOUR_API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
    "search_id": <SAVED_SEARCH_ID>,
    "url": "https://your-product.example.com/hooks/theirstack?user=1042",
    "active_event_types": ["job_new", "job_closed"],
    "max_events_per_day": 20,
    "secret": "<YOUR_WEBHOOK_SECRET>"
  }'
  • Job titleany ofsecurity engineer, head of security, ciso
  • Job title excludesintern
  • IndustryFinancial Services
  • Employees200 to 2,000
  • Job countryUnited Kingdom
  • Company typedirect employer
  • Date postedlast 30 days
22 job posts from 17 companies in the last 30 days, as of 6 Nov 2026

These are the newest matches from that search, written the way your product could show them:

A closed role is news too. The post is no longer advertised, so the account is worth another look. The first version of this search also matched a summer internship, so we added the intern exclusion before counting. Read a few matches before you hand a search to a user.

When a niche is too broad for a daily feed

A broad search floods the feed. Take a user who sells Snowflake consulting in the US and follows data engineer roles that mention Snowflake. On 6 Nov 2026 that search found 64 job posts from 49 companies posted today and yesterday, and 1,122 companies posting such roles in the last 30 days.

Two counts of job posts: 22 in a month for a narrow UK search, 64 in two days for a broad US searchA niche feed sends a few alerts a week, a broad one dozens a day

The narrow UK search produced 22 posts in a month, while the broad US one produced 64 in two days. If that is more alerts than the user will read, there are three ways to cut them. You can narrow it with company size, a state or the user's own list of target domains (company_domain_or). You can set trigger_once_per_company on a job.new webhook, so a company posting five matching jobs sends one event instead of five. Or you can subscribe to company.new instead, which fires the first time a company matches the search and never again for that webhook.

How to build one alert feed per user with TheirStack

Each feed is a saved search with a webhook on it. When a user picks their accounts and roles in your product, your backend creates both, and from then on we post every match to your endpoint.

The diagram shows the path from a user's preferences to the alert they open. Each user has one saved search and one webhook, and its events land in that user's feed.

  1. Create the saved search with POST /v0/saved_searches. It takes the same filters as a job or company search, and saving it costs no credits.
  2. Create the webhook with POST /v0/webhooks, passing the search_id, your URL and the active_event_types you want: job_new, job_closed or company_new. A webhook checks its search every 10 minutes by default.
  3. Set max_events_per_day so one user's feed can't spend more than you budgeted. Records above it are dropped, not queued for the next day (how the limit works).
  4. Set a secret and verify the signature on every delivery. A failed delivery is retried every hour for 48 hours.

Each job.new or job.closed event costs 1 API credit and each company.new event costs 3, per the webhooks docs. A job webhook counts at most two credits per job, one when it opens and one when it closes. At its current rate, the UK feed above would use at most 44 credits a month. From an AI assistant connected to the TheirStack MCP server, the estimate_saved_search_volume tool tells you how many events a saved search would send per day before you create its webhook, and create_saved_search and create_webhook do the two steps above.

Where per-user job alerts fall short

A job alert only covers companies that post jobs. A company that hires twice a year will rarely show up in a feed, however closely the user follows it.

Each webhook is billed on its own. If two of your users follow the same niche, the same job is sent and charged once per webhook, and a job you already pulled through the search API is charged again when a webhook sends it.

When your account runs out of API credits, webhook monitoring pauses until you add more. A search over the last 30 days picks up the jobs it missed once monitoring resumes. A job.closed event carries the time we detected that the source closed or removed the post, which can be later than the day the employer took it down. Company data has errors as well, so an industry or size filter can let a wrong company in or keep a right one out.

Start with one saved search for one user

Pick the user who follows the narrowest niche, open the UK security search, swap in their filters and read ten matches before you save it. Then attach a webhook to it as the webhooks docs describe, or ask your assistant to do it through the MCP tools.

TheirStack: integrations with AI assistants, automations and CRMs

TheirStack works with the AI assistants, automation tools and CRMs you already use: ask Claude or ChatGPT through the MCP server, send new matches to Clay, n8n, Make or Zapier by webhook, and create leads in Salesforce or HubSpot.

Send one user their first alert this week

Get an API key, save that user's search and put a webhook on it. Every new or closed job that matches lands in their feed.

Start free: 200+ free credits.