Getting started

This guide starts from a running instance — yours, or the development stack from installation. In ten minutes: a declared site, the tag pasted, “Received ✓”.

1. Create the site

In Sites, an administrator clicks New site and enters:

• a name (“Maison Arvor”);
• its domain (maison-arvor.fr).

The site receives a public key of the form s_xxxxxxxxxxxx and opens on its Installation tab. Only declared domains can send data: add your testing or staging domains in the site’s Settings (*.maison-arvor.fr covers all subdomains).

By default, the site measures cookieless. The mode can be changed at any time in its Settings, without touching the tag: see tracking modes.

2. Paste the tag

The Installation tab gives the site’s tag, with its key and the collection address already filled in. Paste it into the <head> of every page:

<script defer src="https://stats.example.com/a.js" data-site="s_arvordemo001"></script>

That’s all: page views, sources, campaigns, engagement time, scroll depth, clicks and automatic measurements are sent on their own. A tag manager (Google Tag Manager, for example) works too, with a custom HTML tag.

Without installing anything

In development, the test page http://localhost:4600/demo already carries the demo site’s tag: open it, click around, then move on to the next step.

3. See “Received ✓”

Open a page of the site, then the site’s Verification tab in eodia analytics. It waits at first: “Waiting for the first event…”. As soon as the page view arrives, it shows “Received ✓”, then:

• the check figures: events received in the last 24 hours, rejections by reason, visits classified as Unassigned and their source / medium pairs;
• the latest events, received and rejected, refreshed every two seconds, with the reason for each rejection.

Rejection reason	What it means
Origin not allowed	the page is not on one of the site’s declared domains
Bot	a bot user agent, a headless browser, or no user agent at all
Excluded path, Excluded IP address	the exclusions in the site’s Settings (/admin/*, the office network)
Rate exceeded	more than 120 events per minute for the same visitor
Invalid payload	an event name or properties outside the limits
Identity refused	a signed-in visitor on a site that does not accept them, or an invalid token

The collection endpoint responds 202 to everything that is well formed, rejections included: it does not reveal which sites exist. The Verification tab is what tells you why an event was discarded.

Nothing arrives?

Check, in this order: the browser console (a security policy blocking the script), an ad blocker (try a private window, or serve the script from a subdomain of the site), the browser’s Global Privacy Control signal, which counts as a refusal, and the site’s declared domain.

4. Declare what you measure

The Metadata tab describes events and zones: a label, a description, typed properties. Events received but not declared are listed there, with their observed properties: Declare prefills the form. These descriptions become SQL comments, which eodia insights reads. See the views.

5. Read the data

Connect eodia insights to the database: the PostgreSQL source, then the Statistics button, which opens insights dashboards locked to the site.

What next?

• The tag and its attributes, then the page API for your own events.
• E-commerce, if the site sells.
• The CNIL (the French data protection authority): the information notice to reuse and the opt-out link.