AgencyGenius

How to Set Up Google Ads Enhanced Conversions on Duda Using GTM

Fri, 27 Mar 2026 14:19:29 GMT

When someone fills in a form on your website and that counts as a conversion, Google Ads needs to match that conversion back to the person who clicked your ad. Normally it does this with cookies. But cookies are becoming less reliable - browsers block them, people clear them, and privacy rules limit what they can do.

Enhanced Conversions give Google a backup method. When someone submits a form, you take the data they typed in (like their email address or phone number), scramble it into a code that can't be reversed (called hashing), and send that scrambled version to Google. Google then matches it against the data they already have on that user from their Google account.

The result: better conversion tracking, better data in your ad account, and better decisions on where your budget goes.

Important: The data is hashed before it leaves the browser. Google never sees the actual email or phone number from your site. It only sees the scrambled version.

Yes. This guide works with both the standard Contact Form widget and the newer Advanced Form widget (the flex-based one in Editor 2.0).

Both form types render as standard HTML <form> elements in the browser. The hashing script in this guide uses document.querySelectorAll('form') to find all forms on the page, so it catches both types automatically. As long as your email field uses type="email" and your phone field uses type="tel" (which Duda sets by default for both form types), the script will detect and hash the data correctly.

The only difference between the two is how the success state looks after submission. We cover both scenarios in the trigger setup section below.

- A Duda website with at least one form (Contact Form or Advanced Form) that you want to track as a conversion
- A Google Ads account with a conversion action already set up
- A Google Tag Manager (GTM) container already connected to your Duda site
- About 30 minutes

If you haven't connected GTM to Duda yet, go to your Duda site editor, click Site Settings > Head HTML , and paste your GTM snippet there. That's the  script that GTM gives you when you set up a container.

Before touching GTM, you need to tell Google Ads that you'll be sending enhanced conversion data.

1. Log in to Google Ads
2. Click Goals in the left menu
3. Click Conversions then Summary
4. Click the conversion action you want to enhance (e.g. "Form Submission" or "Lead")
5. Scroll down to Enhanced conversions and click Turn on enhanced conversions
6. Select Google Tag Manager as your setup method
7. Click Save

That's it on the Google Ads side. You're telling Google: "I'm going to send you hashed data through GTM. Be ready for it."

This is the core of the setup. You're going to create a tag in GTM that watches for form submissions on your Duda site, grabs the email and phone fields, hashes them, and stores them so GTM can use them.

1. Open Google Tag Manager
2. Select your Duda site's container
3. Click Tags in the left menu
4. Click New
5. Name it: Enhanced Conversions - Hash Form Data
6. Click Tag Configuration and choose Custom HTML
7. Paste the following code:

What this code does in plain English:

- It finds every form on the page (both Contact Forms and Advanced Forms)
- It attaches a listener that runs when someone submits a form
- When the form is submitted, it looks for email and phone fields
- It takes whatever the person typed, converts it to lowercase, removes any extra spaces, and scrambles it using SHA-256 (the same hashing method Google requires)
- It stores the scrambled data in a place where GTM can pick it up ( window.enhanced_conversion_data )
- It also saves a backup copy in sessionStorage (needed if the form redirects to a thank you page)

Now set the trigger:

1. Click Triggering
2. Click the + icon to create a new trigger
3. Name it: All Pages - DOM Ready
4. Choose DOM Ready as the trigger type
5. Select All DOM Ready Events
6. Save the trigger, then save the tag

You want this running on DOM Ready (not Page View) because Duda forms load dynamically, and you need the form elements to exist before the script tries to find them.

GTM needs a variable that points to the hashed data you stored in Step 2.

1. Click Variables in the left menu
2. Under User-Defined Variables , click New
3. Name it: Enhanced Conversion Data
4. Click Variable Configuration
5. Choose JavaScript Variable
6. In the Global Variable Name field, type: enhanced_conversion_data
7. Save

This variable now reads from window.enhanced_conversion_data , which is where your hashing script stores the scrambled email and phone data.

If you already have a Google Ads Conversion Tracking tag in GTM, you'll edit it. If not, create a new one.

