Development
Sonance
Product tools for a global audio brand
Shopify development with theme changes and product tools for an international store.
Visit sonance.comA web development course does not have to be about writing code. I teach marketing and product teams Google Tag Manager, speed and everything you can fix yourselves, backed by 16 years of developer experience and with your own site as the running example.

star reviews
Read every reviewMarketing and product teams tired of waiting on another department every time something needs measuring or fixing. No technical background is required; if you can find your way around a spreadsheet, you can follow along.
The courses also suit agency teams who want to be more self-sufficient in their clients' setups, and new employees getting to know an existing configuration.
Half days work best, and a series of three half days a couple of weeks apart usually beats one long day, because people get to use the material between sessions.
Each session ends with a real change on your own site, made together. That gives something concrete to hold on to when everyday work takes over again.
A web development course, in my version, is not a coding course. It is training in understanding and working with your own website: how measurements are set up in Google Tag Manager, why pages get slow, what you can change yourselves, and how to order the rest from a developer without misunderstandings.
The audience is the people who live with the site every day: marketing teams, product people and content owners. They do not need to build the site, but they do need to act in it, and that ability is exactly what the course trains.
I have worked as a web developer since 2010 with more than 400 projects behind me, so I teach things I do for clients every week. When a question goes deeper than the syllabus, you get an answer from practice instead of a pointer to the documentation.
A typical session lasts half a day. We start with the theory behind the day's topic, then work into your own setup with exercises, and finish by completing a real change together that stays in place after the course.
Most of a Google Tag Manager course is about three concepts. A tag is what gets sent, for example an event to GA4 or a conversion to Google Ads. A trigger decides when the tag should run: when a page is viewed, when a form is submitted, or when the website reports that a purchase is complete. A variable is a value the tag or trigger needs, such as the page address, the text on a button or the order amount. Understand those three and you can read most containers.
The next part is testing before anything goes live. In Preview mode, which opens Tag Assistant, you can click around the website and see which tags fired, which did not, and why. That habit is what separates a safe setup from one where measurements slowly disappear. We practise it on your own website until participants can find the fault themselves when a trigger does not respond.
Finally there is what keeps things tidy over time. Every time the container is published, Tag Manager saves a version, so you can see what changed and return to an earlier version if something goes wrong. Workspaces let several people work at the same time without overwriting each other, and folders and consistent naming make it easy to find your way around. Permissions can be split so that several people may edit but only a few may publish, and I recommend that split for most teams.
The aim of the course is for routine tasks to be handled in-house. After the Google Tag Manager session the team can add a new measurement on its own, for example a click on a button or a newsletter sign-up, send it to GA4 with a name that follows your fixed pattern, and test it in Preview before it is published. If something goes wrong, they can find the version that worked and return to it.
The team can also keep an eye on whether the measurements still work. After a design change or a new campaign page, a few minutes in Preview and a look at the realtime report in GA4 are enough to see whether the key events still come through. It is far cheaper to catch an error the same day than when the monthly report shows a gap in the numbers.
In the part on speed, participants learn to read PageSpeed Insights and the Core Web Vitals report in Search Console, so they can see whether a page is good, needs improvement or is poor, and what is dragging it down. Oversized images and tags nobody uses any more they can deal with themselves. The rest they can describe precisely enough for a developer to start without follow-up questions, and that ability often saves the most hours in the long run.
The courses are held where your team sits, whether that is in Copenhagen, Aarhus, Odense or Aalborg. I live in Glostrup west of Copenhagen and happily travel across the country when a group needs to gather in front of their own site.
For multi-session programmes the combination is often best: the first session in person at your office, the following ones over video. Google Tag Manager and the speed tools live in the browser anyway, so the online format costs very little in outcome.
The content is tailored regardless of postcode. Before the first session I have been through your site, your Tag Manager container and your speed numbers, so the examples come from your own reality from the first minute.
The most requested half day is about tracking, and rarely because anyone finds it exciting. It is because every new measurement requires another department to find time in the calendar, and nobody wants that conversation every other week.
The solution is an agreement about what the site sends off: page view, form, cart, purchase, search and filter, with fixed names and fixed fields that do not change at the next redesign. With that agreement in place, you can build on in Google Tag Manager without asking for anything new.
That agreement requires marketing and whoever looks after the site to talk, and in many places that conversation has never happened. So I usually suggest both sides join that particular session, because the problem gets solved fastest with everyone in the same room.
Concrete deliverables, not a report of recommendations someone else has to find time for.
I go through the site before the course, so we talk about your front page and your forms, not an invented company.
Each session ends with something that stays on the site, so you have seen the method work before you use it on your own.
Everything we covered, written down step by step, so colleagues who missed it can follow the same approach.
An overview of the changes you can safely make without help, and the ones that need a developer. It saves the most hours afterwards.
Development
Product tools for a global audio brand
Shopify development with theme changes and product tools for an international store.
Visit sonance.comWordPress
Menus, booking and gift cards in one place
A WordPress website for the restaurant with booking, menus and gift cards gathered in one place.
Visit sokkelund.dkShopify
Shopify across markets
Shopify development across markets with theme changes, tracking and ongoing improvements to the store.
Read about my work for OOONOVisit ooono.comWordPress
Design focused on conversion
A new WordPress website for private and business customers with design, tracking and a simpler booking flow.
Visit 3x34.dkWordPress
WordPress built to keep up
A custom theme with flexible templates for Dinero's product pages, pricing and guides.
Read about my work for DineroVisit dinero.dkShopify
A new AED brand on Shopify
A Shopify site with a custom theme and visual product story for Joule's new AED.
Visit jouleaed.comWordPress
From class schedule to booking
A WordPress website for the studios with class schedules, pricing and a clear route to booking.
Visit energii.dkNext.js
Courses for companies and job seekers
A Next.js course platform with course listings, registration and tracking for companies and job seekers.
Visit bigum.coWordPress
10 museums gathered in one website
A WordPress website bringing together museums, experiences and visitor information from across Ringkøbing Fjord.
Visit ringkobingfjordmuseer.dkFour steps. You know what happens when, and you can stop after any of them.
We go over who is attending, what they already know, and what they should be able to do afterwards. From that I propose topics and a programme for the day.
You send two or three tasks the participants genuinely spend time on. I build the exercises around those, so nobody has to translate examples from a foreign industry into their own.
The morning is walkthroughs with short exercises, the afternoon is independent work on your cases while I help at the screens. The pace gets adjusted to the group as we go.
After the day you get the slides, prompts and a document with the solutions that were built. A follow-up session a few weeks later can be added once the questions from daily use have surfaced.
It depends on the number of sessions, the size of the group and how much I need to study beforehand. After a short talk about your needs I send a concrete quote, and you hear from me the same day.
You learn to work with the three building blocks of Google Tag Manager (tags, triggers and variables) and to test in Preview before anything is published. On my course we practise it in your own container, so participants can afterwards add a measurement, find the fault when a trigger does not respond, and return to an earlier version on their own. We also cover folders, naming and permissions, so the container stays manageable.
Marketing and product teams, content owners and agency people who work with websites without being developers. The course is built for the people who use the site, not the ones who coded it.
Google Analytics is where you see the numbers, while Google Tag Manager is where you decide what gets measured and when it is sent. GA4 can be installed without Tag Manager, but then most new measurements require a change to the website's code. With Tag Manager you can add the measurements yourselves and send them to Analytics and other platforms from one place.
No. Everything is explained from scratch and practised in your own tools, and I pace the group rather than a fixed programme.
No, but it makes the course more concrete. If you have a container, I ask for read access beforehand, so the examples come from your own setup. If you do not have Tag Manager yet, we agree before the first session how the code gets onto the website, since that requires access to the site's code or CMS. We can then start the course by building the measurements from scratch.
Yes. I teach at companies in Copenhagen, Aarhus, Odense, Aalborg and everywhere in between, and being based in the capital area, online sessions are often the smoothest option for teams in Jutland and on Funen.
There is no fixed limit, but small groups give the best outcome, because the teaching relies on everyone getting help in their own setup. Larger groups we split across several sessions.
Yes, and I often recommend it. Three half days a couple of weeks apart gives people time to use the material, and the next session can then pick up whatever caused trouble.
Google Tag Manager and measurement, speed and Core Web Vitals, accessibility and working with developers. If you want something outside that list, just ask; if it sits outside my field, I will say so honestly.
Yes. If even one person in the room does not speak Danish, we switch to English, and that usually goes completely smoothly.
Your next step
Tell me about your project. I’ll get back to you with questions, options and a concrete next step.