What Can SchemaNexa Do?
Fix the tracking. Build the infrastructure. Know what actually converts.
SchemaNexa helps businesses solve two connected problems: unreliable marketing data, and websites that are difficult to manage, measure, or scale. I work directly with businesses and agencies to repair Google Ads conversion tracking with Google Tag Manager and GA4, and to build or migrate websites using Payload CMS.
Operated directly by Rafa — no account managers, no handoffs.
Google Ads Conversion Tracking
When Google Ads conversion numbers don't match your real enquiries, CRM leads, calls, bookings, or sales, the tracking architecture behind the campaign is usually the reason. Smart Bidding optimizes toward whatever conversion data it receives — SchemaNexa's job is to make that data reliable.
What Gets Fixed
Conversion action setup
Configuring primary and secondary conversion actions correctly.
Duplicate conversions
Finding and removing leads that get counted more than once.
Missing conversions
Real actions that never register in Google Ads at all.
Form and contact tracking
Form submissions, contact forms, and button clicks.
Phone and messaging clicks
Phone click tracking and WhatsApp or messaging click tracking.
Thank-you page tracking
Confirming conversions fire from the right page, at the right time.
Purchase and lead events
Ecommerce purchase events and lead-generation events.
Cleanup and verification
Removing stale conversion actions and verifying what remains is accurate.
GA4 and Google Ads alignment
Making sure both platforms agree on what counts as a conversion.
Google Tag Manager Setup and Cleanup
GTM containers tend to accumulate problems over time — duplicate tags, unused triggers, old scripts from a previous agency, conflicting Google Ads tags, and inconsistent event naming. Every change gets verified in GTM Preview and GA4 DebugView before it goes live, not assumed to be working.
What SchemaNexa Configures
Google Ads tags
Conversion tags and Conversion Linker configured correctly.
GA4 event tags
Clean, consistently named events sent to GA4.
Click and form tracking
Button clicks, form submissions, and dataLayer events.
Scroll and video tracking
Engagement signals where they add real value.
Ecommerce tracking
Purchase and cart events for online stores.
Cross-domain tracking
Keeping sessions intact across separate domains.
Consent configuration
Tags respecting consent state correctly.
Trigger and variable cleanup
Removing what is unused, fixing what fires incorrectly.
Naming standards and documentation
A container the next person can actually understand.
GA4 Analytics Setup
GA4 should measure the actions that matter to your business — generate_lead, book_appointment, request_quote, phone_click, email_click, purchase — not become an unstructured pile of every possible interaction. The objective isn't to track everything. It's to track the right things accurately.
Tracking Audits
Not every project needs a rebuild. A tracking audit reviews Google Ads conversions, GTM, GA4, forms, landing pages, thank-you pages, and event configuration to find out exactly what's wrong before recommending any changes.
What Audits Commonly Find
Conversions firing twice
The same action counted more than once.
Forms not triggering conversions
A real submission that never reaches Google Ads.
Conversions firing too early
Counted before the form was actually completed.
GA4 and Google Ads disagreeing
Two platforms reporting two different numbers.
Old tags still running
Scripts from a previous setup nobody remembered were there.
Duplicate counting methods
Two separate mechanisms tracking the same lead.
Inconsistent event naming
Making reporting harder to trust than it should be.
Untracked important actions
Calls, bookings, or enquiries with no tracking at all.
Tracking for WordPress, Shopify and Other Platforms
You don't need to migrate to Payload CMS to work with SchemaNexa on tracking. If a website can expose the action that needs to be measured, there is usually a way to build reliable tracking around it — regardless of what the site is built on.
Platforms Worked With
WordPress
Elementor
WooCommerce
Shopify
Next.js / React
Framer
Custom websites
Landing-page builders
CRM and Lead Tracking Integrations
The goal is a clean path: ad, website, lead, CRM, business outcome. Depending on the project, that can mean connecting HubSpot, Zoho, embedded CRM forms, booking systems, APIs, webhooks, or server-side integrations — scoped to what the project actually needs, not promised as an out-of-the-box guarantee.
Payload CMS Website Development
Payload is a modern, developer-focused CMS that gives structured content management alongside a fast, fully customizable frontend — the same architecture this website runs on.
What Gets Built
Business & service websites
Marketing websites
Lead-generation websites
SEO-focused sites
Blogs & publishing systems
Landing-page systems
Resource centres
Location-based websites
Custom CMS dashboards
Payload CMS Development
See detailed capabilities, examples, and what a typical build includes.
All Services
Browse everything SchemaNexa offers, from tracking to full website builds.
Custom Content Management Systems
The CMS should match how your business actually works, not force it into a generic page-builder structure. Content gets modeled around what you have — Pages, Services, Locations, Team, Blog, FAQs, Testimonials, Case Studies — so marketing teams can update structured content without touching code or breaking layouts.
Common Content Structures
Pages
Flexible, block-based pages for any part of the site.
Services & Locations
Structured entries for what you offer and where.
Team members
Author and staff profiles reused across the site.
Blog posts & authors
A full publishing system, not just a plugin.
FAQs & testimonials
Reusable content blocks editors control directly.
SEO metadata & global settings
Site-wide fields editors manage without a developer.
Website Migration to Payload CMS
A migration is not just copying text between platforms. It means mapping URLs, setting up redirects, preserving metadata, recreating structured data, and checking analytics, GTM, GA4, and Google Ads tracking still work correctly after launch.
What Gets Carried Over
URL mapping and redirects
Intentional redirects wherever a URL has to change.
Metadata
Title tags, meta descriptions, and headings preserved.
Canonical URLs & structured data
Recreated to match the new site, not left behind.
Internal links & image metadata
Checked rather than assumed to carry over.
Sitemap & robots.txt
Configured correctly for the new platform.
Analytics, GTM, GA4, Google Ads
Verified working before and after launch.
Search Console & post-launch checks
Monitored after go-live, not just at launch.
SEO-Safe Website Migration
"Will we lose our Google rankings?" is a fair question — poor migrations can genuinely damage organic visibility. SchemaNexa doesn't guarantee ranking preservation, but plans for it deliberately: preserving important URLs where possible, redirecting intentionally where they change, retaining metadata, protecting internal linking, and monitoring after launch.
Technical SEO Foundations
Structured data is added where it matches what's actually on the page — not forced onto every page for the sake of it. The visible content stays useful with or without rich-result eligibility.
What Gets Covered
Editable SEO titles & descriptions
Managed in the CMS, not hardcoded.
Canonical URLs
Correct on every page, including the homepage.
XML sitemaps & robots.txt
Generated from real content, not guesswork.
Open Graph & X metadata
Correct previews when links get shared.
Structured data
Organization, Person, Article, and Breadcrumb schema, applied where it matches the page.
Internal linking & alt text
Clean structure, accessible images.
Clean URLs & fast rendering
No unnecessary redirects or render-blocking delays.
Website Performance
Performance isn't just a Lighthouse score — it's what a mobile visitor experiences after clicking a paid ad, and what keeps organic visitors on the page instead of bouncing back to search results.
Landing Pages for Paid Advertising
SchemaNexa can design the landing page and its measurement architecture together, instead of adding tracking on after development is already finished.
What Gets Built In
Focused campaign messaging
Clear CTA structure
Lead forms
Conversion tracking
GA4 & Google Ads events
GTM & CRM integration
Mobile optimization
Fast loading
Know What Actually Converted
Which form generated the lead?
Which landing page converted?
Which CTA was clicked?
Are phone calls being measured?
Are WhatsApp enquiries measured?
Are leads counted more than once?
Does Google Ads see the same conversion GA4 sees?
Are campaigns optimizing toward the intended action?
Technical Tracking Support for Agencies
SchemaNexa can support agencies behind the scenes on tracking audits, GTM implementation, GA4 events, Google Ads conversion setup, landing-page tracking, debugging, technical documentation, CMS development, and migrations. The agency keeps the client relationship; SchemaNexa handles the technical implementation layer.