1. Go to Tags
2. Either click your existing conversion tag or click New
3. Name it: Google Ads Conversion - Form Submit (or whatever makes sense)
4. Click Tag Configuration
5. Choose Google Ads Conversion Tracking
6. Fill in your Conversion ID ( AW-XXXXXXX ) and Conversion Label from your Google Ads conversion action settings
7. Set Conversion Value and Currency Code if applicable
8. Scroll down and tick Include user-provided data from your website
9. Under User-Provided Data , choose Manual Configuration

For the user-provided data fields, create two separate JavaScript Variables:

Variable name: EC - Hashed Email / Type: JavaScript Variable / Global Variable Name: enhanced_conversion_data.sha256_email_address
Variable name: EC - Hashed Phone / Type: JavaScript Variable / Global Variable Name: enhanced_conversion_data.sha256_phone_number

Then in your conversion tag's user-provided data section, map Email to EC - Hashed Email and Phone to EC - Hashed Phone .

Your conversion tag needs to fire when the form is actually submitted. There are two ways to handle this on Duda, depending on whether your form shows an inline thank you message or redirects to a separate page.

Both the Contact Form and Advanced Form can show inline success messages after submission. To detect this, add a small script to your Duda site's Body End HTML (Site Settings > Body End) that watches for the success message to appear and pushes an event to GTM:

Why the broad selector list? The standard Contact Form and Advanced Form use different CSS classes for their success states. This script checks for multiple possible class names and also watches for attribute changes (some forms toggle visibility via inline styles rather than adding classes). The offsetHeight > 0 check ensures we only fire when the element is actually visible.

Then in GTM, create a Custom Event trigger with the event name duda_form_submit and assign it to your conversion tag.

If your form redirects to a /thank-you page after submission:

1. Create a new trigger in GTM
2. Name it: Thank You Page View
3. Choose Page View as the trigger type
4. Set it to fire on Some Page Views
5. Set the condition: Page Path contains /thank-you (or whatever your thank you page URL is)
6. Save and assign this trigger to your conversion tag

Important: The hashing script runs on the form page, but the conversion fires on the thank you page. The hashed data stored in window.enhanced_conversion_data won't survive the page change. That's why the hashing script in Step 2 already includes a sessionStorage backup.

You also need a recovery script. Create a separate Custom HTML tag in GTM that fires on the thank you page (DOM Ready trigger filtered to your thank you page path):

Make sure this recovery tag fires before your conversion tag. In GTM, edit your conversion tag, expand Advanced Settings > Tag Sequencing , and set the recovery tag as a setup tag.

Preview first. Always.

1. Click Preview in GTM
2. Enter your Duda site URL
3. Navigate to the page with your form
4. Fill in the form with a test email and phone number
5. Submit the form

What to check in GTM's preview panel:

- Your Enhanced Conversions - Hash Form Data tag should show as "Fired" on DOM Ready
- After form submission, click on the Variables tab and look for enhanced_conversion_data - it should contain sha256_email_address and/or sha256_phone_number values (long strings of letters and numbers)
- Your conversion tag should fire on the form submission event (or page view of the thank you page)
- The conversion tag summary should show user-provided data is being sent

If the hashed data isn't showing:

- Inspect the form in your browser and check what the email input's type and name attributes are. Duda sometimes uses generic names - if so, adjust the findInputByType patterns in the hashing script
- Make sure the Custom HTML tag is firing on DOM Ready, not Page View
- If you're using an Advanced Form with multi-step pages, the email field might not be on the first step. The script attaches on DOM Ready, so fields on later steps should still be caught when the form is submitted
- Check the browser console for any errors

Once everything looks right:

1. Go back to GTM
2. Click Submit
3. Name your version something useful like "Added Enhanced Conversions for form submissions"
4. Click Publish

Enhanced Conversions don't show results instantly. Give it 48-72 hours, then check:

1. Go to Google Ads
2. Click Goals > Conversions > Summary
3. Click your conversion action
4. Look for the Enhanced conversions section - it should show a match rate percentage

A match rate of 30-60% is normal and healthy. It won't be 100% because not everyone uses the same email for your form as they do for their Google account, and that's fine. Even a 30% match rate significantly improves your conversion data.

