Console Guide

The Beacon Console at dial.wtf/console/beacon  is where you create and manage Beacon projects. It handles project setup, config publishing, key management, domain allowlisting, and analytics.

Getting Access

1. Connect your wallet — Sign in with your Ethereum or Solana wallet via SIWE/SIWS
2. Request access — Submit a whitelist request with your company name, website URL, segment, and primary use case
3. Get approved — Once approved, you can create Beacon projects

Beacon access is separate from Dial API/SDK access — each product has its own whitelist.

Console Structure

The console is organized into a project dashboard with six tabs:

Creating a Project

1. Navigate to dial.wtf/console/beacon
2. Click Create Project
3. Enter a project name and website origin (e.g., https://example.com)
4. Your project ID is generated automatically

Each wallet can create up to 3 Beacon projects.

Install Tab

The Install tab provides:

• Script snippet — Ready-to-paste <script> tag with your project ID
• AI coder instructions — Copy-paste instructions for AI coding assistants to install Beacon
• Installation status — Shows whether Beacon has pinged from your site, confirming the script is active

Configure Tab

Build and manage your Beacon configuration:

• Visual config builder — Edit branding, quick actions, lanes, triggers, verify gates, FAQ, and handoff
• Version history — Each publish creates a new version
• Publish — Push the current config live
• Rollback — Revert to any previous version

The config follows the schema documented in Config Reference.

Keys Tab

Generate publishable keys for domain validation:

Keys are:

• Stored as hashes (the raw key is shown once at creation)
• Revocable at any time
• Scoped to a specific project

Include the key in your script tag:

<script
  data-dial-project="your-project-id"
  data-dial-key="beacon_pk_live_..."
  src="https://cdn.dial.wtf/beacon/v1/dial-beacon.min.js"
  async
></script>

Domains Tab

Manage which domains are allowed to load your Beacon config:

• Add domains per environment (development, production)
• Wildcard support: *.example.com matches all subdomains
• Beacon validates the Origin header against your allowlist before serving config

Analytics Tab

View Beacon engagement metrics:

• Event counts by type (viewed, opened, action clicked, verified, etc.)
• Period filters — 24 hours, 7 days, 30 days
• Funnel visualization — Track the conversion path from widget view to action

See Analytics for details on tracked events.

API Routes

The Console communicates with the following internal API routes:

Public API

The embed script communicates with two public endpoints: