Get Started
Add Pulse to your website in under five minutes.
1. Create your account
Go to pulse.ciphera.net and sign in with your Ciphera ID. If you don't have one, you'll be prompted to create an account during sign-up.
2. Complete the welcome flow
After signing in for the first time, Pulse walks you through a short setup:
- Enter your organisation name.
- Click Add Site to register your first property.
3. Register your site
Enter a site name (for display in the dashboard) and your domain — for example, example.com. Do not include https:// or a trailing slash.
4. Copy the tracking script
Once the site is saved, Pulse shows you the snippet to install:
<script defer data-domain="example.com" src="https://js.ciphera.net/script.js"></script>Replace example.com with your actual domain.
5. Paste the snippet into your site
Place the snippet inside the <head> element of every page you want to track — ideally in a shared layout or template file. The defer attribute ensures the script never blocks page rendering.
6. Verify the installation
Click Open Website & Verify in the Pulse dashboard. This opens your site with a ?utm_source=ciphera_verify query parameter and starts a 60-second polling window. When Pulse receives the first event from your domain, the dashboard confirms the installation.
The verification visit itself is counted as a pageview. You can filter it out later using the campaign filter (utm_source = ciphera_verify) if you want clean baseline data.
7. Start seeing data
Once verified, data begins appearing in the real-time dashboard immediately. Historic data populates as visitors arrive — there is no back-fill from before the script was installed.
Troubleshooting
If verification does not succeed within 60 seconds, check the following:
Ad blocker active in your browser. The verification request is made by your browser. Disable your ad blocker for the test, or use a browser profile without one.
Wrong domain. The domain in data-domain must exactly match the domain registered in Pulse, without www. unless you specifically registered it with www..
Script not in <head>. Some page builders inject scripts into <body>. Pulse works from <body> too, but make sure the script tag is present on the page before verifying.
Testing on localhost. Pulse ignores localhost and 127.0.0.1 by default. Deploy to a staging URL or a real domain to verify.
If you are using a Content Security Policy, make sure pulse.ciphera.net and pulse-api.ciphera.net are included in your script-src and connect-src directives respectively.