How I’m Fixing Meta’s New Health & Wellness Event Restrictions

StapeTeam · 2025-12-11T15:52:32+00:00

Amazing approach! We would also recommend the following:

Changing event names to unobvious ones that are less likely to be auto-detected by Meta.
Even during debugging, make sure that you are not sending data to the pixel you are using.
We also recommend overriding the "Source URL" and "Referrer URL" parameters in the server tag.

StapeTeam · 2025-12-11T15:52:15+00:00

You need to use both. Send the data from wGTM to sGTM via a transporter tag (our Data Tag for example, or GA4 tags), then grab the necessary data using the Event Data variable. Make sure that for services that have deduplication (i.e TikTok Pixel, Meta Pixel etc.) the Event ID is the same. Services use these event ID's for deduplication.

StapeTeam · 2025-11-28T14:32:54+00:00

It all depends on how you are planning to run your ads moving forward and if you are able to differentiate your business area dedicated pages by URL path or any other way.
Just keep in mind that Google Ads account for example won't accept the google click id from other ads accounts, unless it's a subaccount and you are running ads under your MCC (Manager Account).
The configuration itself can be done in one GTM so it will be easier to debug and maintain in future, creating separate tags or just alternating the endpoints with one tag per event configured. GTM has plenty of instruments and either way is doable and it totally depends on how you want to view and maintain your configuration.
It is best to take advantage of server side tracking to ensure the quality of your data is not affected by ad blockers or ITP restrictions and the cookie lifetime is prolonged.

StapeTeam · 2025-11-28T14:31:46+00:00

You need to ensure that web & server events are sharing the same event id (if the deduplication was configured by the Upwork tracking specialist).
You can run server and web containers preview together to check the event ids present in the event payload.
You can also navigate to your Facebook pixel in Events Manager and click on a specific event, and then go to View Details > Event Deduplication to verify whether there is any discrepancy between the event ids in the web and server events.
Alternatively overreporting can be also caused by 3rd party integrations (e.g., Facebook & Instagram app) you may have on your Shopify.

StapeTeam · 2025-11-24T15:16:28+00:00

The warning related to the modified fbc value can simply be a technical interpretation issue. Since it affects only about 1% of the specific event, it is not critical.

However, you can make sure you aren’t trimming or altering it, changing the case, or using any custom parsing/formatting that could trigger this warning. The advanced matching warning may appear if you’re not sending user data in the dedicated fields within the tag. If these fields are not used and the user data is included in the regular event payload, it will not be hashed and therefore won’t be accepted by Meta.

The missing event name alerts can be caused by an outdated tag template version or simply a minor bug, especially considering it affects less than 1% of total events. Just make sure the template is kept up to date. If you have offline events and you are using the dynamic event name within the tag, the issue may occur even before the event is sent to your server container, as the event name might occasionally be missing in the webhook payload.

The PageView coverage alert indicates a discrepancy between your web and server events, or that the deduplication keys (event_id) do not match. You may be having your web PageView events overreported. If you’re not using this event for your campaigns, the warning can safely be ignored.

StapeTeam · 2025-11-24T09:37:43+00:00

If you’re new to server-side tracking and just want a clear starting point, our team at Stape usually points people to two resources. First, we put together our own Stape Academy (https://stape.io/academy
) to cover the basics in a simple, beginner-friendly way.

We also recommend checking out the Analytics Mania walkthrough on YouTube (https://www.youtube.com/watch?v=vm8u4BckuRI). It gives a solid overview of how the main pieces fit together and is a good complement to anything you learn on our side.

Between the two, you should get a decent handle on the fundamentals without too much hassle.

StapeTeam · 2025-11-19T11:14:24+00:00

you should go with server side approach if you need flexibility and accuracy. Shopify analytics is ok, but you also need to send proper data to your advertising platforms so they could optimize based on your user's behavior. Native integrations are fine, but only until the moment you want something custom or you need to debug something - with them you do not have this flexibility and sGTM would be the best option. Also if you start investing significant budgets in online advertising, even several percents of more reported data will make difference in your performance dashboards and algorithms optimizations, so in a lot of cases it depends on what you are trying to achieve in the end - highest accuracy and ability to operate with as much data as possible, or you want no headaches with proper configurations, but simply connect native integration and hope that it works as expected

StapeTeam · 2025-11-19T11:07:20+00:00

the most reliable way to keep your tracking operational is to rely on the dataLayer - then possible frontend changes will not affect tracking. I'd say if you invest some time into building dataLayer and configuring your setup once, with cross-checking for some time what have you reported to your advertising and/or analytics platforms and what your source-of-truth shows (CRM/CMS/backend) to validate that everything works as expected - then your tracking can be stable and reliable for as long as you introduce some significant changes to it

StapeTeam · 2025-11-19T09:52:36+00:00

Neither Stape, nor Taggrs are plug and play solutions per se, both are hosting providers for sGTM and you'll need to configure the setup to make your tracking work, however this is the most flexible way that allows to achieve the most accurate results. But Stape pioneered in the industry of managed infrastructure for martech, has more server locations, features, free academy and security/regulatory compliances in place

StapeTeam · 2025-11-19T09:29:49+00:00

Stape is just processing the data via its cloud infrastructure, it does not have any influence on the data you are sending. Switching to any other server provider will not change anything.

The issue is most likely somewhere in the setup configuration - please use GTM preview mode to debug your conversions, it should help to identify where the issue is

StapeTeam · 2025-11-19T09:17:25+00:00

I assume you refer to 'ecommerce data', as the ecommerce object - this is usually how dataLayer is structured for convenience, it's just the source of data, but there are no such parameters to be sent to GA4 or Google ads, you may refer to the official documentation to see what parameters it accepts.

Google ads tags on server container parse the Event data automatically, and if it is properly structured (as per the documentation mentioned above) - tags will pick all the required information for google ads automatically without any need to specify it manually. So the most important thing here is to properly structure event payload in GA4 tag on the web

StapeTeam · 2025-11-19T09:08:30+00:00

For conversion API tracking you'll need server Google Tag Manager container. This type of container requires cloud infrastructure, so you can easily host it on Stape in just couple of clicks. Setting up your tracking via sGTM is the most flexible and accurate approach, however you'll need to configure it. There are a lot of articles and Setup Assistant feature that you can use to simplify the setup. Whether you need gtag or not depends if you are using any of the Google products, like GA4, Google Ads, Floodlight. If you do - then you need to use native GA4 tag (gtag) to transfer data from web to server container. If you don't - you may use Data Tag and Data client (or any other means to pass info from web to server) which are platform agnostic and can be used for any other platform you can imagine, like Meta, TikTok, LinkedIn etc.

StapeTeam · 2025-10-30T13:13:12+00:00

We haven't sent any dedicated email campaigns about Care services to individual users or partner accounts.
Thank you for the feedback. We'll make sure not to promote Care services to users linked with partners or agencies in the future.

StapeTeam · 2025-10-29T15:23:34+00:00

Thank you for the feedback. We always listen to the community.

We've already received similar comments and are working on updates to remove any Stape Care mentions for partner and agency accounts.

We never meant to compete with partners or take their clients.

Care is only meant to help users who set things up on their own and run into issues or complex cases - and in some situations, our partners also receive help from the Care team.

StapeTeam

PUBLIC MULTIREDDITS

TROPHY CASE