ChatGPT 
Gemini 
Perplexity 
Microsoft Copilot You already have GA4. It reports your traffic, events and conversions. So what’s Dáva Zmysel going to add?
The short answer is accuracy.
A fundamental difference with Dáva is where the source gets recorded. GA4 works out where a visitor came from once they’ve arrived at your site. Dáva records it at the click, before they get there.
Anything that goes wrong in between, like a missing tag or a lost referrer, can change what GA4 reports. It can’t change what Dáva has already recorded. Sounds like a technicality? Not once you use the report to decide where your budget goes.
Once this recorded source is connected to the visit outcome, you’re gaining some powerful (and reliable) insights.
How a missing label informs the wrong budget decision
Here’s a hypothetical. Two campaigns each spend $1,000. Every booking is recorded in the booking system. The only problem is that some bookings lose the source, telling which campaign they came from.
| Measure | Campaign A | Campaign B |
|---|---|---|
| Actual bookings | 100 | 80 |
| Bookings credited to the campaign | 50 | 72 |
| Bookings not credited to the campaign | 50 | 8 |
| Reported cost per booking | $20.00 | $13.89 |
| Actual cost per booking | $10.00 | $12.50 |
The report says B is cheaper. But, as you can see, B’s off by a long shot. Allocate budget based on these figures and you fund the weaker campaign, purely because A loses its source most of the time.
If both campaigns lost their source at the same rate, the costs would be wrong but the ranking would hold. Uneven losses are the dangerous kind, because they change the comparison itself. They are also hard to spot, because the report still looks complete.
A large Direct share is the biggest tell-tale sign. Find out which sources are affected and whether the gap is big enough to change a decision.
The solution: Record the source before the destination
GA4 identifies sources using the now unreliable method of campaign tags (UTMs), referrer information and ad platform integrations. Set up correctly, it should do ok in theory, but the catch is that the information has to survive the trip to your landing page.
This trip is becoming increasingly harder. A redirect strips the tags. A link goes out untagged. A visitor arrives with no usable referrer. If no usable source information remains, that traffic will likely get listed as Direct, alongside a handful of people who genuinely typed your address.
Dáva moves the recording process earlier. You create a tracking link with the campaign details and destination, then use it in your ad, email or other placement. When someone clicks, Dáva records the campaign, then sends them on their way to the destination page. By the time the page loads, the record already exists.
“Why not just fix my UTMs?”
Fair question. Clean UTMs are better than lazy labels, but a UTM lives in the URL, so anything between the click and the page can remove it. A Dáva link’s campaign details are set when you create the link and recorded on the click, so nothing downstream can strip them.
Naming discipline matters either way. A Dáva link still has to be labelled correctly and used in the right place. The difference is when the label is recorded, not how OCD it is.
Dáva allows you to rapidly create separate links for each campaign or placement you want to track uniquely. Reusing one link across unrelated sources will group their traffic together, meaning you can’t distinguish the sources later.
Beyond the source. Seeing what each campaign produced
A campaign total tells you how many clicks, not the activity that happened as a result. Dáva’s website snippet connects each visit’s pages and actions to the campaign that delivered the traffic. This provides you with clear cause-and-effect behind a result, so you can decide to scale it, change it or stop paying for it.
Take a hypothetical booking campaign: Someone clicks a Dáva link in a paid social ad, reads the offer, checks pricing page, then books through a supported integration. Dáva records the campaign on the click, then connects the visit’s events and the booking to it. If a redirect had stripped the tags on the way, GA4 might record the booking with no campaign attached. Dáva has already recorded the campaign. If the session and booking connect, the booking is credited to it.
Define success once
Results sit in three stages:
Cold: The initial visit
Hot: A visitor showing signs of genuine interest
Acquisition: A completed journey (e.g. booking, purchase, enquiry)
By applying these definitions to set pages & actions, every visit is clearly filtered accordingly, providing insight rich data.
Compare what each outcome costs
Add campaign spend to the calculator to compare the cost of each outcome. A source with plenty of visits (Cold leads) but few meaningful actions needs a different fix from one that builds strong intent (Hot leads), then loses people before they finish. The session data shows where people drop off, which informs you where to optimise: the audience, ad, landing page or booking process.
GA4 can answer similar questions. The difference is that Dáva is drawing from more reliable data, and puts campaign outcomes, and the sessions behind them, at the centre of the workflow rather than in one report among many.
Is there still a place for GA4?
Dáva’s focus is a single source of truth that provides accurate journey insights. But GA4 can still have a place in your arsenal for broad analysis and activation:
- Path and funnel exploration, cohorts and customer lifetime analysis.
- Connecting multiple sessions and devices through a User-ID.
- Raw event exports to BigQuery for custom analysis alongside other business data.
Most teams won’t have to choose. Dáva runs alongside GA4 without interference, so you keep the broad analysis and add a firmer record of where each campaign’s results came from.
What Dáva doesn’t do
It covers one session by default.
Dáva’s standard connected journey covers a single session, including supported booking and payment flows. Connecting a return visit on another device needs extra setup. GA4 can credit a later visit on the same device to the earlier campaign, so judge the fit by the outcome you measure, not the length of your sales cycle.
It only knows its own links.
Dáva can’t identify a source that didn’t use one of its tracking links. Installing the snippet alone will only provide site activity data, not where the traffic came from.
Website activity can still be blocked.
Nothing can be promised 100% of the time. So ad blockers and consent settings can limit what the snippet records after the click, even when the campaign source itself has been captured.
Setting it up
- Connect a subdomain you own.
- Install the website snippet.
- Swap the relevant destination URLs for Dáva tracking links.
- Set what counts as Hot and Acquired, and connect the integrations that report them.
- Test one complete journey, from click to outcome, before trusting the report.
As you can see, the set up is lean. The majority of your time will be spent creating links and updating existing campaigns. This is why we also offer setup support to get your team up and running, preferably on the same day.
Better reports start with better inputs
GA4’s broader features are valuable, but they’re only as good as the data that feeds them. Missing sources distort campaign comparisons. Missing activity distorts funnels and conversion rates. Missing identity weakens conclusions about returning customers.
Incomplete data can still be useful. An unknown source doesn’t erase a recorded purchase for example. The question is whether the gaps make the report misleading, especially when the gap ratio is not evenly distributed. A sophisticated report can still point you to the wrong budget decision, with confidence.
If that decision is the one you need to get right, book a 30 min demo session so we can show you just how simple tracking can be. Run Dáva alongside GA4 on the same campaigns, outcomes and period to see what you’ve been missing all this time.