Catch accounts whose website traffic is surging

Each month, reads website traffic estimates for your top accounts, saves the trend, and flags accounts growing past your surge level.

8 stepsMonthly

The workflow diagram

Catch accounts whose website traffic is surging: workflow diagramThe 8 steps of this workflow, from its trigger to the final step.On the 2nd of every month, for each top account. Scores, schedules and toolsBWWHENTRIGGEROn the 2nd of everymonth, for each top…Scores, schedules and toolsRead website traffic. Paid per resultDATHENRead website trafficPaid per resultWork out the trend. Waits and logicBWTHENWork out the trendWaits and logicSave the trend. Audiences and recordsBWTHENSave the trendAudiences and recordsSurging?Surging?Add to Traffic surging. Audiences and recordsBWTHENAdd to Traffic surgingAudiences and recordsResearching your topic too?Researching yourtopic too?Mark as in market. Audiences and recordsBWTHENMark as in marketAudiences and recordsAlert the owner. AIMEEAITHENAlert the ownerAIMEEThis path stops hereThis path stops hereYesNoYesNo
This is the workflow BrandWell builds on your canvas when you add it. You can change any step.

What this workflow does

Each month, reads website traffic estimates for your top accounts, saves the trend, and flags accounts growing past your surge level. In-market accounts are marked and the owner is alerted.

Why it works. Traffic growth usually follows a launch, a campaign or new funding, and growing companies have the budget and the urgency to buy.

Nothing is sent outside your team, so nothing waits for approval.

How it works

It starts: On the 2nd of every month, for each top account, or run it now.

  1. 1

    Read website traffic

    Runs a BrandWell data lookup and brings the result back into the workflow.

  2. 2

    Work out the trend

    AIMEE classifies, extracts or writes using your instruction.

  3. 3

    Save the trend

    Saves what was found onto the record.

  4. 4

    Surging?

    If yes, it goes on to "Add to Traffic surging". If no, it stops for that person.

  5. 5

    Add to Traffic surging

    Saves the people to an audience you can use anywhere.

  6. 6

    Researching your topic too?

    If yes, it goes on to "Mark as in market". If no, it goes on to "Alert the owner".

  7. 7

    Mark as in market

    Saves what was found onto the record.

  8. 8

    Alert the owner

    AIMEE tells the right person, with the context they need.

What you need

  • Workflow Wallet funds for paid lookups
  • MarketPulse in your BrandWell plan
  • AIMEE in your BrandWell plan
  • A list of target accounts
  • A MarketPulse topic

What it costs

Paid steps are charged per result from your Workflow Wallet, and you set the limit.

  • Assumes plan with MarketPulse intent data enabled. Subscription fees are separate. Pulls use your plan allowance; extra pulls cost more unless explicitly included below.
  • Assumes AIMEE is already enabled in your plan. Subscription fees are separate.
  • Execution estimates are not a total campaign price. External tool subscriptions, model usage, advertising spend and delivery costs are separate unless explicitly itemized.

$4.00 typical per 100 account checks, up to $9.98

Free sources run first when they can answer. You see a price before anything paid runs. Estimates use current customer prices.

Data partners

Free sources run first, then the rest in the order this workflow tries them.

  • Read website traffic

    • Akta by Wokelo