GTM container snippet - Duda Site Settings > Head HTML - Loads GTM on your sit
Hash Form Data tag - GTM (Custom HTML, DOM Ready) - Scrambles form data and stores it
Enhanced Conversion Data variable - GTM (JavaScript Variable) - Points GTM to the hashed data
Conversion Tracking tag - GTM (Google Ads Conversion) - Sends conversion + hashed data to Google
MutationObserver script - Duda Body End HTML (optional) - Detects inline form success for triggering
sessionStorage recovery script - GTM (Custom HTML, thank you page only) - Recovers hashed data after page redirect

Enhanced Conversions are one of the best things you can do for your Google Ads performance on Duda. The setup takes a bit of work because Duda doesn't have a native integration for it, but once it's running, it's set and forget.

The match rate data alone makes it worth doing - you'll finally know how much conversion data you've been missing, and your Smart Bidding strategies will have significantly more signal to work with.

What Are Enhanced Conversions (and Why Should You Care)?

Does This Work With Both Duda Form Types?

What You'll Need Before Your Start

Step 1: Turn On Enhanced Conversions in Google Ads

Step 2: Create a Custom HTML Tag to Capture and Hash Form Data

Step 3: Create a User-Provided Data Variable

Step 4: Set Up Your Conversion Tag with Enhanced Conversions

Step 5: Set the Conversion Trigger

Option A: Inline Thank You Message (Form Stays on the Same Page)

Option B: Thank You Page Redirect

Step 6: Preview, Test, and Publish

Step 7: Verify in Google Ads

Common Questions

Quick Reference: What Goes Where

Wrapping Up

Why Duda's Video Training Page Isn't Good Enough (And How to Make Your Own)

Fri, 27 Feb 2026 19:37:47 GMT

Duda has a fantastic library of training videos covering everything from editor basics to eCommerce setup. They're well-produced, focused, and genuinely useful. It's one of the best training resources any website builder offers.

The problem isn't the content - it's finding it.

All the videos live on a single page at videos.multiscreensite.com with no search, no categories, and no way to filter. Duda built this with the best intentions, and they keep adding to it - which is great. But as the library has grown, the most valuable and practical videos have ended up further and further down the page and for anyone searching for something specific there is no easy wa y.

What It Looks Like Now

One long feed. No structure. If you need help with something specific, you're scrolling through everything to find it.

Why Building Your Own Is Much Better!

Example shows avago.ai/video-tutorials

The videos are organised into clear categories:

Getting Started
AI Features
Design Techniques
Layout Fundamentals
Breakpoints & Responsive
Site Management
eCommerce
Bookings
Forms & Integrations

Build Your Own With AI

The best bit - you don't need our design. Build your own version using Claude (our LLM of choice) and make it match your branding completely. The design is entirely up to you. Just tell Claude your colours, fonts, and style and it handles the rest.

We've put together a file with all the video URLs, titles, and categories. Copy the prompt below, paste it into Claude, and let it do the work.

The Prompt

Before You Start - Set Up Your MCP

This only works if you've connected the Duda MCP to Claude. If you haven't done that yet or aren't sure what that means, watch this first:

Once connected, paste the prompt, swap in your details, and you'll have a working training hub on your site in minutes — designed however you want.

A searchable, categorised training hub you can drop into any Duda site as an HTML widget. Live keyword search, colour-coded category filters, a responsive video grid, and a modal player with keyboard navigation. Thumbnails lazy-load and cache. It just works.

Adding More is Super Simple, Thanks to Collections

Adding and editing is super simple as the MCP has done the retrospective work and created a component that is linked to the collection. That means you can easily add new videos as they come or your own to the collection.

Duda Collections Are Powerful, But Why Don't We Make Them Look Better?

Tue, 15 Jul 2025 17:15:42 GMT

Right, cards on the table. I was late to the party with Duda collections. Really late. And you know why? Because I'm a bit of a design snob. There, I said it.

Don't get me wrong – I've seen some decent collection implementations. But most of the examples I came across were... functional. And functional is great! But I've always believed that functional and beautiful aren't mutually exclusive. We can have both, yeah?

Collections are incredibly powerful – they pull dynamic data, update automatically, and save hours of manual work. But for the longest time, I struggled to make them match the design standards I wanted for my sites. Maybe you've been there too?

