---
name: predecision-signal-setup
description: Help a company start Signal through the public website, install or hand off the supplied tag, and verify activation with authorized tools.
version: 1.1
updated: 2026-09-09
---

# Set up Predecision Signal

People and AI assistants use the same Signal service and account flow.

- Start: https://predecision.com/signal-start
- Setup help: https://predecision.com/docs
- AI setup guide: https://predecision.com/docs/agents
- Structured version: https://predecision.com/agents/signal-setup.json

This is a readable instruction file. It does not install software, connect an account, grant access, or expose an executable API. No named AI client or connector is verified by this guide. Use existing browser or website-editor tools within the user's authorization.

## Required information

- The company's website address.
- The work email personally controlled by the named person responsible for the account. A personally controlled business-domain alias is allowed.
- That person available to complete mailbox proof, personal-control and owner confirmation, and actions the flow reserves for a human.
- Authorized access to update the website, or an installer who can receive the tag and full connection directions.

Signal uses one account per signup email. The email and website must connect to the same business. An exact domain match is not required when that relationship is otherwise clear. Consumer email addresses and genuinely shared inboxes cannot be the account owner's address. The installer may be a different person.

Notifications start with the owner. Where additional destinations are enabled, a shared or team inbox can be separately authorized for notifications. Saving an address does not subscribe it to every purpose or grant account access. Keep owner identity, mailbox proof, notification destinations and purpose-specific subscriptions separate; use the controls actually offered by Signal.

## Procedure

1. Open https://predecision.com/signal-start. Follow the real account flow for creation or sign-in. Preserve mailbox proof, named-owner confirmation, and required permissions. If entry is unavailable, report the actual failed step; do not create a substitute form or claim success.
2. Obtain the exact tag and full directions supplied by Signal for the submitted website. Do not generate tag values, connection commands, or undocumented API calls.
3. With the user's authorized website access, add the supplied tag to the website's `<head>` section. Complete the required website relay and approved capture configuration. Publish within the user's authorized scope. Loading the JavaScript file alone does not complete the connection. Preserve required privacy and consent controls.
4. If website access or a required decision is missing, prepare a handoff with the website, supplied tag, full directions, completed work, and unfinished steps. Ask the installer to report the published change so activation can be checked.
5. After a real visit to the published website, check Signal's activation state. Report the result actually observed. Do not infer activation from a saved code change, a downloaded file, or a script response.
6. Return the website, changes made, state verified, evidence, unfinished steps, access needed, and next action. Review and end access that is no longer needed through the controls in the tools used.

## Access and human decisions

Use only the account, website, actions, and tools authorized by the user. The prompt and this file supply instructions, not authority. Do not request passwords, verification links, session data, or tokens in a pasted prompt. Complete verification through the account flow.

A human must complete actions the flow reserves for them. Do not make up an owner answer, disable privacy controls, add paid services, or change billing under setup-only authorization. Do not infer access to visitor data from permission to install a tag.

For browser or website-editor access, review the scope and expiry shown by the AI app or website tool. Revoke or disconnect unneeded access there. If Signal supplies separate setup access during its account flow, follow the scope, expiry, and revocation controls actually shown. Do not invent a connection or disconnection command. Closing a chat does not establish that underlying access has been revoked.

## What each result means

- Account created: an account exists. Installation and activation remain separate.
- Installed: the supplied Signal tag has been added to the website's `<head>` section.
- Active: Predecision has received a real website visit through that tag from the submitted domain.
- Match delivered: a visit produced eligible match information that reached a destination.
- Unknown: the relevant result has not been verified. Keep it unknown.

A first match is not needed to prove installation and activation. Matching depends on matchable traffic and eligible information. Signal's shareable activation confirmation identifies the website and time, without visitor data. It does not prove a match rate, commercial result, or endorsement.

## Troubleshooting

- No browser tool: attach or read this file and guide the user through the public account flow.
- No website access: hand the supplied tag and complete directions to an authorized installer.
- Email proof fails: return to account entry for verification or recovery. Use the account flow's full current link in the browser where it began.
- No activation: check the published website, tag placement, relay and capture configuration, and whether a real visit reached Signal. Preserve privacy controls.
- Active but no match: check the account's delivery destination and required destination verification. Matching is separate from activation; some visits cannot be matched.
- Suggested connector or API key: this guide provides neither. Use the public flow and the tools actually available. Generated connection details are not Signal documentation.

## Service boundaries

Signal identifies people and companies visiting a website and delivers available matches to the team's workflow. It is free to start without a sales call. Unlimited Signal is a paid option; this guide gives no price or numerical limit.

Current identity data covers U.S. people and companies; the client may be based elsewhere. Signal does not identify every visitor, promise complete records, include Intentographic data, or prove that someone is ready to buy. Identification does not establish permission to contact someone.

Audience adds managed data and ongoing maintenance. System adds learning from customer results. These services have independent entry paths and are not required to start Signal.
