We have a subdomain for eg. https://qwert.abba.com which we have tagged with the same Adobe Launch Production Code as our main domain https://www.abba.com However I am unable to see the activity map working on my subdomain website https://qwert.abba.com
Do I need to add the subdomain here in the Internal URL Filter in Adobe Analytics because I don't want to miss any analytics activity happening on my subdomain? Though my domain and subdomain both use the same launch tag on web pages so activity map is working on the main domain it should be working on the subdomain as well, isn't it?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi there,
Yes, you're correct. The Adobe Analytics activity map should work on your subdomain if you're using the same Adobe Launch tag. But to ensure that traffic on the subdomain is not treated as referrals, you should indeed include the subdomain in the "Internal URL Filters".
The "Internal URL Filters" setting is used to designate which domains and subdomains are considered internal to your organization. By default, traffic between these domains is considered to be internal traffic, not referrals. If you do not include your subdomain in the "Internal URL Filters" list, visits moving from your main domain to the subdomain could be counted as a new visit and a referral from the main domain, which could skew your analytics.
So, in Adobe Analytics, navigate to the report suite settings, and under "General", add your subdomain to the "Internal URL Filters". After you have added this, it should start considering your subdomain as part of your main domain and the activity map should also work correctly.
Please note that these changes will not retroactively affect the historical data, they will only apply to data going forward.
I hope this helps! If you have further questions, don't hesitate to ask.
Hi there,
Yes, you're correct. The Adobe Analytics activity map should work on your subdomain if you're using the same Adobe Launch tag. But to ensure that traffic on the subdomain is not treated as referrals, you should indeed include the subdomain in the "Internal URL Filters".
The "Internal URL Filters" setting is used to designate which domains and subdomains are considered internal to your organization. By default, traffic between these domains is considered to be internal traffic, not referrals. If you do not include your subdomain in the "Internal URL Filters" list, visits moving from your main domain to the subdomain could be counted as a new visit and a referral from the main domain, which could skew your analytics.
So, in Adobe Analytics, navigate to the report suite settings, and under "General", add your subdomain to the "Internal URL Filters". After you have added this, it should start considering your subdomain as part of your main domain and the activity map should also work correctly.
Please note that these changes will not retroactively affect the historical data, they will only apply to data going forward.
I hope this helps! If you have further questions, don't hesitate to ask.
Just going to add this... if you already have ".abba.com" as an internal URL filter, you do not need to add "qwert.abba.com" as another value... it will be picked up by your main domain value....
Now, if you specifically added only "www.abba.com" as an internal url filter, then yes you will need to add it.... URL Filters work on "contains" logic... so it's much simpler to just use one .abba.com entry, then adding all subdomains individually.
Thanks @Jennifer_Dungan this is helpful however, after adding my subdomain to the Internal Filter URL in analytics my activity map started working.
@Jennifer_Dungan thanks, I was looking for this answer [URL Filters work on "contains" logic... ].
Views
Likes
Replies