# Install your tag and confirm your first visitor alert

Follow this guide to install the XSeller tag, check for visitor activity, and confirm a Slack message in your chosen channel.

## Before you start

[Sign in and choose your workspace](/support/sign-in). Use a workspace owner or admin account for setup. You need permission to edit your website, or help from someone who can. Connecting Slack also requires permission to authorize the app in your Slack workspace.

Available contact fields and delivery features depend on your plan and access. A website visit does not guarantee that XSeller can identify a person or find their email.

## 1. Add your website and get its tag

During onboarding, enter your website on **What is your website?**, then choose **Next step**. XSeller creates a tracking tag and opens **Install the tag**.

If you have already left onboarding:

1. Open **Tracking** at `/tracking` and add your website under **Domains**.
2. Open `/tracking/pixels` and choose **Create a tracking tag**.
3. Select the domain, enter a name and choose **Create tracking tag**.
4. Open the tag and copy its **Installation snippet**.

Use the snippet generated for this website in this workspace. Do not copy a sample tag from another account. Domain ownership verification is separate from checking whether the tag has fired.

## 2. Install and publish the tag

On **Install the tag**, choose **Copy**. Paste the complete snippet just before your website's closing `</head>` tag, so it loads on every page you want to track. Publish the website change.

If someone else manages the website, use **Someone else looks after our website** in onboarding to send the installation instructions to them. Sending instructions does not install the tag; they must publish the change.

A newly created tag may take a couple of minutes to become available. After publishing, visit a page on the actual website that contains the tag.

## 3. Check that an event reached XSeller

Return to the installation screen or the tag's detail page and choose **Check now**.

- A positive result means XSeller has recorded the tag firing at least once.
- **Nothing has reached us yet** means there is no recorded event yet. Check that the website change is published, the snippet belongs to the correct domain and workspace, and the tag is enabled. Allow time for a new tag to become available, then visit the page and check again.

**Check now is not a fresh scan of your website.** A tag that fired previously can still have a positive result after a later installation problem. Use recent visitor activity to check that traffic is still reaching XSeller.

## 4. Find the visitor activity

Open **Visitors** at `/visitors`. The list starts with identified visitors. If it is empty, change **Status** to include anonymous or unresolved visitors and clear search or date filters that could hide the visit.

Visitor activity and identity resolution are separate. A recorded visit can remain anonymous, and an identified visitor may appear later. Reload the list after allowing processing time; do not treat an empty identified list as proof the tag is broken.

Inspect the available visitor details and page activity. Contact fields depend on the data available and your plan. If you choose to reveal contact information, review the displayed availability and allowance first. Revealing a contact is not required to test the Slack connection.

## 5. Connect Slack and confirm a test message

1. Open **Integrations** at `/integrations` and select **Slack**.
2. Choose **Add to Slack**. During onboarding, the button is **Connect Slack**.
3. In Slack, choose the intended workspace and channel and approve the connection.
4. Back in XSeller, check the channel shown and make sure the connection is **Sending**, not **Paused**.
5. Choose **Send a test message**. This sends a real message to the connected channel.
6. Open that channel in Slack and confirm that the message arrived.

The on-screen preview is an example. A connection marked connected, or a **Test sent** message, is not your final receipt: the message appearing in the intended Slack channel is the check.

If connecting is unavailable, follow the displayed error or access restriction. If the test fails, use its error message; do not assume reconnecting will fix every failure.

## 6. Confirm a real visitor alert

The test proves the connection can send a test message. It does not prove that a real website visitor has been identified and delivered.

Leave the connection **Sending**. Slack alerts are for identified visitors, not anonymous ones. When an identified visitor alert arrives, compare its visitor and page details with XSeller and confirm it appeared in the intended channel.

**Last sent** and **This week** show recorded successful runs; they help you investigate, but the Slack channel is the final place to confirm receipt. There is no guaranteed identification or delivery time in this guide.

## If you get stuck

| What you see | What to check next |
| --- | --- |
| No recorded tag event | Published website, correct snippet/domain/workspace, enabled tag, time for a new tag to become available |
| Tag has fired, but Visitors looks empty | Status, search and date filters; processing time; whether recent activity exists |
| Anonymous visitor, no Slack alert | Identity is not yet resolved; anonymous visitors do not trigger these alerts |
| Slack connected, no test message | Correct channel, displayed test error, Slack permissions and Sending/Paused state |
| Test arrives, no real visitor alert | Whether an identified visitor is available and sending remains enabled; compare visitor activity and delivery records |

When asking for help, include the workspace name, website domain, approximate event time and time zone, the step that failed, and the displayed error. Do not include sign-in codes or Slack credentials.