I have used only Meta CAPIG so far, but my question applies to all CAPIGs and the Stape Gateway available in the Stape interface.
What I’ve learnt is that Meta CAPIG is built on top of existing pixel tracking (be it GTM or direct). My question is: how can I manage cross-domain tracking with CAPIGs?
I mean, CAPIGs also need subdomain creation and adding DNS records. But in the case of cross-domains, should I create two subdomains and add DNS records individually to each, and will it pick up? I mean, I will have the FB pixel on both domains and they will be tracked? I need to understand if the same CAPIG logic works for all the other tools GA4, Google Ads, etc. if we use those CAPIGs?
My question is: how can I manage cross-domain tracking with CAPIGs?
you can’t, that is beyond just running the same pixel on different domains.
But in the case of cross-domains, should I create two subdomains and add DNS records individually to each, and will it pick up? I mean, I will have the FB pixel on both domains and they will be tracked?
Gateways (Meta, TikTok, Snap) are tied to pixels, not domains. Therefore you will only be able to have one domain associated with a single pixel.
other tools GA4, Google Ads
Stape Gateway (GA4 and Google Ads) would be an exception, this one operates around domains, so you can have multiple and generate loaders (which will inform destination urls) for each seperate domain in question