Check target accounts for website traffic spikes in ChatGPT

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: ChatGPTLusha
Type: Prompt

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own target accounts to see live results.

A website traffic spike usually means something changed.

Maybe the company launched a campaign. Maybe demand is rising. Maybe a new product, market move, announcement, or hiring push is driving more attention. On its own, a traffic increase does not prove buying intent. But paired with the right account, persona, and supporting signals, it can show which accounts are worth prioritizing now.

The problem is that most teams only react to traffic on their own website. They miss signals happening at the account level.

This prompt uses Lusha in ChatGPT to check a target account list for recent website traffic increase signals, enrich each matched account, look for supporting signals, identify relevant contacts, and create an outreach angle tied to what changed. Instead of treating every target account the same, you can prioritize the ones showing real movement.

How to start

1

Open Lusha in ChatGPT

Go to Lusha in ChatGPT and click “Start chat.” Every conversation started this way is automatically Lusha-enabled.

2

Or invoke Lusha in any existing conversation

Type @Lusha in the prompt bar and select Lusha from the dropdown. Unlike Claude, Lusha does not activate automatically in every ChatGPT conversation. You must invoke it every time.

3

Paste your target accounts and send

Copy the prompt below, paste your company names or domains, add your target persona and product context, and send. Lusha checks the accounts for website traffic increases, supporting signals, and relevant contacts.

The prompt

Start from Lusha in ChatGPT or type @Lusha before sending.

@Lusha Check these target accounts for recent website
traffic spikes and help me decide which ones are worth
prioritizing.

TARGET ACCOUNTS:
Paste company names or domains:
1. [company name or domain]
2. [company name or domain]
3. [company name or domain]

TARGET PERSONA:
Persona or title: [Marketing, Growth, Sales, RevOps,
Product, Operations, or other relevant persona]
Department: [department]
Seniority: [manager / director / VP / C-level]

TIME WINDOW:
Look for website traffic increase signals from the last
[30/60/90/180] days.

MY PRODUCT:
[One sentence describing what you sell and the problem
it solves]

Using Lusha, do the following:

1. MATCH AND VERIFY THE ACCOUNTS
   Match each company to the correct Lusha company profile.
   Return company name, domain, industry, employee count,
   HQ location, and match status.

   If a company cannot be matched, flag it clearly.

2. CHECK WEBSITE TRAFFIC SIGNALS
   For each matched account, check for website traffic
   increase signals in the selected time window.

   For each signal, return:
   - Signal date
   - Historical average visits, if available
   - Last month visits, if available
   - Change rate percentage
   - Whether the signal is strong, medium, or weak

3. CHECK SUPPORTING SIGNALS
   Check whether the same account has supporting signals
   from the last 6 months.

   Prioritize:
   - Hiring surges
   - Hiring surges by relevant department
   - Headcount increases or decreases
   - IT spend changes
   - Commercial activity news
   - Corporate strategy news
   - Financial events news
   - People news
   - Product activity news
   - Risk news
   - Promotion or company-change signals for relevant contacts

4. EXPLAIN WHY THE SIGNAL MAY MATTER
   For each account with a traffic increase, explain what
   the signal may suggest based on my product and target
   persona.

   Keep the explanation grounded. Do not assume the company
   is actively buying my category unless Lusha returns a
   relevant supporting signal.

5. PRIORITIZE THE ACCOUNTS
   Rank the accounts:

   Tier 1:
   Website traffic increase + strong ICP fit +
   supporting signal or clear persona relevance

   Tier 2:
   Website traffic increase + strong ICP fit,
   but no supporting signal

   Tier 3:
   Weak signal, unclear relevance, or no urgency

   Hold:
   No verified traffic increase signal in the selected
   window

6. FIND STARTING CONTACTS
   For each Tier 1 account, find 1-2 relevant contacts
   matching the target persona.

   Return:
   - Name
   - Current title
   - Department
   - Seniority
   - Location
   - LinkedIn profile if available
   - Verified business email availability
   - Direct or mobile phone availability
   - DNC status if available

7. CREATE THE OUTREACH ANGLE
   For each Tier 1 account, write:
   - One subject line under 7 words
   - One opening line under 30 words
   - One discovery question tied to the traffic signal

   Do not:
   Say "I saw your website traffic spiked" in a creepy
   or overly direct way.
   Overstate what the signal proves.
   Invent campaigns, launches, vendors, projects, or
   initiatives that Lusha did not return.
   Make the message sound like a surveillance note.

8. OUTPUT FORMAT
   Return:
   - Account table
   - Website traffic signal, if found
   - Supporting signals, if any
   - Priority tier
   - Recommended contacts
   - Outreach angle
   - Discovery question
   - Accounts with no verified traffic signal

Do not invent companies, contacts, emails, phone numbers,
or signals. If Lusha cannot verify a traffic signal for
an account, mark it clearly.

What you’ll get back

 

A target account check that shows which accounts have recent website traffic increases, which signals support the movement, and who to contact next. Here’s what the output looks like:

Website traffic spike check — Lusha

FieldValue
Account checkedHxxxxot · matched by domain
Website traffic signalApr 11, 2026 · 52.6M visits last month · +11% above historical average
Supporting signalIT spend increase · hiring surge detected in recent months
Priority tierTier 1 · traffic movement plus supporting account signals
Recommended contactR.M. · VP Growth · verified email available · mobile available
Outreach angleRecent demand movement may make lead routing, follow-up speed, or conversion workflows more timely

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own target accounts to see live results.

 

Why use Lusha in ChatGPT to check website traffic spikes

 

Website traffic increases can point to movement inside an account. A company may be seeing more demand, launching campaigns, entering a new market, promoting a product, or getting more attention from buyers, partners, or the press.

Lusha helps turn that movement into a practical account check. The prompt takes the target accounts you already care about, checks whether they have verified website traffic increase signals, looks for supporting signals, and identifies relevant contacts. That gives the rep both the account context and the person to start with.

The supporting signal step matters because traffic alone is not always enough. A traffic increase plus hiring growth, IT spend movement, product activity, commercial news, or relevant team expansion gives the outreach more context. It helps reps avoid awkward “saw your traffic went up” messages and focus on what the signal may mean for the buyer.

The result is a prospecting motion built around account movement, not just static filters.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use. Lusha is GDPR compliant and covers contacts across North America, EMEA, and APAC.

FAQ

  • Why is a website traffic spike useful for prospecting?

    A website traffic increase can suggest rising demand, campaign activity, product interest, market attention, or another change at the account. It does not prove buying intent by itself, but it can help identify target accounts where a timely conversation may make sense.

  • Why should I paste target accounts instead of asking for any company with traffic spikes?

    This play works best when Lusha checks a known account or account list. Starting from target accounts keeps the workflow more accurate and useful because the output can focus on verified traffic signals, supporting account signals, and relevant contacts at companies you already care about.

  • Should I mention the traffic spike directly in outreach?

    Usually not directly. The prompt asks ChatGPT to turn the signal into a natural business angle rather than saying “I saw your traffic spiked.” The message should feel relevant, not intrusive.

  • What if an account has no website traffic increase signal?

    The prompt asks ChatGPT to mark that account as “Hold” rather than forcing an angle. You can still check for other signals, such as hiring surges, IT spend changes, company news, promotions, or company changes.

  • Who should use this prompt?

    This prompt is useful for teams selling to Marketing, Growth, Sales, RevOps, Product, Operations, or any buyer responsible for converting demand, managing pipeline, or responding to market activity.

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.