---
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.5
updated: 2026-10-15
---

# Set up Predecision Signal

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

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

**Current connection status (checked September 18, 2026):** Direct OAuth/MCP connections are disabled in production. Use the browser-assisted setup flow. A displayed connection address does not establish availability or named-client compatibility.

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.

## Start with your AI chat

Open https://predecision.com/signal/setup?help=ai to create or resume your account, choose your website and platform (or say you are not sure). Get AI help opens with the instructions for that website. Use Copy installation prompt and paste those instructions into your usual AI chat. The optional overview at https://predecision.com/docs/agents is for asking questions first; copying it is not a setup requirement. Tracking code goes on the website; instructions for AI go in the chat.

Ask which website builder the user uses, such as WordPress; help them find out if they do not know. Give one action at a time. If you cannot browse or edit, guide them or prepare the exact tag and directions for their website person. Never request passwords, sign-in links, API keys, account tokens or visitor records in the chat. Return to Signal for Check installation and explicit privacy responsibility acknowledgement. Customer setup complete, service ready, a real visit received and match delivered are separate states.

Manual instructions: https://predecision.com/docs#setup. Website-person handoff: https://predecision.com/docs#handoff.

## 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/setup?help=ai for guided AI setup, or https://predecision.com/signal/setup for manual setup. 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. Check first whether the exact issued combined script is already present; do not duplicate or replace it merely to restart setup. The returned `predecision_hosted` transport needs no merchant relay; use the actual transport for each website rather than inferring it from a platform name. For other connection types, follow the exact current Signal directions. Publish within the user's authorized scope. Loading the JavaScript file alone does not complete the connection. Preserve required privacy and consent controls.
4. Use Signal’s **Check installation** action. This verifies website control and script placement, not capture or activation. Follow the remaining privacy and service steps separately.
5. 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.
6. After saving the final customer step, read the website status. Supported service connections reconcile automatically. Report setup complete and ready to receive visits separately; the first visit is not another customer setup task. Do not invent a manual activation requirement. After a real visit to the published website, check Signal's activation state for the current installation revision. Report the result actually observed. Do not infer activation from a saved code change, a downloaded file, or a script response.
7. 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.

Only if https://predecision.com/signal/connect reports that direct connections are available, and your AI tool supports them, use that optional entry within the access the user authorizes. This does not establish compatibility with a named AI client or give the assistant website-editing access.

## 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.
- Ready: current status for the same website and installation revision reports `operations.state: enabled` and `processing.enabled: true`. No first visit is needed to finish customer setup.
- Active: Predecision has received a real visit through the current installation. Historical activation does not establish current processing.
- Paused: current processing is disabled or held, even if setup was completed earlier.
- Match delivered: a visit produced eligible match information that reached a destination.
- Unknown: the relevant result has not been verified. Keep it unknown.

Do not reinstall or rotate a working tracker after an application update. If an existing installation needs expired-proof recovery, preserve its code and ask the signed-in human owner to use **Verify existing installation**. Setup agents cannot use that owner-only recovery route.

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, remaining privacy/service steps, and whether a real visit reached Signal. Mapped hosted Shopify does not require a merchant relay. 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.

## Privacy and cookie setup

After installation, collect one choice: <a href="https://termly.7zqw8y.net/predecision" target="_blank" rel="noopener noreferrer">Termly</a>; an existing CMP with its name; or a custom, proprietary or in-house solution. Both <a href="https://termly.7zqw8y.net/predecision" target="_blank" rel="noopener noreferrer">Termly</a> entry points open the same normal setup page. Save a draft so the person or an authorized agent can resume it. Present the saved exact attestation wording and record it only after the customer's explicit confirmation. Existing users can sign in through the same setup link. Never infer consent from choosing a platform. Use `signal_privacy_setup` with the saved revision through an authorized MCP connection, or use the website form. On conflicts, reload before changing another actor's work. Opening <a href="https://termly.7zqw8y.net/predecision" target="_blank" rel="noopener noreferrer">Termly</a> is not completion; no partner callback or API connection is currently provided. The customer acknowledgement does not verify compliance, install a CMP, or authorize visitor processing.

Open customer-facing Termly links in a new tab. Keep actual policy, form and service resource URLs unchanged.

## Saved choices, readiness and notifications

Read `privacy_setup.revision`, `attestation_text` and `current_attestation_version` before changing choices. Draft requests use `customer_attested: false` and `attestation_version: null`. After explicit customer confirmation, send `customer_attested: true`, `attestation_version` equal to the returned `current_attestation_version`, and `expected_revision` equal to the saved revision. MCP arguments also include `website_id`. The response field `current_attestation_version` is not a request field.

Saving the final required customer step automatically reconciles supported service readiness. The acknowledgement does not override visitor consent or service holds. Read the saved choice and current website status before reporting completion; never treat a successful save alone as proof of current processing. An unknown/custom CMP name is not proof of an implemented consent adapter.

Notification addresses require mailbox confirmation and the owner's alert choice. Adding an address alone is not subscription; an opted-out recipient requires a fresh double opt-in. Setup agent access cannot change notification subscriptions. Add notifications@predecision.com to the address book. First-day matches are grouped into one summary after the initial 24-hour window; later visits use realtime alerts. Resolution and email arrival are not guaranteed instantaneous.