When I started Agency Genius, the mission was simple: get more people using AI in their creative workflows. And yes, I said creative. Because AI is creative when the person behind the prompt gives it the right direction. But that's a discussion for another day.

What I want to share today is a workflow that's completely changed how I approach Duda collections. It's the perfect marriage of Duda's powerful data handling and AI's ability to create stunning designs.

I'm making a tool available to everyone – publicly, ungated, no login required. Use it to your heart's content. It's called the JS API Explorer, and when you combine it with Claude AI, something special happens.

Let me walk you through creating a "Meet the Team" component that'll make you proud to show it off.

First, map out what you want. For our team component, let's go with:

Pretty standard stuff, right? But here's where we can elevate it beyond the usual grid layout.

Head into Duda and create a new collection. Call it something sensible like "Team Members" (we've all been guilty of "test123" at some point, haven't we?).

Add some dummy data:

Add a few more team members, then publish the collection . This bit's crucial – if you don't publish it, the magic won't happen.

Now here's where it gets interesting. If you're a Pro member of AgencyGenius, you can request this as a Duda widget and just drag-and-drop it in. But if you're not (yet), you'll need to add the code directly... scroll down to find:

Once published, you'll see a little widget appear in the bottom left corner of your page.

This is the clever bit:

If you've published your collection properly, you'll see your data appear. Want the full JSON? Click "View Full Data" in the Raw JSON tab and copy the whole thing.

