Set up with your AI.
Give your assistant the instructions. Let it help with the work it can access. You and your AI use the same Signal service and the same account flow.
What your AI needs
An assistant that can read these pages can explain setup and prepare a handoff. An assistant that can use a browser can help with the public account flow. To install the tag, it also needs authorized access to edit your website.
Give it your website address and the work email personally controlled by the named person responsible for the account. A business-domain alias that person controls is allowed. Keep that person available for mailbox verification, personal-control and owner confirmation, and any other step the account flow requires them to complete.
The account owner’s address cannot be a consumer email address or a genuinely shared inbox. Notifications start with the owner. Where additional destinations are enabled, a team inbox can be separately authorized for notifications; saving it does not grant account access or subscribe it to every purpose. The installer can be someone else.
This guide works as a general browser or website-editor handoff. It does not establish a tested connection to a named AI app, an installable connector, or an API integration. What your assistant can complete depends on its tools and the access you give it.
Give your AI the next step
Copy this into your assistant. It will ask for the website or account owner’s work email if you haven’t already supplied them.
You can also select and copy the text yourself.
Give it the access the task needs
Connect through your own tools
Use your AI app’s existing browser or website-editor connection. Review the website and actions it can access before allowing changes. If it can only read pages, use it for guidance and continue setup yourself.
Keep the scope on setup
Authorize the specific website and setup work. Use only the account, website, and setup access actually provided. A setup prompt or downloaded guide does not grant access to your account or website.
Keep passwords, verification links, session data, and access tokens out of a pasted prompt. Follow the account flow for proof and permissions. Do not give an assistant broader access to visitor data just to install the tag.
Review choices that belong to you
The company remains the client. A person must handle any action the flow reserves for them. The assistant should bring back a missing permission or owner decision instead of making up an answer, changing privacy controls, or adding paid services.
End access when the work is done
Review the connection in the AI app and website tool you used. Revoke or disconnect access you no longer need and check its expiry where shown. Closing a chat does not establish that an underlying connection has been removed.
If Signal provides separate setup access during the account flow, follow the scope, expiry, and revocation controls shown there. This public guide does not create that access.
Ask for a clear handoff
Your assistant should report the website, the changes it made, and what it actually checked. Keep these results separate:
- Installed: the supplied tag is in the website’s
<head>. - Active: Signal confirms a real visit from the submitted website through that tag.
- Matched and delivered: eligible match information reached a destination.
If the assistant cannot finish, ask it to name the missing access or failed step and prepare the supplied tag and full directions for your installer. The next person should be able to continue without starting the account over.
Share the activation confirmation only when Signal has produced it. It shows the website and confirmation time, without visitor data. It does not prove a match rate, pipeline result, or revenue outcome.
Take the instructions with you
Use the Markdown guide as a readable skill or attach it to your assistant. Use JSON when your tool needs structured instructions. Both point to the same Signal start and describe the same access limits.
These are instruction files. They do not install software, connect an account, or expose an executable API.
If your AI gets stuck
My assistant can’t open the website
Download the Markdown guide and attach it, or paste the setup prompt and the relevant page text. The assistant can prepare the work while you use the public account flow.
It asks me for a connector or an API key
This guide uses the public website. It does not supply a connector, key, or installation command. Continue with your assistant’s existing browser tools, or use the manual setup path. Do not treat generated connection details as Signal instructions.
It needs email verification or website access
Complete the account step yourself when required. Grant only the website access you intend, or ask the assistant to prepare a handoff for someone who already has it. Keep verification links and credentials in their intended account flow.
It says the job is done, but I see no confirmation
Ask which state it verified and where. A code change proves an installation step; only Signal’s receipt of a real visit confirms activation. An unknown state should remain unknown. Work through the setup checks.