Running ten sites, a few plain HTML sales pages and a members area on a script that is not WordPress? Pulse watches all of them from one place. The rule is simple: every domain gets its own row under Connections, Your Sites, and its own line of code. That gives each site its own name and colour on the globe, and it is also your security: your site IDs only work from the domains on that list.
Every domain gets its own row:
On your main site, open 🔌 Connections, Your Sites. Type the site's name and domain and press + Add Site, then Get The Code on its row. See More Than One Site: The Hub and Pairing Codes for the whole card.
Another WordPress site:
Best: install Pulse there and paste the pairing code (Option B). It needs no licence key, and logged-in members are recognised by themselves. Quick alternative: paste that site's one line (Option A) in the theme footer.
A plain HTML page:
Paste that site's one line before </body>. That is all. It works when you open the file from your own computer too.
A PHP site or script:
Paste the same line into the footer file every page includes (often footer.php), once.
A membership site:
Put the line in the members template as well as the public one. Pages behind a login count exactly like public ones, because the line runs in the member's own browser.
A sub-domain:
members.yoursite.com is covered when yoursite.com is on your list. Give it its own row only if you want it in its own colour.
Pages on your main site that WordPress does not serve:
Your main site tracks itself already, with nothing to paste. For an extra HTML or PHP page on the same domain, use the line under Get The Code on the HUB row, or the 1. Tracker line under ⚙️ Settings, 🧩 Put Pulse On Your Pages. That card also shows your Public site ID and the Endpoint, the 2. Globe embed, the 3. WordPress shortcode, and 4. Shortcodes for pages, posts and sidebars, each with Copy.
Showing who a logged-in member is (sites that are not WordPress):
On a WordPress site Pulse does this by itself. Anywhere else, your member area already knows who is logged in, so tell Pulse with one line after the tracker:
<script>window.addEventListener('load',function(){ RAVG.identify('member@example.com','Maria'); });</script>
Print the member's real email and first name there from your membership script. The email is turned into a one-way fingerprint inside their browser and only the fingerprint is sent. If your plugins know that person, they show in your Live View by name with their lifetime value.
Any opt-in form on a tracked page does the same thing by itself the moment somebody submits it.
A domain you have not listed yet:
Your site IDs only work from your own domains, so a copied ID is worth nothing on somebody else's website. When a domain that is not on your list tries, the Dashboard and the Connections tab show 🔒 Visits From A Domain That Is Not On Your List, with each domain and two buttons:
- This Is Mine, Add It: one click and that domain counts from then on.
- Not Mine: the note goes away.
Diagnostics, Your Sites shows Turned away (not one of your domains) too.
Allowed origins:
Sites on Your Sites are allowed automatically. For anything unusual, Settings, Data & Access has Allowed origins (CORS): a comma-separated list of origins allowed to read the feed.
A real example:
Yoursite has a WordPress main site, a WordPress shop, a members area on WordPress and three HTML sales pages on offers.yoursite.com. The shop and members site get pairing codes. The sales pages share one footer file, so the owner pastes the Offer Pages line there once. A week later the owner tries a new landing page on a second domain, forgets to list it, and the Dashboard shows the domain under Visits From A Domain That Is Not On Your List. One click on This Is Mine, Add It and it counts.
Tips:
- Keep one row per domain, so each site has its own colour, its own line in Your Sites, Side By Side and its own filter in Stats.
- Diagnostics, Live Tests checks that the tracker file downloads and Pulse answers from the outside.