A website visitor campaign that runs with nobody touching it

    Who this was forA company with a working website and a visitor identification tool, where identified visitors ended up in a report and went nowhere.

    Website visitor identification campaign

    All case studies

    The drawing

    return visitVisitor identified byname, company, andtitleWebhook processes theleadCompliance filtersMessage picked by thepage visitedSequence, oneenrollment across bothchannelsSequence escalatesSingle exit point

    The problem

    The client could already see who visited the site. Nothing happened after that. Identification was a report somebody might read, not a motion.

    What we built

    An end to end pipeline. The identification event itself triggers everything.

    1. A visitor is identified by name, company, title, and profile.
    2. A webhook picks up the lead and runs compliance filters.
    3. The message is chosen by the page the person visited.
    4. The person enters a sequence. Every return visit escalates it.

    Underneath sits a sequence engine with one enrollment across email and LinkedIn and a single exit point, so nobody gets two sequences at once.

    The compliance filters run before any message is chosen, so a visitor who shouldn't be contacted never reaches the sequence.

    What it produced

    The pipeline runs end to end without anyone touching it.

    The volume is small. About 90 visitor records have come through it so far. We're printing that because it's the honest number, and a small real count is more use to you than a projection.

    Identification, filtering, message choice, enrollment, and escalation all run without a person in the loop. A report became a motion.

    What runs now

    The pipeline runs unattended. We maintain it.

    Your scenario

    If you're paying for visitor identification and reading it as a list, the missing piece is the trigger. Tell us which tool you use and we'll show you where the sequence would hook in.

    Client names are always kept confidential at MMG, so they have been removed from this case study.

    Published April 28, 2026

    Last updated November 2, 2026