Skip to main content
Set up Plainrouter Signals by creating a workspace, activating your collection domain, and installing the generated browser snippet. The browser setup is complete when Plainrouter stores the first qualifying arrival from your website. Connecting a Meta ad account is optional for this first step. An arrival confirms website collection. Add your consent integration and connect a Meta dataset separately to deliver advertising conversion events.
Registration is open. Review pricing for the Free band’s spend threshold and history retention. Arrival counting is free on every plan.

​
Which setup path do I need?

​
Before you begin

Before you begin, you need:
  • An email address you can access.
  • Access to the DNS provider for your website domain.
  • Access to your website’s shared <head> template or site-wide code injection setting.
  • A consent integration for conversion events and advertising delivery. The identity-free arrival check does not wait for a consent grant.

​
Set up your account

1

Create your account

Create a Plainrouter account.Plainrouter creates a personal team and a default workspace, then opens the Signals setup flow. A workspace keeps one client, brand, or market and its connected resources together.Connecting an ad account is optional. Open Connections when you are ready to configure Meta reporting, Meta delivery, or other available provider connections. You can continue Signals installation without connecting Meta.
2

Name your workspace

Open the Plainrouter dashboard, then go to Settings → Workspace.Give the workspace a name your team will recognize, such as the client, brand, or market name. You can create and switch workspaces later when you need to separate access or data.

​
Join an invited team

Open the invitation email, sign in or register with the invited email address, and choose Join on the invitation page. Opening the link alone does not add you to the team. If you are signed in with a different email, use the account-switch option and continue with the invited address. Invitation links last seven days. After acceptance, Plainrouter opens the invited team’s settings. Owners can resend or cancel pending invitations from team settings. Ask the owner to resend an expired or older link; accepted and cancelled invitations cannot be reused.

​
Set up Signals

Signals collects first-party conversion events from your website through a collection subdomain you control.
1

Enter your website address

Open Signals and continue setup. In Website address, enter the website where you will install Signals, such as www.example.com.The form supplies https://. Use the exact website host, without a page path, query string, or fragment. The website address identifies the site allowed to send events; it is separate from your collection subdomain, such as collect.example.com.
2

Confirm your collection hostname on Install

Saving your website address opens Install directly. Meta authorization and dataset selection are optional and do not gate installation or arrival collection.Under Choose your collection hostname, keep the suggested t label or edit it, for example to collect. For www.example.com, the fixed domain suffix is example.com, giving t.example.com or collect.example.com. Click Use t or Use collect to confirm. Enter only the label, not a complete hostname, URL, or path.The hostname cannot be edited after provisioning. Copy the final hostname shown in the DNS instructions; if your choice is already allocated, Plainrouter can add a suffix. See hostname rules.
3

Add the CNAME record

Copy the CNAME name and target from Plainrouter into your DNS provider. Keep the setup screen open or return to it from Signals.CNAME detection and automatic HTTPS validation can take several minutes. If setup remains pending, leave the record in place and return to Install after your provider has published the change.See Configure DNS and CNAME for provider field guidance and troubleshooting.
4

Install Signals and wait for an arrival

When the collection domain becomes active, copy the generated snippet into the shared <head> of your site, deploy, and visit a page. The snippet sends one identity-free arrival before evaluating consent.After installing, choose I’ve added the CNAME and snippet to record the setup path. This confirmation alone does not verify traffic. Plainrouter verifies the browser installation after the first qualifying arrival is stored for the workspace. The setup screen polls automatically, backs off while it waits, and resumes after you return to the tab. Connect your consent flow separately before sending conversion events or advertising identity.See Install the Signals pixel for the snippet and consent requirements.
For server-side API, SDK, or CLI access, the workspace owner manages the Signals secret under Settings → Workspace → Server secret. Follow API secret rotation to install and verify a replacement before confirming it. The secret is shown once. The browser snippet uses the publishable key and must never contain this secret. Managed-hostname setup can also recognize qualifying verified server revenue. The identity-free POST /api/v1/verification-events operation remains available as a server-side diagnostic, but it does not count as real arrival or revenue evidence and does not complete onboarding. See Test Signal ingestion.
Signal setup is optional and resumable. Closing the setup screen does not remove your collection domain or log you out.

​
Confirm your setup

Your initial Plainrouter setup is complete when:
  • Signals shows setup as complete after receiving the first qualifying arrival on an active collection domain.
  • Your workspace name clearly identifies the client, brand, or market it contains.
You can now return to the dashboard and continue working from the workspace you created. Before the workspace’s first arrival, Dashboard and Signals show installation instructions directly. For a provisioned managed hostname, copy the CNAME and browser snippet there; you do not need arrival data to access them. The screens refresh while waiting for collection. Open Signals → Install for hostname selection and the full verification controls. After the first arrival, use Signals for actual collection and reporting. The Dashboard no longer shows sample charts. See billing setup to interpret a checkout notice.

​
Why is setup still waiting?

​
Continue from here

Choose the next step that matches your goal:

Choose an SDK or CLI

Add server-side conversions to your application or inspect events from a terminal.

Track conversion events

Add purchases, leads, checkouts, and other events to your implementation.

Review browser measurement

Review the installed Signals pixel and troubleshoot consent-aware website events.

Connect Meta

Send paired browser Pixel and server events with automatic deduplication.

Read signal health

Read arrival windows, platform read states, and account-scoped delivery diagnostics.

Connect an agent

Authorize one ad account for a compatible MCP client.