Skip to content

One conversation, from a live count to a running feed.

You describe the audience. The chat counts it live against our identity graph, writes the count and the cost onto a card beside you, sends a test record to wherever it is going, and switches it on when you confirm the test landed. From then on it runs on its own and reports to one screen, Overview.
Book a 30-minute demo

The chat that counts and builds

Know in seconds how many of the people you want exist and what they cost, before you spend anything.

You describe the audience in plain English. The chat picks the filters, runs the count against our identity graph of hundreds of millions of people with phones, emails, addresses, property, in-market signals, form fills and callers, and shows the number live. Then it asks the one question that matters: once, on a schedule, or as an audience?

“Homeowners in ZIPs 75034, 75035 and 75071, homes built before 2010, owner-occupied, with a cell phone”

What a roofing company after a hail storm typed into the chat.
New feed

Homeowners in ZIPs 75034, 75035 and 75071, homes built before 2010, owner-occupied, with a cell phone

Counting the audiencedone in 9s

About 38,000 homeowners match, and 31,000 of them have a cell phone that rings.

Do you want them once, on a schedule, or as an audience in your ad account?

Hail-path homeowners

Fills in as you go. The checklist below says what is left.

What
Homeowners in ZIPs 75034, 75035 and 75071, homes built before 2010, owner-occupied, with a cell phone
31,000 in the pool right now
Supply
About 90 a day
New matches, measured over 30 days. First send clears the 31,000 standing now.
You get
Every Monday, up to 700
Goes to
Posts to your dialer webhook
One test record goes first, nothing is live until it lands.
Headroom
About 2,700 a month, inside 250,000
Past that it stops sending rather than billing more.
Cost
Feed 1 of 1 included
No extra charge for this one.

The deal card beside the chat. Every line is written by a live count, never by the assistant. Figures shown are illustrative.

Most data vendors make you wait for a sales rep to come back with a count. Here the count is the first thing you see, and the card beside it shows the cost at your volume, so the decision is yours to make in the same minute.

Book a demo

Where it goes

Records land where your team already works, on the schedule you set, and nothing goes live until a test proves the connection.

The same audience can go out five ways. A one-off file. A recurring feed that posts to your webhook, writes to your S3 bucket, emails a CSV, or waits for your code to pull it. An audience kept fresh in Meta, Vibe or Roku. A pixel that names the people visiting your website. An identity API your own app calls, phone in and identity out. You can also upload your own customer file and ask to be told when anyone in it moves, changes phone or goes in market.

“Homeowners aged 45 to 70 in Florida and Texas with a cell phone, 20,000 records, delivered weekly”

What a call center keeping the floor dialing typed into the chat.

A list you have to download and upload is a list that goes stale. A feed with a passed test send runs on its own, dedupes against what you already have, and stops at its ceiling instead of billing you more.

Book a demo
Test send
Waiting on you

Five real records went to your webhook

POST https://crm.example.com/hooks/tdtm200 OK
  • Dana Whitfield · Plano, TX(555) 010-4471
  • Marcus Oyelaran · Frisco, TX(555) 010-2208
  • Priya Natarajan · McKinney, TX(555) 010-9135
  • Tom Albrecht · Allen, TX(555) 010-6624
  • Renee Castellanos · Prosper, TX(555) 010-3390

No charge for a test. The same five records will not be sent again.

Did they land where you expected?

Then it runs on its own

Not live yetEvery day at 06:00, up to 1,500. First run clears the backlog.

The test send before any feed goes live. Names and numbers shown are invented.

  • Webhook. Each batch posted as JSON to a URL you give us.
  • S3 bucket. A CSV in your bucket on every run.
  • Email CSV. A file to the inbox you choose.
  • API pull. Your code asks for the next batch when it is ready.
  • Ad audience. Kept fresh in Meta, Vibe or Roku.
  • Pixel. Your website visitors, identified as they arrive.
  • Your database. Upload your file, be told when anyone in it changes.

Overview, everything you own on one roster

One screen answers the four questions an owner has about every feed: what is it, how often does it run, did it deliver, and what does it cost.

Every feed, audience, pixel and API key on the account is a row. Each row carries its cadence, when it last ran and when it runs next, a thirty-day sparkline of volume, the cost, and a plain sentence if anything needs attention. Product tabs are for setup. Status lives here.

“People aged 64 to 65 in Florida, Texas and Arizona with a cell phone and a mailing address”

What a Medicare agency running a turning-65 feed and a streaming TV audience from the same list typed into the chat.

When a feed stops you find out from the roster, in words, the same morning, instead of from a quiet month and a surprised sales team.

Book a demo
Overview
5 things running

  • Texas homeowners over $400K

    LiveWebhook

    1,400 in the last 24 hours. 42,000 this month, inside 250,000.

    Every day at 06:00

    Last 2h ago, next in 22h

    Feed 1 of 1 included

    Records count against your plan

  • Turning 65 in FL, TX and AZ

    LiveMeta audience

    48,000 people in the audience. Refreshed this morning.

    Refreshes daily

    Last 6h ago, next in 18h

    $500 a month

    Second feed on the plan

  • Website visitors

    LivePixel · example.com

    310 visitors identified this week. 2,900 since install.

    As they arrive

    Last visitor 4 minutes ago

    2,900 records

    Metered against your plan

  • Customer file, in market for auto

    Test sendYour database · S3

    Waiting on you to confirm the test file landed in your bucket.

    Five test rows were written to s3://example-bucket/tdtm/ 20 minutes ago.

    Every Monday

    Not run yet

    $500 a month

    Charged when you switch it on

  • Identity API

    API keyProduction key

    12,400 lookups in the last 7 days, 9,800 matched.

    When your app calls

    Last call 1 minute ago

    12,400 records

    Metered against your plan

The Overview roster. One row per feed, audience, pixel and API key, with cadence, thirty days of volume and cost. Figures shown are illustrative.

Bring the audience. We count it live.

Thirty minutes. Tell us who you are trying to reach and we run it against the real data while you watch. You leave knowing your count and your cost before you spend anything.

Book a 30-minute demo

What the demo covers

  • The audience you are trying to reach, counted live against the real data.
  • What it costs for your volume, against prices you already saw on the pricing page.
  • How it gets delivered: a recurring feed, the pixel, the API, or your ad platform.
  • Compliance for your specific use case, including DNC and consent.

Prices are published. Read them first so you arrive knowing the numbers.