Rafael Arceo — Founder, SchemaNexa
Who Actually Does the Work
SchemaNexa is operated directly by Rafa. Projects are handled directly rather than passed through multiple layers or account managers.
10+ years in digital marketing
Hands-on Google Ads, GTM & GA4 implementation
Payload CMS, SEO, and analytics experience
Technical implementation combined with marketing strategy
Who This Is For
You run Google Ads
but are unsure whether conversions are accurate.
Your agency manages advertising
but needs someone technical to implement tracking.
Your GA4 account is confusing
and nobody trusts the events anymore.
Your WordPress site is slow
or difficult to maintain.
Your marketing team depends on developers
for basic content changes.
You are planning a migration
and want to protect existing SEO.
Tracking and Website Development Work Better Together
A good campaign can't optimize reliably from bad conversion signals, and accurate tracking can't compensate for a slow, confusing website. Advertising leads to a landing page, a conversion, GTM, GA4, Google Ads, a CRM, and finally an actual lead or sale — the strongest implementation considers the website and the measurement architecture together, from the start.
Working With SchemaNexa
The process below is the same six-step delivery model used across every SchemaNexa engagement — see the Working Together page for the full breakdown.
How Working With SchemaNexa Works
Tell Me What Is Happening
You describe the problem — a symptom, a suspicion, or a project goal.
I Review the Setup
Google Ads, GTM, GA4, the website, or all three, depending on the request.
You Get a Clear Scope
What needs fixing, why, and what it involves — before any work starts.
I Implement It Directly
No handoffs to other developers or account managers.
Everything Important Gets Tested
Verified in GTM Preview, GA4 DebugView, or live, before sign-off.
You Receive a Clear Handover
Documentation of what changed and what to expect.
Frequently Asked Questions
What exactly does SchemaNexa do?
SchemaNexa specializes in Google Ads conversion tracking using Google Tag Manager and GA4, together with Payload CMS website development and SEO-conscious CMS migrations.
Can SchemaNexa fix my Google Ads campaigns?
SchemaNexa primarily fixes the measurement and tracking architecture behind your campaigns, not full campaign management. Accurate conversion data gives Google Ads better signals to optimize toward — it doesn't guarantee a specific performance improvement.
Can you tell whether my Google Ads tracking is wrong?
Yes — a tracking audit reviews Google Ads, GTM, GA4, and the website together to identify exactly what is broken, missing, or duplicated.
Can you track Elementor forms?
Yes, depending on how the form is implemented.
Can you track HubSpot forms?
Yes, depending on how the form is implemented.
Can you track Shopify?
Yes, including GA4, Google Ads, and ecommerce events where applicable.
Can you work on WordPress without rebuilding the website?
Yes. Tracking work on WordPress does not require moving to a new CMS.
Do I have to use Payload CMS?
No. Tracking, GTM, and GA4 work is independent of what platform your website runs on.
Why does SchemaNexa use Payload CMS?
It gives structured content management alongside a fast, fully customizable frontend — flexible architecture without plugin bloat.
Is Payload CMS good for SEO?
The CMS alone does not guarantee SEO outcomes — implementation matters. Payload gives full control over metadata, structured data, and page speed, which a good implementation uses correctly.
Can you migrate WordPress to Payload CMS?
Yes, depending on the project requirements and existing content structure.
Can you preserve our current URLs?
Where possible, yes. Where a URL genuinely needs to change, an intentional redirect is put in place.
Can you migrate the blog too?
Yes, including posts, authors, categories, media, and SEO relationships, depending on your existing system.
Can our team edit the website afterwards?
Yes — that is one of the main purposes of the CMS.
Can you build the website and tracking together?
Yes. This is one of SchemaNexa's strongest use cases — measurement designed in from the start, not added afterward.
Do you work with agencies?
Yes. SchemaNexa can handle the technical implementation layer while the agency keeps the client relationship.
Who actually does the work?
SchemaNexa is operated directly by Rafa. Projects are handled directly rather than being passed through multiple layers.
Not Sure Where to Start?
Find the description closest to what you are dealing with.
Google Ads says I have more leads than I actually received.
Our form submissions are not appearing as conversions.
Our GTM container is a mess.
Our website is slow and difficult to update.
We want to leave WordPress but are worried about SEO.
We are building a new landing page for Google Ads.
Build a System You Can Trust
Your website generates the interaction. Your analytics records it. Your advertising platforms optimize from it. Your CRM turns it into a business opportunity. Those systems should agree with each other — SchemaNexa helps connect them.
Fix the tracking. Build the infrastructure. Know what actually converts.