u/WillyDoesntMiss

Hi everyone,

I'm working on setting up Enhanced Conversions for Google Ads using a GTM Server-side container (Stape) and I'm running into an interesting issue that I can't figure out.

My Setup:

- Multiple domains (.es, .de, .uk, etc.) - each with its own GTM Web container

- 1 shared GTM Server-side container (Stape with first-party domains)

- Each domain has its own GA4 property

- All properties have "Allow user-provided data capabilities" enabled with:

- Automatically detect: Email, Phone, Name and address

- CSS selectors configured:

- Email: `.modal_msg_texto > strong:nth-child(1)` (captures from confirmation modal)

- Phone: `input[name="telefono"]`

The Problem:

- Spain (.es) is successfully sending BOTH email and phone number to Google Ads

- Other domains (Germany, UK, etc.) are sending NEITHER

When I check with Tag Assistant on Spain, I see:

ep.user_data.email: user@example.com ep.user_data.phone_number.0: +34123456789

On Germany and other domains: nothing.

**What's Identical Across All Domains:**

- Same form HTML structure (`<input name="email">` and `<input name="telefono">`)

- Same GTM Web container setup (tags, triggers, variables)

- Same GTM Server container (shared by all)

- Same GA4 configuration for "Allow user-provided data"

**My Theory:**

The email CSS selector points to the confirmation modal (`.modal_msg_texto > strong:nth-child(1)`) which appears AFTER form submission. The phone number is NOT visible in the modal, only in the form input (which is still in the DOM but hidden under the modal overlay).

Questions:

1. Why would GA4's "Automatically detect" work for phone numbers in Spain but not in other domains, when the configuration is identical?

2. Should I configure hashing in GTM Server, or does GA4 handle that automatically when linked to Google Ads?

3. For Enhanced Conversions with GTM Server-side, is it better to use "Google tag" method or GTM method in Google Ads settings?

Additional Context:

- I just updated the CSS selector for email on the other domains to match Spain's configuration (pointing to the modal instead of the input field)

- Configuration was saved 24-48 hours ago but hasn't propagated yet

- Spain's configuration was done weeks/months ago and works perfectly

Any insights would be greatly appreciated! Has anyone experienced similar issues with GA4's automatic detection in server-side GTM setups?

Thanks!

Hi everyone,

I’d like to ask for advice on the best workflow for the following use case.

We want to use the WhatsApp Cloud API to collect customer reviews, either for Google Reviews or Trustpilot.

The challenge is that we would like to "make sure" the customer understands we are asking for a positive public review only if they had a genuinely good experience. My initial idea was to use a WhatsApp Flow that first asks whether their experience was positive or negative. If the experience was positive, the flow would automatically send a message the Google Review link, for example. If the experience was negative, we could collect their feedback internally and follow up with them.

However, I’m not sure if this is the best approach, especially because I assume most users won’t want to write their feedback twice: once inside the WhatsApp Flow and then again on Google or Trustpilot.

Has anyone implemented something similar? What would be the cleanest and most compliant workflow for this?

Any suggestions or examples would be very welcome.

Thanks in advance!

Hi everyone,

I’d like to get some feedback on my current setup and understand what limitations I might face as it grows.

I’ve been using Lovable to build a marketing dashboard where I integrated the WhatsApp Cloud API. So far, I’ve created pages for campaigns, contacts, templates synced with Meta, analytics, and settings — including the ability to create team members for managing conversations.

So far, everything is working well:

Campaigns are being sent correctly
WhatsApp messages are being received
Templates sync properly with Meta
The analytics page is tracking message statuses correctly
When I use WhatsApp Flows, I store the responses using the Flow ID

At the moment, my campaigns are being sent to around 40–60 people at a time. However, the goal is to eventually get closer to my daily messaging limit of around 2,000 contacts.

My main concern is scalability. I’m not sure how far this setup can go before I start running into issues with Lovable, the WhatsApp Cloud API, database structure, rate limits, webhooks, analytics accuracy, or general performance.

Has anyone here built something similar with Lovable and WhatsApp Cloud API?

What limitations did you run into?

Do you think this kind of setup can realistically scale to around 2,000 WhatsApp messages per day, or should I start thinking about a more custom backend before reaching that point?

Any advice, warnings, or best practices would be really appreciated.

Thanks!

Hi everyone,

I’d like to get some feedback on my current setup and understand what limitations I might face as it grows.

I’ve been using Lovable to build a marketing dashboard where I integrated the WhatsApp Cloud API. So far, I’ve created pages for campaigns, contacts, templates synced with Meta, analytics, and settings — including the ability to create team members for managing conversations.

So far, everything is working well:

Campaigns are being sent correctly
WhatsApp messages are being received
Templates sync properly with Meta
The analytics page is tracking message statuses correctly
When I use WhatsApp Flows, I store the responses using the Flow ID

At the moment, my campaigns are being sent to around 40–60 people at a time. However, the goal is to eventually get closer to my daily messaging limit of around 2,000 contacts.

My main concern is scalability. I’m not sure how far this setup can go before I start running into issues with Lovable, the WhatsApp Cloud API, database structure, rate limits, webhooks, analytics accuracy, or general performance.

Has anyone here built something similar with Lovable and WhatsApp Cloud API?

What limitations did you run into?

Do you think this kind of setup can realistically scale to around 2,000 WhatsApp messages per day, or should I start thinking about a more custom backend before reaching that point?

Any advice, warnings, or best practices would be really appreciated.

Thanks!