Head over to Claude (if you're an Agency Genius member with our custom instructions installed, this will work even better).

Start your prompt with something like:

Then add this crucial bit:

Hit enter and watch Claude create something beautiful.

Copy the code Claude gives you, paste it into an HTML widget on your Duda site, publish, and see your collection data transformed into something special.

Here's where I love to push things further. AI has seen thousands of design patterns and can combine them in ways we might not think of.

So here's your challenge: Once Claude gives you that first design, follow up with:

I guarantee you'll get at least one design that makes you think "Oh, I like that approach!"

Duda collections are powerful, and now they can be beautiful too. The combination of the JS API Explorer and Claude means you can create collection-powered components that look like they were custom-coded by a developer.

We've all built functional things that we wished looked better. Now we don't have to compromise. We can have both the power of dynamic data and designs that make us proud.

So let's raise the bar together. Let's make collections that make other Duda users ask "How did you do that?"

Now go create something amazing. And when someone asks how you did it, send them this blog.

Want to level up your Duda game even more? Join Agency Genius and get access to our custom Claude instructions, exclusive widgets, and a community of people who love pushing the boundaries of what's possible with Duda.

If you have the Duda Widget drag in the JS API Explorer widget

Click on the JS API Explorer widget
Hit "Discover Available APIs" – this initializes everything
Go to the "Collections" tab
Type in your collection name ("Team Members")
Click "Find"

Person's name
Their position
A professional headshot
A short bio about them

Name: Sarah Chen
Position: Creative Director
Image: Upload a headshot
Bio : "Sarah brings 15 years of experience in transforming brands..."

Alternatively, if you're not yet a Pro member:

Copy the 'Combined' tab
Paste it into an HTML widget on your Duda site

The Creative AI Revolution (Yes, I Said Creative)

The Free Tool That Changes Everything

Step 1: Plan Your Component

Step 2: Create Your Collection in Duda

Step 3: The JS API Explorer Magic

Step 4: Extract Your Collection Data

Step 5: The Claude Prompt That Makes Magic

Step 6: The "Wow" Moment

But Wait, There's More (The Creative Bit)

The Bottom Line

Duda Just Launched Their MCP - But What in the World Is an MCP (and Why Should I Care)?

wells.callum93@gmail.com (Callum Wells) — Wed, 09 Jul 2025 02:09:00 GMT

Duda Just Launched Their MCP — But What in the World Is an MCP (and Why Should I Care)?

OK, I’m going to overdo this a bit and explain it how I explain it to myself. Apologies if the tech comparisons I make don’t totally land for you — this is just how I think about it in my head. Hopefully it helps someone.

This is where things get powerful.

Let’s say Claude writes a blog post in Duda. Then you connect Zapier to your social scheduling tool. Now you can say:

“Claude, write a blog post about X and publish it. Then send it to LinkedIn via my scheduler.”

And it happens — across platforms , with no need to manually move content between tools.

Tools like Zapier , n8n , and others are building their own MCPs too. That means tools can talk to tools, and you don’t have to be the middleman anymore.

You might want to watch Corbin Brown’s Zapier MCP demo — even though it’s not specific to Duda, it shows exactly how this mindset works and where it’s heading.

The real shift is understanding that the new skillset isn’t clicking buttons — it’s asking the right things, in the right context, using the right tools .

First: how do you normally use a system?

You move your mouse. You click around. You do stuff manually. That’s your method of interacting with a system.

Then along comes something like Zapier, where you can say:

“When this thing happens, go and do that thing.”

And it just… happens. Without you doing it yourself.

Now, an MCP is kind of the same thing — just a different medium for talking to a system.

In Duda’s case, they’ve made parts of their platform available to outside tools via an MCP. That means external systems — like Claude or Gemini — can now do things inside Duda just by you asking for it in plain English. No more clicking around. Just:

“Do this thing for me” — and it does.

Think of the MCP like a framework — kind of like how Google uses schema or structured data to make sense of web content — but instead of indexing, it’s for tools (especially AI) to understand what’s possible and what’s available to act on.

Claude takes your input — typing, voice, whatever — and converts that into a request Duda can process, thanks to the MCP.

So what is Duda's MCP?

So what can it do right now? (July 2025 MVP)

Right now, there are 30 live actions available through Duda’s MCP.

In the DudaCon demo, there were 60+ — so it’s clearly growing.

These actions are basically the “verbs” Claude can use inside Duda. Things like:

List all your sites
Duplicate a page
Publish something
Read SEO metadata
Change text on a block

It’s important to build context by looking at the action list , so you understand what’s actually possible. Don’t ask it to do something it can’t do.

It’s the same as talking to Alexa:

“What’s on my calendar tomorrow?”

That works — because Alexa has access to your calendar.

Asking Alexa to iron your shirt? Not going to happen. That’s not a capability it has. Same thing here.

The really exciting bit: chaining across systems

And just a quick aside — if you’re still only using ChatGPT, now is the time to branch out.

Claude (by Anthropic) is a completely different model. Same category (LLM), but different approach, different logic, different outputs.

For example:

If you asked both Claude and ChatGPT to write the same blog post, the structure, tone, and depth would be noticeably different. Some people prefer Claude’s reasoning and cleanliness — I personally find it better for design-related logic and more natural flow.

Neither is universally better. They just think differently.

And then you’ve got others — Gemini, Mistral, DeepSeek, etc. It’s worth exploring.

Pro tip: when a tool says “AI-powered,” it usually just means it’s plugging into one of these models via API. The real smarts live in the models themselves.

Why Claude?

Because this is exactly how the future of work is going to function.

The people who can leverage AI tools, connect them via MCPs, and build cross-platform flows — they’re going to win.

The people who never look into this stuff? They’ll be left behind.

You don’t need to become a developer. You just need to learn how to:

Connect Claude (or your preferred model) to Duda’s MCP
Understand what’s available
Ask things in a useful, actionable way

Once you get the hang of it, it’s hard to go back.

So why does this matter?

Important thing to remember!

One thing worth keeping in mind — especially if you’re testing this around launch day — is that Claude isn’t Duda .

Duda’s MCP lets third-party tools like Claude interact with your account, but Claude is still a separate system, running on its own infrastructure, built by a different company (Anthropic). Anytime you use an external tool, you’re also inheriting its quirks, limitations, and potential downtime.

Coincidentally, on launch day, there was a spike in issues.

Not necessarily Duda’s fault. In fact, in many cases it’s the external tool — Claude, Zapier, or whatever else you’re using — that hits a rate limit, goes temporarily offline, or just gets a bit moody.

If something seems broken or slow, don’t immediately log a support ticket with Duda — they can’t fix Claude .

Instead, try the following first:

Check Claude’s status page
Visit DownDetector

And if it’s a bigger issue, just wait it out — AI tools are still evolving, and hiccups happen.