Next steps after onboarding

Where to go from here

Onboarding installs the tracker and confirms datakant is receiving data. This guide covers the setup that turns that raw traffic into something you can report on and share — it takes about fifteen minutes and none of it needs a developer.

Work through the steps in order. Each one builds on the last, and you can always come back and refine.

1. Assign your consent signals so datakant knows what it is allowed to collect.
2. Import your most important elements by clicking through your live site.
3. Add events and flag conversions for the actions that matter.
4. Enable event forwarding to send events on to GA4 and Meta.
5. Add server-side tracking if you want to beat ad blockers and ITP.
6. Invite your team so colleagues can see the same dashboards.

1. Assign your consent signals

Open Data Settings from the sidebar (it sits under Configuration) — or go straight to /dashboard/settings. It opens on the Mode & Consent tab. Your collection mode is already set from onboarding — here you tie each tracking system to a consent signal from your cookie banner.

1. The page opens on the Mode & Consent tab by default. Step 1 (your collection mode) is already set from onboarding — go straight to Step 2.
2. Under Step 2 · Map signals, assign a signal to each tracking system (datakant, GA4, Meta) in the Mapped consent signal column. This is how you tell datakant which consent your CMP grants for analytics and marketing.
3. Click Save changes in the bar that slides up at the bottom. Each mapped row then shows an Active status.

2. Import your most important elements

You never have to write a CSS selector. The tracker watches real clicks on your site and builds a catalog of elements visitors interact with — buttons, links, and form submits. You pick from that visual list when you define an event.

To seed the catalog quickly, open your live website in a normal browser and click the things that matter, a few times each, across the pages where they appear:

1. With the snippet installed, open your live site in a normal browser tab (not a private or automated one — bot traffic is ignored).
2. Click your primary CTAs, signup and checkout buttons, form submit buttons, and key navigation links.
3. datakant records each click and adds the element to your catalog, with a confidence score and a screenshot preview.
4. The elements then appear under Data Settings → Events & Conversions → Add Event → Element click, ready for you to name in the next step.

3. Add your events and flag conversions

Go to Data Settings → Events & Conversions (/dashboard/settings?tab=events). The table lists every element datakant detected plus any events you define manually. An event is simply an action worth counting; a conversion is an event that matters to the business.

Add an event

1. Click Add Event at the top right. A three-step wizard opens.
2. On the first step, Trigger, pick how the event fires — Element click, URL match, or Scroll depth — then click Continue.
3. On the Configure step, set up the trigger: for Element click, pick your element from the catalog list (the screenshot preview confirms you have the right one); for URL match, enter the path and match type; for Scroll depth, pick 25, 50, 75, or 100 %. Click Continue.
4. On the final step, Finalize, review the Event name (lowercase snake_case, e.g. checkout_complete) and add an optional description.
5. Turn on Treat as a conversion if this action counts as a goal. The Default value and Currency fields light up — enter a value if the conversion has a monetary worth.
6. Click Save event. It now appears in the table.

Flag an existing event as a conversion

Already have the event in the list? Flip the toggle in the Conversion column of its row. It saves immediately, and the Conversions tile at the top of the tab increments.

4. Enable event forwarding

Forwarding relays your events on to GA4 and Meta so you can keep using those tools while datakant handles collection. You connect each destination separately under Data Settings → Destinations.

1. Open Data Settings → Destinations for the property.
2. On the Google Analytics 4 or Meta Pixel card, click Connect.
3. Enter the credentials for that destination (see the two cards below).
4. Map a consent signal — this is required. Forwarding only sends events for visitors who granted the matching consent, so datakant will not let you save without it.
5. Read the compliance notice, tick the box, and click Save changes to activate. The notice appears every time you switch a destination on — you remain the data controller for what GA4 or Meta receives.

Avoid duplicate events

The one thing that can go wrong is double-counting. If you already send data to GA4 or Meta directly from your site, that tag and datakant would both report the same events. Remove the old tag so datakant is the only sender.

5. Add server-side tracking (optional)

Server-side tracking is a paid, per-property add-on that routes your analytics through a subdomain of your own domain (a first-party CNAME to datakant's EU edge) instead of sending events straight to a third-party endpoint. Same events, same data — a more resilient route. The dedicated Server-side tracking guide has the full walkthrough.

Why enable it

How to enable it

1. Buy the Server-side tracking add-on for the property from your billing settings (some plans already include one).
2. Open Data Settings → Server-side tracking and copy the subdomain datakant suggests.
3. Add the DNS TXT and CNAME records shown at your DNS provider, then click Verify.
4. Once the domain verifies, replace your snippet with the first-party snippet and deploy. Swap the snippet last — keep the standard one until the CNAME resolves.

6. Invite your team

Open the user menu in the top-right corner and click Account settings — or go straight to /dashboard/account-settings directly. Only Owners and Admins can invite people.

1. In Account settings, open the Account users tab.
2. Click Invite User.
3. Enter the person's email, an optional full name, and choose an Account Role — Viewer, Manager, Admin, or Owner.
4. Click Add User. To give someone access to a single property instead of the whole account, use the Property users tab and Invite to property.

Roles at a glance

• Owner — the account creator; full access to everything, cannot be removed, and the only role that can grant billing access.
• Admin — full read and write access to every property, plus the ability to invite and manage users.
• Manager — full access, but only on the properties assigned to them.
• Viewer — read-only access on the properties assigned to them.