# Narrativva full LLM export Source: https://narrativva.com/ Markdown: https://narrativva.com/index.md # We fix analytics and websites for teams that spend on ads. Companies spend thousands on campaigns, but decisions are still based on unclear tracking and conflicting reports. We fix analytics first, then align the website, reporting, and systems around reliable data. Trusted by Thermo Fisher Scientific (S&P 500). ## Primary actions - [Start a conversation](https://narrativva.com/contact) - [See services](https://narrativva.com/services) - [Markdown source](https://narrativva.com/index.md) ## Web analytics first. Then the rest of the system. We start with analytics and tracking for teams that spend on ads. Then we improve websites, web applications, and automation where the wider system is blocking performance. ### Web Analytics GA4, GTM, cookie banner setup, Consent Mode v2, server-side tracking, CAPI, dashboards, RFM analysis, and measurement planning built to improve attribution, reporting, and campaign decisions. - [Service page](https://narrativva.com/services/web-analytics) - [Markdown source](https://narrativva.com/services/web-analytics.md) ### Website Development Strategy-led, custom-built websites with fast performance, solid SEO foundations, and a structure people can actually navigate. - [Service page](https://narrativva.com/services/website-development) - [Markdown source](https://narrativva.com/services/website-development.md) ### Web Application Development From client portals to internal systems, we build focused web applications with clean architecture and a clear operational purpose. - [Service page](https://narrativva.com/services/web-application-development) - [Markdown source](https://narrativva.com/services/web-application-development.md) ### Automation / AI Systems Workflow automation, reporting pipelines, internal tools, and practical AI systems designed around real operational constraints. - [Service page](https://narrativva.com/services/automation-ai-systems) - [Markdown source](https://narrativva.com/services/automation-ai-systems.md) ## Signs your data is broken If these sound familiar, the issue is usually not media buying, but measurement quality. This is exactly where we start. - Ad platform numbers and GA4 numbers do not match. - Conversion tracking is inconsistent across channels. - Reports contradict each other and nobody trusts the dashboard. - Campaign spend is rising, but decision confidence is dropping. - Tagging and events were added over time and the setup is hard to maintain. ## Case studies are coming soon. The work section stays in place, but the public case studies are still being prepared. If you want relevant examples now, ask and we can share them directly in conversation. Detailed case studies are on the way. Until then, reach out and we can share the most relevant examples directly. [Work page](https://narrativva.com/work) ## First we find the actual problem. Before anything gets designed or built, we need to understand what is not working today. That might be the analytics, the website, the ad reporting, or the workflow behind it. The process usually starts with a few practical questions: what data is missing, where are people getting lost, what is still manual, and what is costing time or money every week. 1. Review the current state: We start by looking at the analytics, the site, the ad data, and the workflow around them. The point is to understand how things work today before suggesting anything new. 2. Find what is breaking: Then we identify the real bottlenecks: weak structure, broken analytics, wasted ad spend, manual work, or unclear logic between systems. 3. Define the right scope: Once the problem is clear, we decide what actually needs to be done. Sometimes it is better analytics. Sometimes a new website. Sometimes a dashboard, automation, or a small internal tool. 4. Build it properly: Then we design, build, connect, and implement. The work has to hold up technically, not just look good in a presentation. 5. Test and hand over: Before handoff, we check speed, forms, events, reporting, and real usability. The team should be able to run the result without depending on us for every small update. ## What clients say Feedback from clients who hired Narrativva for analytics, websites, and technical delivery. ### MUDr. Petr Krejcirik Eye doctor, Czechia. Scope: Website redesign, structure, and technical trust layer. > The service provided to me by Mr. Bujnovsky was performed professionally and within the agreed time frame. The communication was factual and efficient. I was very pleased with the proactive and innovative approach. ### Muhammad Motala SEO expert, Saudi Arabia. Scope: New website delivery with clear conversion structure. > I cannot be more impressed. He delivered on time and exactly what I needed. I cannot recommend him enough. If you are after a new website, go for FERO. You will not be disappointed. ### Benjamin Chan Copywriter, Dubai. Scope: New website build. > I loved working with FERO. He was kind, polite, and made the whole process seamless and easy. He knows his stuff. I got a fantastic-looking website and the whole process was genuinely enjoyable. ### Martin Pšenica Marketer. Scope: GA4, GTM, Meta CAPI, Google Ads and Sklik tracking across multiple clients. > Excellent collaboration and outstanding work on analytics and GTM. Communication was fast, delivery quality met all expectations, and the pricing was exactly as agreed. I am very satisfied and would highly recommend. ## Two brothers building analytics-led websites, apps, and digital systems. Narrativva is run by Frantisek Bujnovsky and Antonin Bujnovsky. Together they connect analytics, websites, applications, and technical delivery so the whole setup is clearer, more reliable, and easier to run. - Frantisek focuses on analytics, websites, and reporting. He helps clients see what is missing in the data, what is happening on the site, and what should be fixed first. - Antonin builds applications, works with databases, and turns messy ideas or manual processes into software that people can actually use. - The studio also works with larger teams. In Brno, Narrativva delivered practical AI workshops for Thermo Fisher Scientific warehouse teams. ### Enterprise-facing credibility Our technical standards are vetted by global leaders. For Thermo Fisher Scientific in Brno, we delivered hands-on AI workshops and bring the same rigour to every build. [About Narrativva](https://narrativva.com/about) ## The name points to two simple ideas: visibility and value. Narrativva comes from the word narrative. Story matters because it carries identity, memory, and meaning. The double V adds the other side of the idea: the story should be visible and it should create real value. - Visibility: People need to be able to find the business in search, ads, referrals, and the moments when they are already looking for help. - Value: Being seen is not enough on its own. The data, website, or system also has to help the business work better and make the next step easier. That is what the studio tries to connect: clear message, better visibility, and work that is actually useful. ## Notes from the studio Short practical articles about analytics, websites, access sharing, and the tools around them. ### How to know the problem is not in campaigns, but in measurement Before you rebuild campaigns, check whether the drop is really caused by media performance or by broken tracking, attribution, forms, consent, or reporting logic. Published: 2026-06-02 - [Article](https://narrativva.com/blog/how-to-know-problem-is-not-campaigns-but-measurement) - [Markdown source](https://narrativva.com/blog/how-to-know-problem-is-not-campaigns-but-measurement.md) ### Why Google Ads, GA4, and CRM numbers do not match A practical explanation of why campaign, analytics, and sales numbers disagree, what differences are normal, and what to check before you blame the campaigns. Published: 2026-05-11 - [Article](https://narrativva.com/blog/why-google-ads-ga4-and-crm-numbers-do-not-match) - [Markdown source](https://narrativva.com/blog/why-google-ads-ga4-and-crm-numbers-do-not-match.md) ### How to share Microsoft Ads access (Updated 2026) How to invite a user to Microsoft Advertising without sharing the main login, and when account linking is cleaner than adding a user. Published: 2026-03-19 - [Article](https://narrativva.com/blog/how-to-share-microsoft-ads-access) - [Markdown source](https://narrativva.com/blog/how-to-share-microsoft-ads-access.md) ## Start with a tool or guide. If the problem is still unclear, these are the two quickest starting points on the site. ### Free Tracking Checker Run a quick public-page check for visible tracking, consent, and analytics signals. - [Open page](https://narrativva.com/tracking-checker) - [Markdown source](https://narrativva.com/tracking-checker.md) ### Sharing Access Open the full hub for sharing access across GA4, GTM, Meta, Search Console, Microsoft Ads, and Clarity. - [Open page](https://narrativva.com/access-guides) - [Markdown source](https://narrativva.com/access-guides.md) ## A few common questions If you are figuring out whether Narrativva is the right fit, these are usually the first things people ask. ### Do you only build websites? No. Analytics is often the first part of the work, and we also handle websites, reporting, automations, internal tools, and selected web apps. ### Can you fix analytics on an existing website? Yes. Not every project needs a full rebuild. In many cases, the main problem is weak analytics, broken attribution, or poor reporting rather than the site itself. ### Do you work only with small businesses? No. We work with founders and smaller teams, but we have also delivered work in larger environments, including AI workshops for Thermo Fisher Scientific in Brno. ### Can you help even if we already have developers or an agency? Yes. Sometimes the right role is not replacing the whole team, but fixing analytics, clarifying structure, reviewing the current setup, or building one missing part properly. ### What is usually the first step? Usually a short conversation about what is not working right now. From there we can tell whether it makes more sense to rebuild, fix, connect, measure, or simplify. ## Losing money on campaigns because your tracking is unreliable? Send a short message. We will tell you what to fix first. [Start a conversation](https://narrativva.com/contact) --- Source: https://narrativva.com/about Markdown: https://narrativva.com/about.md # About Narrativva Meet the two brothers behind Narrativva, a studio focused on analytics, websites, applications, and digital operations. --- Source: https://narrativva.com/services Markdown: https://narrativva.com/services.md # Web Analytics, Tracking, Websites, Automation We start with analytics and tracking for teams that spend on ads. Then we improve websites, web applications, and automation where the wider system is blocking performance. ## Related Markdown - https://narrativva.com/services/web-analytics.md - https://narrativva.com/services/website-development.md - https://narrativva.com/services/web-application-development.md - https://narrativva.com/services/automation-ai-systems.md --- Source: https://narrativva.com/services/web-analytics Markdown: https://narrativva.com/services/web-analytics.md # Web Analytics GA4, GTM, cookie banner setup, Consent Mode v2, server-side tracking, CAPI, dashboards, RFM analysis, and measurement planning built to improve attribution, reporting, and campaign decisions. Most analytics problems are not caused by missing tools. They come from weak event models, inconsistent implementation, and reporting that nobody fully trusts. The result is simple: teams spend money on ads without being sure what is actually working. ## Who it is for - Brands with broken tracking or unclear attribution - Teams that need a cookie banner, Google Consent Mode v2, and tag firing rules configured correctly - E-commerce teams that need better conversion visibility - Founders who need dashboards they can actually trust ## Common problems - Events fire inconsistently and reports do not match reality. - Marketing channels and ad spend cannot be evaluated with confidence. - The cookie banner, cookie categories, and tag rules do not match what the site actually loads. - The team sees dashboards, but not decision-grade measurement. ## Deliverables - Measurement planning tied to business goals - GA4, GTM, consent, pixels, CAPI, and server-side tracking implementation - Custom server-side event flows for Meta CAPI, GA4, or other conversion APIs - Cookie banner configuration, cookie categories such as necessary, analytics, and marketing, Google Consent Mode v2, and GTM consent checks - Dashboard design in Looker Studio or custom reporting - RFM analysis and customer segmentation for e-commerce or CRM data - Validation, QA, and change logs ## Outcomes - Cleaner attribution and clearer reporting across channels - Tracking that respects the user's cookie choices and still keeps measurement useful - Faster diagnosis when campaign performance changes - Clearer customer segments based on recency, frequency, and monetary value - More confidence in campaign decisions and less wasted ad spend --- Source: https://narrativva.com/services/website-development Markdown: https://narrativva.com/services/website-development.md # Website Development Strategy-led, custom-built websites with fast performance, solid SEO foundations, and a structure people can actually navigate. A website should explain the business, make the next step obvious, and hold up technically. We build websites that are easier to trust, easier to find, and easier to run. ## Who it is for - Founders replacing outdated or slow websites - Service businesses that need more trust and clearer positioning - Brands that want performance without looking generic ## Common problems - The site looks acceptable, but it does not convert or rank. - Messaging is fragmented and the structure hides what matters. - Performance, accessibility, and measurement were treated as afterthoughts. ## Deliverables - Positioning-aware site architecture and page planning - Custom design system and editorial interface design - Implementation matched to the project, with strong technical SEO - Analytics-ready events, forms, and conversion tracking ## Outcomes - A website that explains the business with precision - A stronger trust signal for high-intent buyers - A platform that supports content, campaigns, and future growth --- Source: https://narrativva.com/services/web-application-development Markdown: https://narrativva.com/services/web-application-development.md # Web Application Development From client portals to internal systems, we build focused web applications with clean architecture and a clear operational purpose. When teams outgrow spreadsheets, inbox threads, and patchwork tools, the answer is usually not more software. It is a better-fit system. ## Who it is for - Teams running fragile manual processes - Companies that need client-facing portals or dashboards - Founders validating a focused software product ## Common problems - Too much work depends on manual copying, chasing, and checking. - Important information lives across multiple disconnected systems. - The business needs software, but not enterprise bloat. ## Deliverables - Product architecture and workflow mapping - UI design for dashboards, portals, and complex interfaces - Frontend and backend implementation - Database design and deployment guidance ## Outcomes - Less operational friction - Clearer access to the right information - A system shaped around the actual workflow --- Source: https://narrativva.com/services/automation-ai-systems Markdown: https://narrativva.com/services/automation-ai-systems.md # Automation / AI Systems Workflow automation, reporting pipelines, internal tools, and practical AI systems designed around real operational constraints. Automation is useful when it reduces time, friction, or error without making the process harder to understand. That is the standard we work to. ## Who it is for - Businesses wasting time on repetitive reporting or admin - Teams that want AI assistance grounded in real workflows - Operators who need systems to talk to each other ## Common problems - Reporting and operational tasks still depend on manual assembly. - Data exists, but the workflow around it is slow and unreliable. - The team wants AI leverage without vague promises or unsafe implementation. ## Deliverables - Workflow analysis and automation design - Reporting pipelines and alerting systems - Internal assistants and AI-enabled tools - Governance around prompts, data access, and reliability ## Outcomes - Less repetitive work and cleaner handoffs - Faster access to the right operational signals - Automation that stays understandable and maintainable --- Source: https://narrativva.com/work Markdown: https://narrativva.com/work.md # Work The work section stays in place, but the public case studies are still being prepared. If you want relevant examples now, ask and we can share them directly in conversation. ## Related Markdown - https://narrativva.com/work/noir-shisha-bar.md - https://narrativva.com/work/live-looker-studio-reporting.md - https://narrativva.com/work/petr-krejcirik-eye-doctor.md - https://narrativva.com/work/uptime-monitor.md --- Source: https://narrativva.com/work/noir-shisha-bar Markdown: https://narrativva.com/work/noir-shisha-bar.md # A venue website shaped around atmosphere, clarity, and trust. A premium hospitality website designed to reflect the physical experience of the venue while making key actions easy. Client: Noir Shisha Bar Year: 2025 ## Challenge The digital presence needed to feel more intentional, more memorable, and more aligned with the venue’s identity. ## Approach Narrativva focused on rhythm, contrast, and content hierarchy to create a site that feels immersive without becoming visually noisy. ## Outcomes - Stronger alignment between brand atmosphere and digital presentation - Cleaner path to reservation and contact actions - A foundation ready for future campaigns and events ## Stack - Next.js - Tailwind CSS - Motion - SEO --- Source: https://narrativva.com/work/live-looker-studio-reporting Markdown: https://narrativva.com/work/live-looker-studio-reporting.md # Reporting infrastructure built to replace manual status chasing. A reporting system that brings campaign and performance data into one readable operational layer. Client: Live Looker Studio Reporting Year: 2024 ## Challenge The existing reporting workflow was slow, fragmented, and difficult to trust during live decision-making. ## Approach Narrativva connected data sources, clarified reporting logic, and reduced the gap between collection and executive visibility. ## Outcomes - A live reporting layer designed for operational use - Less manual assembly and fewer reporting delays - Clearer visibility into performance trends ## Stack - Looker Studio - GA4 - GTM - Automation --- Source: https://narrativva.com/work/petr-krejcirik-eye-doctor Markdown: https://narrativva.com/work/petr-krejcirik-eye-doctor.md # A medical website focused on trust, accessibility, and service clarity. A service website designed to communicate expertise calmly and make key information easy to find. Client: MUDr. Petr Krejčířík – Eye Doctor Year: 2024 ## Challenge Medical websites often become dense, dated, and difficult to navigate for patients who need certainty quickly. ## Approach Narrativva used restrained design, precise copy structure, and accessible layouts to support trust and readability. ## Outcomes - A more credible digital first impression - Clearer explanation of treatments and practice details - A calmer and more usable patient experience ## Stack - Next.js - Accessibility - SEO - Content Architecture --- Source: https://narrativva.com/work/uptime-monitor Markdown: https://narrativva.com/work/uptime-monitor.md # A focused monitoring product designed around signal, not dashboard clutter. A monitoring interface that makes service availability visible, actionable, and easy to review. Client: Uptime Monitor Year: 2025 ## Challenge Monitoring tools often show plenty of data while still making real issues harder to spot quickly. ## Approach Narrativva focused the product around status visibility, alert hierarchy, and a cleaner operational reading flow. ## Outcomes - Clearer signal for operators - A more legible status and incident experience - A foundation ready for further product expansion ## Stack - React - Node - Database Design - Monitoring UX --- Source: https://narrativva.com/blog Markdown: https://narrativva.com/blog.md # Blog Short practical articles about analytics, websites, access sharing, and the tools around them. ## Related Markdown - https://narrativva.com/blog/how-to-know-problem-is-not-campaigns-but-measurement.md - https://narrativva.com/blog/why-google-ads-ga4-and-crm-numbers-do-not-match.md - https://narrativva.com/blog/how-to-share-microsoft-ads-access.md - https://narrativva.com/blog/how-to-share-google-ads-and-ga4-access.md - https://narrativva.com/blog/how-to-share-meta-business-manager-access.md - https://narrativva.com/blog/how-to-share-microsoft-clarity-access.md - https://narrativva.com/blog/how-to-share-google-tag-manager-access.md - https://narrativva.com/blog/how-to-share-google-search-console-access.md --- Source: https://narrativva.com/blog/how-to-know-problem-is-not-campaigns-but-measurement Markdown: https://narrativva.com/blog/how-to-know-problem-is-not-campaigns-but-measurement.md # How to know the problem is not in campaigns, but in measurement Before you rebuild campaigns, check whether the drop is really caused by media performance or by broken tracking, attribution, forms, consent, or reporting logic. Published: 2026-06-02 Author: František Bujnovský Category: Analytics When performance drops, campaigns usually get blamed first. Budgets are moved, keywords are paused, audiences are rebuilt, creatives are questioned, and the reporting meeting becomes a debate about whether the agency, platform, or market changed. Sometimes that is correct. Campaigns can be poorly targeted, too expensive, badly structured, or pushed into traffic that is not commercially useful. But if the measurement layer is damaged, changing the campaigns can make the situation worse: you optimize against a broken signal and lose the ability to tell whether the fix helped. ## The short version > Do not ask whether the campaigns are good until you know whether the conversion signal is real, complete, and comparable over time. The point is not to protect campaigns from criticism. The point is to avoid making campaign decisions from data that no longer describes what actually happened on the website, in analytics, or in the CRM. ## Five signs the problem is probably measurement A campaign problem usually has a marketing pattern. A measurement problem usually has a systems pattern. These signs are worth checking before you move budget or rewrite the account structure. 1. The drop starts on the same day as a website release, GTM publish, cookie banner change, form update, CRM integration change, or checkout change. 2. Sessions, clicks, spend, and landing-page engagement stay relatively stable, but reported conversions fall sharply or disappear. 3. The same problem appears across several campaigns, channels, or landing pages that do not share one obvious marketing cause. 4. GA4, ad platforms, and the CRM disagree in a new way: not just by normal attribution differences, but by missing events, missing leads, duplicated conversions, or empty source fields. 5. The team cannot explain what exactly counts as a conversion, where it fires, who owns it, and whether it still fires only after a successful business action. None of these signs proves the campaigns are fine. They prove that the measurement layer is no longer trustworthy enough to use as the only basis for campaign decisions. ## What a real campaign problem looks like It is still possible that the campaigns are the issue. The difference is that campaign problems usually show up in media and traffic quality before they show up in the measurement stack. - Search terms, placements, audiences, or geographies changed and traffic is visibly less relevant. - CPC, CPM, impression share, auction pressure, or budget limits changed in a way that explains the commercial drop. - The website conversion event still fires correctly, but lead quality, qualification rate, or revenue from a specific campaign segment is worse. - Only one campaign, audience, keyword group, creative set, or market is affected while the rest of the measurement chain behaves normally. That kind of evidence belongs in campaign work. But if you cannot first prove that the conversion path is still clean, campaign optimization becomes guesswork with a dashboard attached. ## Start with a timeline, not with opinions The fastest way to stop the debate is to build a simple timeline. Put the performance drop next to operational changes. You are looking for a coincidence that is too precise to ignore. - Website deploys, redesigns, landing-page edits, form plugin updates, checkout changes, and thank-you page changes. - GTM publishes, new tags, trigger edits, consent-mode changes, cookie banner changes, and analytics configuration changes. - CRM field changes, webhook changes, Zapier or n8n flow edits, duplicate rules, lifecycle-stage changes, and lead-routing changes. - Campaign changes: budgets, bidding strategy, new creatives, new landing pages, changed locations, changed audiences, and changed conversion actions. If reported conversions collapse on the same day a cookie banner or form integration changed, do not start by rewriting campaigns. Start by verifying the measurement path. ## Trace one conversion path end to end Do not audit everything at once. Pick one important action and follow it from the first visit to the business system. For lead generation, that is usually a successful form submission on a paid landing page. 1. Open the landing page and submit a realistic test lead. Confirm that the form actually succeeds, not only that a button was clicked. 2. Check whether the success event fires once, with the right name, after the successful submit and not on page load, validation error, or button click. 3. Confirm that consent behavior is intentional: tags should not fire too early, too late, or differently from the documented consent setup. 4. Check whether GA4 receives the event, whether the relevant event is marked as a key event, and whether the event is duplicated by another tag. 5. Check the ad platform conversion action: source, primary or secondary status, counting method, attribution settings, conversion window, and recent change history. 6. Check the CRM or lead inbox. The test lead should arrive with source, medium, campaign, landing page, timestamp, and click identifiers where your setup captures them. This is not a full analytics audit. It is a controlled proof that the most important signal still exists. If the test fails, the campaign performance discussion should pause until the signal is fixed. ## Watch for these reporting traps Some problems look like campaign performance because the dashboard presents them that way. The dashboard can be technically live and still misleading. - One chart mixes clicks, form starts, form submits, key events, platform conversions, CRM leads, and qualified opportunities under one label. - Recent data is judged before normal processing delay, attribution delay, or lead qualification delay has passed. - A dashboard compares metrics with different date logic: click date, event date, lead-created date, stage-change date, and closed-won date. - Consent changes are treated as if they only affect legal compliance, even though they can change what identifiers and events are available for reporting. - The dashboard has no owner for metric definitions, so every team interprets leads, conversions, and revenue differently. ## A practical decision rule Use this rule before changing campaigns: if the commercial result changed but the measurement path has not been verified, the first task is diagnosis, not optimization. - If traffic quality changed and measurement is clean, work on campaigns. - If measurement changed and traffic is stable, fix measurement before campaign changes. - If both changed, isolate one conversion path first, then decide whether the remaining problem is media quality, website conversion, or sales follow-up. - If nobody can define the metric, do not use it for budget decisions. ## What to send the team The useful output is not a long analytics document. It is a short note that explains whether the conversion signal can currently be trusted. - What action was tested: for example, successful contact form submit on the paid landing page. - Where it was verified: browser, tag manager, GA4, ad platform, CRM, integration log, or dashboard. - What is working, what is not working, and what cannot be concluded from the current data. - Which decision is safe now: keep campaigns unchanged, pause budget changes, fix tracking, review landing pages, or investigate traffic quality. This turns a vague argument into an operational decision. The team does not need perfect analytics to move forward. It needs to know which signal is reliable enough for the next decision. ## Bottom line A campaign can be weak. A market can change. A landing page can stop converting. But if conversion tracking, consent behavior, form handoff, attribution, or CRM fields are broken, the first problem is not campaign performance. The first problem is that the team is steering with an unreliable instrument. Before you change bids, budgets, or agencies, verify the signal. Start with the [Free Tracking Checker](/tracking-checker) for the public basics, then trace the key conversion path into analytics and the CRM. If the path breaks or the report cannot explain its own numbers, the next step is a [measurement cleanup](/services/web-analytics), not another campaign rebuild. --- Source: https://narrativva.com/blog/why-google-ads-ga4-and-crm-numbers-do-not-match Markdown: https://narrativva.com/blog/why-google-ads-ga4-and-crm-numbers-do-not-match.md # Why Google Ads, GA4, and CRM numbers do not match A practical explanation of why campaign, analytics, and sales numbers disagree, what differences are normal, and what to check before you blame the campaigns. Published: 2026-05-11 Author: František Bujnovský Category: Analytics If Google Ads shows 42 conversions, GA4 shows 36 key events, and the CRM shows 29 leads, it does not automatically mean that something is broken. It means the three systems are answering different questions. The problem starts when a team treats those three numbers as if they should be identical. Then every reporting meeting turns into guessing: maybe Google Ads is overreporting, maybe GA4 is missing something, maybe the CRM is wrong, maybe the agency is hiding bad performance. Most of the time, the first step is simpler: define what each number is actually counting. ## The short version > The goal is not to make every report show the same number. The goal is to know which number to use for which decision. Google Ads is built for campaign measurement and bidding. GA4 is built for behavior and cross-channel analysis. A CRM is built for sales operations and lead management. They overlap, but they do not share the same purpose, timing, attribution rules, or data-cleaning logic. - Google Ads asks: which ad interaction should get credit for a conversion used in campaign reporting or bidding? - GA4 asks: what happened on the website or app, and which channels contributed to important user actions? - The CRM asks: which usable leads, opportunities, customers, or deals exist in the sales process? ## What Google Ads is counting Google Ads conversion data exists to help you evaluate and optimize campaigns. That sounds obvious, but it matters. The Conversions column is not a neutral business ledger. It is shaped by conversion actions, attribution settings, conversion windows, counting method, inclusion in bidding, invalid-click filtering, and the date when Google Ads assigns credit. - A lead conversion can be counted as one conversion per ad interaction or every conversion after the interaction. For lead generation, one is often cleaner; for purchases, every may make more sense. - A conversion only counts if it falls inside the selected conversion window. A shorter window will usually produce fewer reported conversions. - Recent Google Ads performance can look worse than it really is because some users convert days or weeks after the click. That is [conversion lag](https://support.google.com/google-ads/answer/9347141). - If GA4 key events are used to create Google Ads conversions, the setup is closer, but the reports still need to be compared with the same attribution scope and date logic. Google's own documentation is explicit that [conversion counting choices](https://support.google.com/google-ads/answer/3438531) matter. For example, Google Ads lets you choose whether a conversion action counts every conversion or only one conversion after an interaction. That single setting can explain a large gap before you even look at GA4 or the CRM. ## What GA4 is counting GA4 is event-based. It records events from the website or app, lets you mark important actions as key events, and can create Google Ads conversions from those key events. Google's [conversions vs. key events](https://support.google.com/analytics/answer/13965727) naming matters here: a GA4 key event in a standard report is not automatically the same thing as the Google Ads Conversions column used for campaign optimization. - GA4 reports website and app behavior across channels, not only Google Ads traffic. - GA4 attribution settings decide which channels are eligible to receive credit for key events and web conversions shared with Google Ads. - GA4 data can keep changing during processing. In its [data freshness documentation](https://support.google.com/analytics/answer/11198161), Google states that processing can take 24 to 48 hours. - Consent, identifiers, thresholds, and modeling can change what appears in Analytics reports, especially on lower-volume properties or in narrow date ranges. This is why comparing yesterday in GA4 with yesterday in Google Ads is often a bad diagnostic. The numbers are still moving, attribution may not be aligned, and recent conversions may not have fully arrived yet. ## What the CRM is counting The CRM is usually the closest thing to commercial truth, but it is not automatically the cleanest measurement system. A CRM record depends on form logic, integrations, duplicate handling, required fields, spam filters, sales rules, manual edits, lifecycle stages, and whether the team actually uses the CRM consistently. - A form submit in GA4 may become no CRM lead if the backend rejects it, the integration fails, or the CRM deduplicates it into an existing contact. - A CRM lead may have no clean source if UTM parameters, gclid, gbraid, wbraid, referrer, or landing-page fields are not captured and stored. - A lead can be created days after the original session if the sales team imports it manually, edits it, or moves it between systems. - A CRM opportunity or customer count is intentionally smaller than a raw conversion count because it filters for quality, qualification, and sales progress. ## Normal reasons the numbers differ Some differences are not only normal, they are expected. Before looking for a bug, check these causes first. 1. Different date logic. Google Ads can assign a conversion to the ad interaction date, while Analytics reports the event when it happened. The CRM usually uses lead creation, update, or stage-change dates. 2. Different attribution scope. Google Ads looks at eligible ad interactions. GA4 can look across paid and organic channels. The CRM may use first touch, last touch, self-reported source, or whatever the integration writes into a field. 3. Different counting rules. Google Ads may count one or every conversion. GA4 counts events and key events. The CRM may deduplicate contacts or suppress repeat submissions. 4. Different conversion definitions. A button click, successful form submit, thank-you page view, qualified lead, sales opportunity, and closed deal are different business events. 5. Different time zones. Google Ads account timezone, GA4 property timezone, Looker Studio data source settings, and CRM workspace timezone can be out of sync. 6. Processing and lag. GA4 reports can change during processing, and Google Ads conversions can arrive later because people do not always convert immediately after clicking. 7. Consent and identifiers. If analytics or ads storage is denied, some identifiers are unavailable. Depending on the setup, reports may rely on observed data, modeled data, or miss some detail entirely. 8. Broken or incomplete handoff to the CRM. The tracking can fire correctly, but source fields, click IDs, hidden form fields, or webhook payloads may still fail on the way into the CRM. ## When the mismatch is suspicious A mismatch is not automatically a problem. A pattern is. These are the situations worth investigating quickly. - Google Ads shows conversions, but GA4 has no matching key event or event volume for the same action. - GA4 records form submits, but the CRM does not receive the leads or receives them without source fields. - The gap appears suddenly after a redesign, cookie-banner change, GTM publish, form plugin update, or CRM integration change. - Paid traffic keeps spending, but CRM-qualified leads drop while raw website events stay stable. - A report uses yesterday or today as proof of performance without accounting for processing delay or conversion lag. - A dashboard blends Google Ads, GA4, and CRM metrics under one label called leads without explaining the source and definition. ## A practical reconciliation process Do not start by comparing all dashboards. Start with one conversion path and trace it from click to CRM. 1. Choose one business action. For example: successful contact form submission on a specific landing page. Do not mix button clicks, page views, and qualified leads in one comparison. 2. Pick a completed date range. Avoid today and yesterday. For lead-gen accounts, use a range that is old enough for normal conversion lag and CRM processing. 3. Check the raw website event first. Confirm that the form success event fires once, with the right name, on the right trigger, and only after a real successful submit. 4. Check GA4 event and key event setup. Make sure the event is collected, marked correctly if it should be a key event, and not duplicated by another tag or enhanced measurement setting. 5. Check the Google Ads conversion action. Confirm the source, count setting, conversion window, include-in-conversions setting, attribution settings, and whether the action is primary or secondary. 6. Check the CRM handoff. Submit a test lead and verify that source, medium, campaign, landing page, click ID, consent state, and timestamp arrive in the CRM or integration log. 7. Separate raw leads from qualified leads. Report them as two different metrics. A campaign can generate many form submits and still produce few usable leads. 8. Document the expected gap. A healthy setup can still have a normal difference between ad conversions, analytics key events, CRM leads, and qualified opportunities. ## Which number should you trust? The better question is: what decision are you making? - Use Google Ads conversion data for campaign optimization, bidding, and platform-level campaign diagnostics. - Use GA4 for website behavior, channel comparison, landing-page analysis, and understanding what users did before the lead. - Use the CRM for lead quality, pipeline, revenue, sales follow-up, and whether the business actually received something useful. - Use a reconciled dashboard only after every metric has a clear definition, source, date logic, and owner. A common mistake is to make the CRM the only truth for campaign optimization. The CRM is essential, but it often arrives late, has lower volume, and includes sales decisions that the ad platform cannot observe directly. Another common mistake is to trust Google Ads alone and ignore whether those conversions become real leads. The useful setup connects both views without pretending they are the same report. ## What a good reporting setup looks like The cleanest reporting systems do not hide disagreement. They explain it. A good dashboard should make it obvious whether a number comes from Google Ads, GA4, or the CRM, what it means, how it is counted, and why it may differ from the neighboring metric. - Name metrics precisely: form_success_events, Google Ads primary conversions, CRM new leads, CRM qualified leads, opportunities, and closed revenue are not interchangeable. - Keep campaign, analytics, and CRM numbers next to each other, not merged into one unexplained total. - Show both volume and quality: raw conversions tell you whether the journey is producing actions; CRM stages tell you whether those actions are commercially useful. - Add a short measurement note to the report. One paragraph is often enough to prevent the same argument every month. ## Bottom line Google Ads, GA4, and CRM numbers should be close enough to explain, not identical enough to stop thinking. A small, documented gap is normal. A sudden unexplained gap is a measurement issue until proven otherwise. If your reports disagree and you do not know which number drives decisions, start with the public basics: run the [Free Tracking Checker](/tracking-checker), then review the conversion path from event to CRM. If the gap still does not make sense, the next step is not another dashboard. It is a [measurement cleanup](/services/web-analytics). --- Source: https://narrativva.com/blog/how-to-share-microsoft-ads-access Markdown: https://narrativva.com/blog/how-to-share-microsoft-ads-access.md # How to share Microsoft Ads access (Updated 2026) How to invite a user to Microsoft Advertising without sharing the main login, and when account linking is cleaner than adding a user. Published: 2026-03-19 Author: František Bujnovský Category: How-to If someone needs to work in Microsoft Ads, do not pass them the main credentials. The cleaner setup is to invite them as a user with their own login, or to use formal account linking when an agency is managing the account. Based on Microsoft Advertising guidance, adding a user requires Super Admin access on the account. For agency work, Microsoft recommends a formal relationship instead of simply stacking more users into one account. ## Step by step 1. Open [Microsoft Advertising](https://ads.microsoft.com/) with a Super Admin account. 2. From Settings, open User management. 3. Choose Invite user. 4. Enter the invitation email and choose the account role. 5. Send the invitation and wait for the user to accept it. Microsoft notes that the invitation email is mainly for sending the invite. The invited person can later sign in with a different Microsoft account if the setup allows it. ## When to add a user and when to link an agency - Add a user when it is an internal teammate or a named freelancer. - Use formal account linking when a full agency account will manage campaigns. - Keep billing and super-admin control on the client side wherever possible. In practice, the same principle applies here as elsewhere: separate identity, intentional role choice, and fewer high-level permissions than feels comfortable at first. If Microsoft Ads is only one part of the setup, the [Sharing Access hub](/access-guides) covers the rest. --- Source: https://narrativva.com/blog/how-to-share-google-ads-and-ga4-access Markdown: https://narrativva.com/blog/how-to-share-google-ads-and-ga4-access.md # How to share Google Ads and GA4 access (Updated 2026) Step-by-step guide to granting Google Ads and Google Analytics 4 access without sharing passwords, plus a few practical permission tips. Published: 2026-03-09 Author: František Bujnovský Category: How-to If someone is helping with campaigns, analytics, or reporting, do not send a shared login. The safer and cleaner approach is to add them as a user and give them only the level of access they actually need. In practice, this usually means granting access separately in Google Ads and in Google Analytics 4. They are different products, so one invitation does not cover both. ## Google Ads 1. Open [Google Ads](https://ads.google.com/home/) and go to Admin. 2. Open Access and security. 3. Click the plus button to add a new user. 4. Enter their email address and choose the right access level. 5. Send the invitation and wait for acceptance. If the person is actively managing campaigns, standard or admin-style access may be necessary. If they only need to review setup or performance, lower access is often enough. ## Google Analytics 4 1. Open [Google Analytics](https://analytics.google.com/analytics/web/) and click Admin in GA4. 2. Choose Account access management or Property access management. 3. Click the plus button and choose Add users. 4. Enter the email address, assign the needed role, and send the invite. In GA4, think carefully about whether someone needs account-level access or just property-level access. In many cases, property access is enough and keeps the setup cleaner. ## Before you send the invite - Use the exact email address the person uses for Google tools. - Check whether they really need edit access or only view-level access. - Keep owner-level permissions limited to the client side unless there is a strong reason otherwise. That is the practical baseline: no password sharing, separate access per tool, and permission levels chosen intentionally instead of generously. If you are still mapping the whole stack, the [Sharing Access hub](/access-guides) gives you the rest of the platform guides. --- Source: https://narrativva.com/blog/how-to-share-meta-business-manager-access Markdown: https://narrativva.com/blog/how-to-share-meta-business-manager-access.md # How to share Meta Business Manager access (Updated 2026) A practical guide to giving an agency, freelancer, or contractor access in Meta without creating shared logins or messy workarounds. Published: 2026-03-08 Author: František Bujnovský Category: How-to Meta access often causes confusion because there are two valid ways to do it. You can add a specific person to your business, or you can share assets with a partner business. The correct option depends on whether you are working with an individual or with an agency account. ## If you are inviting a person 1. Open [Meta Business Settings](https://business.facebook.com/settings/) in Business Manager. 2. Go to Users and then People. 3. Click Invite people. 4. Enter the email address and choose the appropriate access. 5. Assign the required assets such as ad accounts, pages, or pixels. This approach is usually best when you are working with one freelancer or one named contact. It is less ideal when multiple people from an agency need access over time. ## If you are sharing with an agency 1. Open [Meta Business Settings](https://business.facebook.com/settings/) and go to Users, then Partners. 2. Choose to add a partner. 3. Enter the partner business ID. 4. Select the assets you want to share and assign the right permissions. If an agency is managing ads for you, partner access is usually cleaner than adding several individual people manually. It is easier to manage and easier to revoke later. ## What to check before you confirm - Make sure you are sharing the correct ad account, page, pixel, and catalog if relevant. - Avoid giving full admin rights if the work only requires campaign management or reporting. - If you stop working together, remove the access cleanly instead of leaving old permissions in place. The main principle is simple: use person access for people, partner access for agencies, and keep the asset list tighter than feels convenient. If Meta is only one layer in the setup, the [Sharing Access hub](/access-guides) covers the rest. --- Source: https://narrativva.com/blog/how-to-share-microsoft-clarity-access Markdown: https://narrativva.com/blog/how-to-share-microsoft-clarity-access.md # How to share Microsoft Clarity access (Updated 2026) How to give someone access to Microsoft Clarity recordings, heatmaps, and project settings without sharing one common account. Published: 2026-03-07 Author: František Bujnovský Category: How-to Microsoft Clarity is simple compared to larger ad platforms, but the access principle is the same: do not pass one shared login around. If someone needs to review recordings, heatmaps, or findings, add them to the correct project directly. That keeps access cleaner, makes audits easier, and avoids the typical situation where nobody knows who still has access to the project. ## Step by step 1. Open the correct project in [Microsoft Clarity](https://clarity.microsoft.com/). 2. Open Settings. 3. Go to Team or project access management. 4. Invite the user by email. 5. Choose the appropriate role and send the invite. Use the minimum level of access that still lets the person do the job. For most reviews, there is no reason to over-grant admin rights. ## When this is usually needed - You want an agency to review UX friction from recordings. - A marketer or product person needs access to heatmaps. - Someone is validating post-launch behavior after a redesign or campaign change. Clarity tends to be simple operationally, which is exactly why access should stay tidy. If more people need it later, add them intentionally instead of defaulting to one shared account. If you are reviewing several tools at once, the [Sharing Access hub](/access-guides) gives you the broader access map. --- Source: https://narrativva.com/blog/how-to-share-google-tag-manager-access Markdown: https://narrativva.com/blog/how-to-share-google-tag-manager-access.md # How to share Google Tag Manager access (Updated 2026) How to grant access to the right GTM account or container while keeping publish rights under control. Published: 2026-03-06 Author: František Bujnovský Category: How-to If someone is implementing tracking, consent updates, or tag QA, they usually need access to Google Tag Manager. The safe approach is to add them as a user and assign only the access they need on the right level. In GTM, you usually decide between account-level and container-level access. That distinction matters, because many collaborators only need access to one container, not to the whole account structure. ## Step by step 1. Open [Google Tag Manager](https://tagmanager.google.com/). 2. Go to Admin. 3. Choose User Management on the account or container level. 4. Click the plus button and add the user by email. 5. Assign the required account and container permissions. 6. Send the invitation. In many cases, someone needs editing and preview access, but not publish access. Keeping publish permissions tighter is usually the safer setup, especially when multiple vendors or freelancers touch the same container. ## A practical rule of thumb - Give view or edit access if the person is auditing or preparing changes. - Reserve publish access for the people who are responsible for final release. - Use container-level access where possible instead of broad account-level access. That gives collaborators enough room to work, while keeping the risk of accidental production changes much lower. If GTM is just one part of a larger cleanup, the [Sharing Access hub](/access-guides) covers the rest of the tools. --- Source: https://narrativva.com/blog/how-to-share-google-search-console-access Markdown: https://narrativva.com/blog/how-to-share-google-search-console-access.md # How to share Google Search Console access (Updated 2026) How to add a user or delegated owner in Search Console without handing over the main account, plus which role usually makes sense. Published: 2023-03-20 Author: František Bujnovský Category: How-to If someone needs to review indexing, coverage issues, or search performance, give them access directly in Search Console instead of passing one main login around. The clean setup is property-level access with the smallest role that still lets them do the work. According to Google, only a property owner can add or remove users. Search Console also distinguishes between owners, full users, and restricted users, so it is worth choosing the role intentionally instead of defaulting to ownership. ## Step by step 1. Open the correct property in [Google Search Console](https://search.google.com/search-console). 2. Open Settings and go to Users and permissions. 3. Click Add user. 4. Enter the Google Account email of the person you want to add. 5. Choose the role and save the change. ## Which role usually makes sense - Use Full user when someone needs to inspect performance and indexing in a meaningful way. - Use Restricted user if they only need a light read-only view. - Use owner access only when they genuinely need user administration or ownership-level actions. Google also notes that users must have a valid Google Account, and email groups cannot be added as users. If someone should not be a user any more, remove the access in the same Users and permissions screen. Practical rule: keep verified ownership on the client side, add delegated access only where it is needed, and treat Search Console as a property-specific tool rather than a shared team inbox. If you need similar instructions for the rest of the stack, open the [Sharing Access hub](/access-guides). --- Source: https://narrativva.com/contact Markdown: https://narrativva.com/contact.md # Contact That might be broken analytics, a slow website, campaigns running on weak data, too much manual reporting, or an internal tool that should work better. Send a few details and we will tell you what makes sense. --- Source: https://studio.narrativva.com/ Markdown: https://studio.narrativva.com/index.md # The Performance Reset landing page The Performance Reset is a Narrativva Studio landing page for teams that spend on ads and need precision tracking, a rebuilt website, and clearer reporting. Use the subdomain as the canonical landing page URL.