Outputs on this page come from a live run on September 10, 2026. Company names are masked to initials. No contacts were previewed or revealed.
A website traffic increase is one of 24 company signals available through the Lusha connector for Claude. It is a demand gen read: the buyer is the CMO, the VP of marketing or the revenue leader who owns inbound, and the pitch is about capturing what the growth brings in.
Check my target account list for website traffic increases and rank who to work first.
Before anything else, run account_usage and tell me my remaining credits. Do not run any signal call if fewer than 50 credits remain; stop and tell me.
Here is my list (domain, one per line):
[PASTE UP TO 25 DOMAINS]
Customer domains (or write "none"):
[PASTE]
Steps:
1. Run signals_companies_search on the list with signalTypes ["websiteTrafficIncrease"], startDate 90 days ago, maxResultsPerSignal 3. Batch in groups of 25 if the list is longer. If a domain comes back "could not be identified," tell me and suggest the canonical domain to retry.
2. For every account that returned an increase, pull the change rate, the historical average visits, the last month visits, and the reading date. Keep accounts with no signal in the output as "no signal" so I see the full list.
3. Rank the hits: two or more consecutive readings first, then single readings by change rate. Show the visit numbers next to the percentage so I can see whether the growth is on a large or a small base. Flag any single reading above 100% as VERIFY.
4. Tell me the most recent reading date in the results. If it is more than 45 days old, say so in one line at the top of the output.
5. Tag customers as EXPANSION and everyone else as NEW LOGO. For the top 5 NEW LOGO accounts, write one opening line addressed to the marketing or revenue leader that references a growing web audience without quoting a number.
Output: one table with columns Account | Traffic change | Visits (avg to last month) | Reading date | Segment | Opening line. Then two lines: what the ranking is based on, and credits used. Do not preview or reveal any contacts in this run.The situation. A list of 25 B2B software companies, mostly product led, 300 to 4,000 employees. No customer domains supplied, so every hit is a prospect.
The run. account_usage first, at zero credits. Then one batch call on 25 domains for websiteTrafficIncrease with a 90 day window. 5 of 25 fired, 5 signal events, 6 credits charged. Two domains could not be identified. The newest reading in the results was dated June 18, 2026, 84 days before the run; the prompt’s freshness check would have said so in the first line.
What came back.
| Account | Traffic change | Visits (avg to last month) | Reading date | Segment | Opening line |
|---|---|---|---|---|---|
| D.R. (compliance automation, ~800 emp) | +33% | 224K to 299K | Jun 18 | NEW LOGO | More people are finding you. The question is how many of them your team can identify before they leave the site. |
| L.N. (project management, ~300 emp) | +32% | 6.1M to 8.1M | Jun 18 | NEW LOGO | An audience that size growing that fast produces more inbound than any team can qualify by hand. Worth ten minutes on how others route it. |
| B.X. (fintech, ~1,300 emp) | +17% | 820K to 962K | Jun 18 | NEW LOGO | When traffic climbs, the leads that arrive incomplete climb with it. We fill the record before the rep sees it. |
| R.P. (HR platform, ~4,000 emp) | +16% | 10.0M to 11.7M | Jun 18 | NEW LOGO | You are pulling in a bigger audience. The gap is usually between who visits and who your team can actually name. |
| A.B. (recruiting software, ~300 emp) | +11% | 16.7M to 18.6M | Jun 18 | NEW LOGO | Growth at the top of the funnel is only useful if the middle can keep up. Happy to show what teams at your stage automate first. |
| 18 accounts | no signal | ||||
| 2 accounts | not identified | One on a .so TLD, one a large consumer design brand. Retry by company name or canonical domain. |
Ranking based on change rate, with visit base shown; no account had two readings in the window. Credits used: 6. Confirmed live via Lusha connector, September 10, 2026. Company names masked to initials.
What happens next. The top five go to the decision maker play with the marketing or revenue leader as the target title. Because the reading here was 84 days old, the honest opening is the direction of travel (“more people are finding you”), not a claim about last week. If the account is a customer, the EXPANSION read is simpler: more traffic means more inbound to enrich and route, and the inbound lead grading play is the natural next conversation.
Traffic is the one number a marketing leader already watches every week, so a conversation that starts there starts on their ground. The connector gives you that number with its base and its date attached, which is what keeps the outreach honest: you can say “more people are finding you” and mean it, and you cannot accidentally claim a spike from last week when the reading is from June, because the prompt tells you. Running it inside Claude means the whole list is checked in one call, the accounts with no movement stay visible so you can judge the list as well as the hits, and nothing is spent on a contact until you have decided the account is worth one. Every signal is sourced under Lusha’s data methodology and compliance framework.
A rise in a company’s estimated monthly website visits against its historical average. The signal carries the change rate, the historical average, last month’s visits, and the reading date. It does not say which pages or channels drove the change.
Because the same percentage on a small base and a large base describes two different companies. The base tells you whether you are talking to a team that just started getting found or one managing a large audience with a new spike.
It depends on the refresh cycle of the signal. In the live run the newest reading was 84 days old. The prompt reports the newest date and warns above 45 days. Use the direction of travel in outreach, not a claim about a specific week.
The marketing or revenue leader who owns inbound: CMO, VP marketing, head of demand gen, or RevOps. The signal describes their number, and the pitch is about capturing what growth brings in.
Signal reads cost 1 credit per event returned, plus the batch identification. In the live run, 25 domains cost 6 credits. account_usage runs first at zero credits and the prompt stops under 50. No contact preview or reveal runs in this play.
Yes. Run the same list against itSpendIncrease and surgeInHiringByDepartment (Marketing) and work the accounts that fire on two or three. The stacked signals play does this in one pass.
One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.
