pl en
Contact

For marketing agencies

The campaign is ready, but it stalls on the client's IT side.

You run Google Ads, GA4 and social campaigns, and your work ends right where the store's code begins. As your technical partner I step into that gap: you sell and manage the client relationship, I help get the project across the finish line on the technical side.

Scope

What I actually do on the store's side

Checking the implementation on the store's side

I check whether what was implemented actually works the way the campaign assumes: what the module collects, when consent gets updated, whether the cron job resends missing orders, and whether statuses are dropping transactions.

Data integrity

The store, the CRM and GA4 need to agree: sessions, consent state, duplicates, amounts. When data goes missing, I trace where it disappears: the code, the database, a cron job or an API.

Feed and Google Merchant Center

Where the store meets Merchant Center: the feed, price and stock updates, the module talking to the API. I analyze the problem and recommend a direction, while the agency keeps running the account.

Fixes the agency hands off

SEO and tracking fixes the agency has prepared, which have to go into the store: I implement them on the client's store and confirm what changed.

Boundaries

What I don't do

A specialist is defined as much by what they don't do. This is where my part ends and yours begins.

Ad accounts

I don't run ad accounts or Merchant Center. That stays with the agency.

GA4 audits

I don't sell them as a product. I change whatever the store needs to change after one.

Server-side GTM

I don't implement it myself. I check whether the agency's implementation is correct.

The client's IT department

I don't replace it or the module vendor. I work alongside both and talk to them directly.

Evidence, not claims

Four cases from 2026

I work with the online-partners agency on several of its clients' projects in 2026. I don't name the end clients; I describe the problem and my part of the work, with numbers where they're documented. All 18 cases, including work done directly for stores, are in the case studies.

agency's client February-March 2026

Are orders reaching GA4 in full? Checking the store side of tracking

Situation

The agency had implemented tracking through GTM and a store module. It needed an answer: was order data reaching GA4 in full, and what exactly did the module collect.

What I did

I analyzed the module, the database, a cron job and order statuses for places where data could go missing. I checked what the module collected, including the identifiers linking an event to a user. I verified purchase events resent by the cron job against GA4's reports, since this module had no way to enable debug mode. I tested the flow on production orders, then checked that the cron job was actually set up.

report

listing the places where data could go missing

5

possible causes mapped for checking on production data

agency's client March-May 2026

Transactions without a session, and data that stopped being recorded

Problem

Without consent, a transaction reached GA4 as (not set), with no session and no user. One test transaction was marked as sent in the database but wasn't in GA4 at all. Consent updates fired too late and in the wrong order. After a GTM configuration change, data stopped being recorded in GA4, even though real-time traffic was visible.

What I did

I tested orders with and without consent, checked the order in which module hooks fired, and reviewed the tag, consent and filter configuration in GA4. I identified the errors in GTM, and once the correct version was activated, data was recorded again. I also recommended a cron resending missing orders every 10 minutes.

recording again

GA4 data after the GTM errors I identified were fixed

10 min

recommended interval for a cron job resending missing orders

agency's client June 2026

The store, the CRM and GA4 each showed a different set of orders

Problem

The order count and amounts in GA4 didn't match the store. The agency was making decisions on data it couldn't verify.

What I did

I compared orders from the store's database with GA4 and with what the CRM reported. I found the first bug on the CRM's side, listed the missing orders, and described five patterns in how amounts were calculated. Only one was correct. The others missed a discount, double-counted, or used gross instead of net. The amount discrepancy was fixed.

129 of 130

orders reached GA4 in the first period checked (99%); 285 of 293 (97%) over the wider period

108 of 130

orders the CRM passed on from the same period - the 22 missing orders were the first bug I found

agency's client March-April 2026

Prices and stock in Merchant Center refreshed once a day

Problem

The server updated the feed file every 3 hours, but Merchant Center only pulled it once every 24 hours. The store ran on a SaaS platform that exposed a single file and had no Merchant API.

What I did

I analyzed four options, from the Merchant API to supplemental files, and tested reading product data through the API on the client's own account. I proposed a split of work: what the client's web developer needed to build, and what the marketing team needed to hand over. This was analysis and a recommendation - building the mechanism was another contractor's job.

4

data-refresh options analyzed for Merchant Center

24 h

interval between Merchant Center's feed pulls in the existing setup

How it works

How we work together under your brand

Work modes, how I price a job, and what I do when the budget doesn't stretch are covered in How I work.

01

Free call

You describe the project and where the implementation is stuck. We check whether there's a fit, no obligation and no cost.

02

Under your brand

By default I work under your brand: to the client I'm part of your team, not a separate subcontractor. The agency I work with gave me an address on its own domain and introduces me to its clients as its own senior developer. If you'd rather I work under my own name, we set that up at the start.

03

Scope and a cap on hours

Hourly billing with an approximate cap, no detailed quote. I don't estimate an outage in advance: what matters there is reaction time, not a price.

04

Work and a report

Every piece of analysis ends with a report: what I checked, what I found, what's left to decide. I come back with a decision to make, not a question.

05

Reaction time

I react to an outage within 4 hours, Monday to Friday, 9:00-18:00 CET/CEST. For long-term clients it can be faster, sometimes within the hour. If you need it urgently, the surcharge is stated plainly before I start.

Next step

Tell me where the implementation is stuck

Tell me which project you're running and what isn't working on the store's side. We start with a free call, no obligation.

Describe your problem