Skip to content

Delivered where you already work.

Every audience you build in the chat can go to your systems, your ad accounts, your website or your own code. Each connection is proven with a test before anything is live, and every one of them shows up on Overview.

Send records to my systems

A recurring feed delivers to the place your team already works, on the cadence you set, with records you already have taken out. Every run is a batch; every batch is logged on Overview.

One feed carries up to 250,000 records a month. Past that it stops sending rather than billing more.

Webhook

We post each batch as JSON to a URL you give us. Your CRM, dialer or automation picks it up.

To connect: Paste the URL. A test record goes first and you confirm it arrived.

S3 bucket

A CSV lands in your bucket on every run, named by date, so your pipeline can pick it up.

To connect: Give us a bucket and a prefix you control. The test run writes one file.

Email CSV

A CSV attached to an email, to the inbox you choose, on every run.

To connect: An address. The test send is a small file to that inbox.

API pull

Your code asks for the next batch when it is ready for it, instead of us pushing.

To connect: An API key from your account settings and one endpoint. The docs show the exact call.

Keep an audience fresh in my ad accounts

The audience you built in chat is pushed into your ad account and refreshed on a schedule, so the people in it are the people who match today. No file to download, no upload to forget.

One audience carries up to 2,000,000 people.

Vibe

Connected TV

To connect: One click. You approve the connection on Vibe and audiences refresh on their own from then on.

About the Vibe integration

Meta

Facebook and Instagram

To connect: No Facebook login. You share your ad account with us once inside Meta Business Settings, we check the share went through, and the audience refreshes on its own.

Roku

Connected TV

To connect: You approve us in Roku Ads Manager with the Audience manager role on the ad account you advertise from. The connection finishes itself when you land back.

These are the networks you can connect today. Anything not listed is not available yet.

Identify my website visitors

One snippet on your site, and the people who visit and leave without filling anything out come back as names, with a phone, an email and a mailing address where we have them. The chat walks you through the setup one step at a time.

Pixel questions and answers

Website pixel

Install once. Visitors are identified as they arrive and show up on Overview, ready to call, mail, or push to an ad audience.

To connect: Name the site, add the snippet, and wait for the first real visit to prove it.

Set up your website pixel
  1. Name your website
  2. Add the snippet
  3. Wait for a real visit
  4. Choose where visitors go

Step 1 of 4

First, name your website

Give this connection a recognizable name.

Website name

Website domain

A front-end illustration of the guided experience, not a working pixel setup.

Look people up from my app

Phone in, identity out, fast enough to use while a call is still ringing. Name and address in, phone out. Email in, match out. The chat shows you the exact call for what you just built, so it is never a cold start.

API reference

Identity API

Realtime lookups and batch appends from your own code, metered as records against your plan.

To connect: Issue a key from your account settings. The reference has every endpoint and a worked example.

Drive it from my own assistant

MCP is a standard way for an assistant to use tools. You paste one URL into the assistant you already use, sign in to your account when it asks, and from then on that assistant can count, price, order and set up feeds for you, the same as the chat on this site.

It works with Claude Desktop, Claude.ai, Cursor, and any assistant that speaks MCP. Counting and pricing are free from there, the same as on this site, and a good assistant asks you before it spends anything.

How to connect your assistant

Connect your assistant
Server URL
https://www.talkdatatome.online/api/mcp
  1. Add the connector in your assistant

    In Claude, open Settings, then Connectors, then Add custom connector, and paste the URL above. In Cursor, add it as an MCP server. Leave every other field empty.

  2. Sign in when it sends you to us

    Your assistant opens our sign-in page. Use the same email and password you use for Talk Data to Me. You are not creating anything new.

  3. Read the approval screen, then approve

    We show you which assistant is asking, which account it will act on, and exactly what it will be able to do. Approve it and you land back in your assistant, connected.

  4. Ask it something

    Start with a count. Counts and estimates are free, and a good assistant asks you before it spends anything.

The same four steps the connector page walks you through. Every account can connect an assistant; there is nothing to request.

Tell us where it needs to land.

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.