Under Connections you find Measuring (/w/<workspace>/connections?tab=meten). It is one place for three things every site needs: being found in Google (Search Console), seeing what visitors do (Google Analytics) and seeing how they behave (Clarity). It works per brand, and everything is on by default. What is still missing and what to do now is shown at the top.
The status
At the top the three parts sit side by side, with the next step below. A part is only ready once the data is there and the tag has been seen on the site. A tag we could not check does not count as ready.
Connecting Google
You choose what you connect to Google: Search Console, Analytics, or both (both by default). You see Google's own screen; Denkploeg never sees a password.
- Search Console asks for the right to submit sitemaps and have pages inspected. Google has no separate permission for that, so the right is called webmasters. We never delete a property or a user.
- Analytics asks for the right to create a property and a web data stream, and to read the figures. We only clean up what we created ourselves.
A part you untick does not appear on Google's consent screen. You can always revoke access in your Google account, under Security.
Search Console
Fetch your properties, link the site's property to the brand, and submit the sitemap. You can also have a page inspected: Google then shows whether it is indexed. A daily quota of 2000 inspections per property applies; the screen keeps count.
Google Analytics
Pick an account and have a GA4 property with a web data stream created, or pick an existing property. The measurement ID (G-...) is stored with the brand. We cannot create a new Analytics account for you: Google asks for agreement to its terms itself. Create one at analytics.google.com and come back.
Clarity
Clarity has no API to create a project. Create a project at clarity.microsoft.com and paste the project ID here. The whole project address or the snippet Clarity gives you works too.
The tags on the site
For a site Denkploeg will host itself later the tags will arrive automatically. For an existing site (WordPress, Shopify, Magento, Wix, Squarespace, Webflow or something else) there is a snippet with instructions for the platform we detected. By default the tags only load after a visitor has given consent: your cookie notice calls dpMetenLaden(). With Check the site we look whether the tags are there.
Google Tag Manager
If you use Google Tag Manager your tags live there and you do not need to put the snippet below on the site. When you connect Google, also tick Google Tag Manager; we then only ask for the permission to read. Next you pick an account and a container, or type the container ID (GTM-...). We read what is live in it and tell you per part what we see: "GA4 is in your container" or "GA4 is missing", the same for Clarity, and whether the measurement ID or the Clarity project equals the one stored for the brand. If the tag is paused or has no trigger we say it does not fire. If the container was never published there is nothing live to read.
We never change or publish anything in your container. Read again looks again after you have published in Tag Manager; Unlink removes the container from this brand (nothing changes in Tag Manager). If your permission has expired or you did not tick Tag Manager, the screen says which step is missing and has a button to connect Google. When a container is linked, the Tags on the site block says you put the tags in Tag Manager and can skip the snippet.
Undoing
Every call to Google is in the log at the bottom. A sitemap you submitted can be removed again, and an Analytics property Denkploeg created goes to Analytics' trash (recoverable for 35 days). Whatever was there before Denkploeg did anything stays.
After connecting Google, we immediately fetch Analytics properties and Search Console sites and schedule a Marketing import. Analytics shows the property name; Expert shows its technical id. A temporary fetch failure keeps the connection intact so you can try again.
Adding site ownership
Under Search Console you can verify the saved site address of the selected workspace brand. Connect Google Site Verification using the same Google account as Search Console. Choose DNS-TXT for the domain or a meta tag for the homepage head. Install the public verification proof yourself. Denkploeg does not automatically change DNS or site code.
Choose I have installed the proof. Prepare proposal, then confirm under To sign with the extra code. Google checks the proof, adds the site and confirms ownership. Only then does Denkploeg save the property for this brand. A changed site, revoked consent or proof older than 24 hours requires a new proposal. If adding fails after verification succeeds, Google may already have recorded ownership; check the result and retry. Removing a local connection does not remove existing site ownership at Google.
Tag Manager permissions
Reading Tag Manager only uses tagmanager.readonly. There is no permission to change or publish a container. The permission is not part of the default choice: you only see it on Google's screen if you tick Google Tag Manager yourself.
Analytics permissions and measurement ID
Reading metrics uses analytics.readonly. Preparing a GA4 property or web data stream uses analytics.edit. Without the required permission Denkploeg sends no API request. Select an existing property, or create a property and data stream inside an existing Analytics account. Create an account at Google yourself because its terms require acceptance. A service account can read metrics but receives no write access through this flow.
The measurement ID is stored for the selected brand. It does not prove that the tag is installed, visitors have consented or data is arriving. Install and check the tag using the existing setup steps. Imports read sessions, key events and revenue per day/source/medium/campaign. Recent days are repeated because Google can revise their metrics.