Make wildcards possible in "Site or app address" field (*.example.com)

Hello together,

I have the problem that a clients website has thousands of subdomains, additionally some of them continuously changing. Thus, it is not possible to fill all of them into the configuration field “Site or app address”.

However, it would be great to be able to do this, because then referral handling could be more exact and make possible more detailed insights.

Thus, could you please make possible to also fill wildcards i.e. *.example.com into this configuration field?

Thanks!

1 Like

Hi @thomasgerstmann,

Sure, I will write a feature request for that. Also, if you disable below option in Administration => Data collection settings, every site where you place tracking container, the tracking requests will be sent.

1 Like

Hi @Adam,

thank you very much!

The option “Collect data only from known sites” was already configured like shown in your screenshot.

Best regards,
Thomas

Hi @Adam, are there already any updates on this topic? Kind regards, Thomas

Hi @thomasgerstmann,

Afaik no current updates regarding this new feature.

Best regards,
Adam

Hi Adam,

thanks for your fast reply!

The minor data referral data quality, because of this topic here, is regularly and recurringly an analytics/reporting problem for us.

The problem is, user movements between different subdomains (which are not being explicitly mentioned in this list) result in the start of new sessions. And thus, goal attribution is disturbed by such new sessions which should not happen. Such movements from one to another subdomain should - in our case - not start a new users session.

Thus: Do you have an estimation, when this will be implemented and available?