# Website Visitors integration

> Turn anonymous website traffic into Reply contacts: which accounts can still use it, how identification works, what each visitor costs, and whose consent duty it is.

**Available on AI SDR plans, to teams that already have a tracker, and with a paid add-on; new accounts on other plans no longer see it. A script identifies a share of your anonymous traffic and creates those people as Reply contacts. Identification is partial, every identified visitor consumes credits, and the consent obligations are yours.**

_Status: Reviewed – written against Reply's product documentation on 2026-09-22, not yet confirmed against the running product._

## At a glance

| | |
| --- | --- |
| **Availability** | Available on AI SDR plans, to teams that already have a tracker, and with a paid add-on. Not offered to new accounts on other plans – check yours in Billing |
| **Direction** | One-way: your website → Reply |
| **Sync timing** | Continuous. A visit is processed as it happens |
| **What you need** | The ability to add a script to your site, and a lawful basis for the tracking |
| **Surfaces** | **Setup:** the script goes on your site; the tracker is configured in the app. **Once live:** the contacts identification creates are readable through the API and MCP, and raise webhook events like any other contact |
| **Does not** | Identify most of your traffic · tell you what an individual read · work without consuming credits |

## Availability

Three kinds of account have it:

- **Plans that bundle it, which is the AI SDR family.** New sign-ups on those plans get it too.
- **Any team that has already created a tracker**, whichever plan it is on.
- **Accounts holding a paid add-on.**

Everyone else no longer sees the feature: it was withdrawn from accounts that had never
created a tracker, and the page where a first tracker is created is the page that went with
it. If you cannot find it and none of the three applies, that is why.

The identification itself is provided by a data partner, so coverage reflects that partner's
data rather than anything about your site.

## How to connect Website Visitors

### Before you start

- **Settle the consent question first.** You are placing a tracker on your own site and identifying individuals from it. Depending on where your visitors are, that needs a lawful basis and usually a consent mechanism. This is your obligation, and it is worth resolving before the script goes live rather than after
- Decide what should happen to an identified visitor: sit in a list, or enter a sequence
- Have access to your site's template or tag manager

### Connect

1. In Reply, create a tracker. It is issued with its own identifier.
2. Copy the script and add it to your site, on every page you want covered.
3. Optionally configure what happens to identified visitors: the list or sequence they join.
4. Visit the page yourself and confirm the tracker starts registering activity.

## What to expect

### What you get

| Data | Direction | When | Notes |
| --- | --- | --- | --- |
| Identified visitor | Site → Reply | On the visit | Becomes a Reply contact |
| List membership | – | On identification | If you configured one |
| Sequence enrolment | – | On identification | If you configured one |

### Identification is partial, by design

**Most visitors are never identified.** That is normal and not a fault: identification depends on the visitor matching the partner's data, and a large share of traffic will not. Plan around the identified share being a fraction of your total, and treat the number as a lead source rather than as analytics.

### Credits

Each identified visitor consumes credits. A busy site can consume steadily without anyone watching, which is the most common unwelcome surprise here. Check your balance in the first week rather than the first month.

### What it does not do

- **Tell you what a person read.** This is contact identification, not page analytics. Use your analytics tool for behaviour.
- **Identify everyone**, or guarantee any particular visitor.
- **Work without consent** where consent is required; that is on you.

## Common problems

- **Almost nothing is identified** – expected at first. Compare identified visitors against total sessions over a week rather than judging on a day.
- **Credits are dropping faster than expected** – the tracker is working. Consider restricting it to high-intent pages rather than the whole site.
- **Identified visitors are not entering a sequence** – check what you configured on the tracker, and that the contacts are not being skipped as duplicates. [Full guide](/troubleshooting/contact-was-not-enrolled/)
- **The tracker registers nothing** – confirm the script is on the page and is not blocked by your consent banner before consent is given.

## Pause or disconnect

Remove the script from your site to stop identification immediately. Deleting the tracker in Reply stops processing; contacts already created remain, as does anything they have entered.

## FAQ

### What share of visitors will Reply identify?

A minority, and it varies by audience and geography. Treat identified visitors as a lead source, not as a measure of traffic.

### Does it cost anything per visitor?

Yes. Every identified visitor consumes credits. Restricting the script to high-intent pages is the usual way to control it.

### Do I need consent?

Where your visitors' jurisdiction requires it, yes, and it is your obligation rather than Reply's. Settle this before going live.

### Can I see which pages someone visited?

No. This identifies people; it does not report their behaviour. Use your analytics tool for that.

## Need help connecting Website Visitors?

If the connection fails or data isn't syncing the way you expect, the Reply support
team can check your integration settings with you. Open the
[Reply Help Center](https://support.reply.io/) and send the team a message.

To get an answer faster, include:

- which integration and which sync step is affected
- what you expected to sync, and what happened instead
- the error text from the integration's **Logs**, or a screenshot of it

Don't send passwords, API keys, or access tokens.

## Related

- [CRM and integrations](/capabilities/integrations/) – everything Reply connects to
- [RB2B integration](/integrations/rb2b/) – the same idea from an outside provider
- [Limits](/reference/limits/) – what consumes credits

## Build with Reply

- REST API: [Contacts](https://docs.reply.io/api-reference/introduction) – read the contacts identification creates
- Webhooks: [Webhook events](https://docs.reply.io/api-reference/introduction) – react when an identified visitor enters a sequence
- MCP: [docs.reply.io/mcp](https://docs.reply.io/mcp/overview) – let an assistant work with identified contacts