Hi,
Recently I have implemented a new property using the Web SDK. It isn't the first Web SDK property I have implemented for the site, so mainly I have copied the work I did before for other properties.
For my last implementation, I can see that eventhough the default 'Page' dimension is set correctly on Adobe Data Collection I can't see the dimension being sent on the Edge server call and when checking on Adobe Analytics Workspace I can see it gets populated with the value 'Other'. It didn't happened with previous implementations.
My last implementation sets on a different domain, which differs from the previous ones, but both share the same Adobe Analytics report suite. I haven't added yet the new domain on the internal URL's filter section and I think the issue might be related to it according to the information I have read on this page.
Can you confirm if the issue is related to not have added the new domain to the internal URL´s filters as I suspect?
Thanks.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @RaulFo
you're right, it's the missing filter. This is something that keeps your report suite data clean e.g., if someone else unintentionally sends data to your analytics solution.
had a similar issue with a client a while back when someone implemented the Bulk Data Insertion API and set the domain to something completely different.
the "Other" was our way to finally finding out the root cause of our issue.
set the filter and you will be fine.
skip any subdomain and www. though.
mydomain.com instead of www.mydomain.com or subdomain.mydomain.com
Views
Replies
Total Likes
Hi @RaulFo
you're right, it's the missing filter. This is something that keeps your report suite data clean e.g., if someone else unintentionally sends data to your analytics solution.
had a similar issue with a client a while back when someone implemented the Bulk Data Insertion API and set the domain to something completely different.
the "Other" was our way to finally finding out the root cause of our issue.
set the filter and you will be fine.
skip any subdomain and www. though.
mydomain.com instead of www.mydomain.com or subdomain.mydomain.com
Views
Replies
Total Likes
Hi @bjoern__koth ,
Sorry for coming back to this topic, but we put on hold this change related to the internal domain and when we've done it the Page dimension has been populated with the page url value.
This is what must be happening now according to the official documentation:
As said on this ticket, it isn't the first Web SDK property I have implemented. The default Page dimension is set correctly on Adobe Data Collection but I still can't see the dimension being sent on the Edge server call. Is it a matter of time to get the dimension correctly set on the server call and populated in Analytics?
Thanks.
Views
Replies
Total Likes
Hi @bjoern__koth,
Can I have an answer from you or any from the community or would it be better to open a new ticket?
Thanks.
Views
Replies
Total Likes
Hi @RaulFo
in the classic AppMeasurement if you don't populate the s.pageName it uses the URL.
WebSDK behaves the same way if you don't set the fields accordingly
https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/page-vars/pagename
Views
Replies
Total Likes
Hi @bjoern__koth,
The page name dimension has been set up in the web SDK implementation using the schema:
I can see the server, site section and other custom dimensions like the page name (mapped to an eVar) populated in Analytics but not the required Page dimension. I thought it would be entirely related to the internal url filter change, but as mentioned above I can't see the dimension being sent on the Edge server call and so the Page dimension has been populated with the page url value.
I still can't identify what is wrong.
Thanks.
Views
Replies
Total Likes
Can you send a screenshot of the expanded pageViews object please?
Views
Replies
Total Likes
Hi,
Do you mean the schema object?
The value number is 1.
Thanks.
Views
Replies
Total Likes
In that case it shall be populated as well. Do you have any prod URL where this could be looked at?
Views
Replies
Total Likes
Hi,
I'd prefer not to share the client's url as this chat is public.
Maybe it would be better to create a private ticket with the Adobe support?
Thanks.
Views
Replies
Total Likes
Understood. You can share it in a DM instead or open a ticket
Views
Replies
Total Likes
Views
Likes
Replies