Hi,
We have an issue about sending adobe analytics request.
Most of data are send correctly in our project when page load, thus I'm sure that our code is right.
But there are a few cases where data (all data has the same format) cannot be received when page load, think it's not due to network issue since our page loads normally.
Could you please help me about this? Is there any reason for this issue?
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
ok so in the case of SPA.
Your dev needs to ensure that from (virtual page to virtual page) or route change he fires the correct page load event. Likely step 2 is missing it or just not firing it.
I`m guessing the other events you do see are link click events for example...
Ask you dev did you build it so a custom event for page load was defined or did you use a direct call rule? Custom events for page loads are tricky as in the case of SPA events may not trigger as expected when users navigate. I definitely recommend direct call rules for SPA vs custom page load events.
Views
Replies
Total Likes
For those cases where the data (e.g. eVars) are not sent:
Views
Replies
Total Likes
Hi, thanks for reply.
1. Yes. Since most data can be received correctly.
2. Yes. We push the data to datalayer after page loading, and it always success.
3. No. There's no error in the console, print datalayer in console, no issue.
4. We don't use Launch to manage tags.
Thanks
Views
Replies
Total Likes
Can you share your website?
Views
Replies
Total Likes
Sorry. It's an website for internal use. I'm not allowed to share it.
Views
Replies
Total Likes
Are you using a single page APP?
What type of server environment?
Are you using any akamei or caching on your site?
In network console type:
/b/ss/
do you get multiple adobe beacons for Adobe metrics on this odd page load?
Views
Replies
Total Likes
Thanks for your reply.
Yes, our project is a single page React App.
In the development env, we can't found /b/ss/ request for page loading, but works well for other events.
In the prod env, both page loading and other events works well, and we use single adobe beacons.
Now the issue is, in the prod, there're few cases lost some page loading data.
eg. we have data for page1, page3, page4 and so on, but don't have data for page2. And it is not possible to skip page in our project.
Thanks!
Views
Replies
Total Likes
At page 2, are you saying that:
Views
Replies
Total Likes
Will confirm with data team after Christmas holidays and reply at here ASAP.
Thanks for your help!
Views
Replies
Total Likes
ok so in the case of SPA.
Your dev needs to ensure that from (virtual page to virtual page) or route change he fires the correct page load event. Likely step 2 is missing it or just not firing it.
I`m guessing the other events you do see are link click events for example...
Ask you dev did you build it so a custom event for page load was defined or did you use a direct call rule? Custom events for page loads are tricky as in the case of SPA events may not trigger as expected when users navigate. I definitely recommend direct call rules for SPA vs custom page load events.
Views
Replies
Total Likes
Thanks!
Yep, the other events are triggered by button clicking, the page loading is triggered in useEffect hooks in React.
I'll dive into the direct call rules for SPA, I'm new at here.
Thanks for your help!
Just an extra FYI.
In direct call rules.. Some SPA may experience a first page load double fire.
If you implement Direct call rules well you can also get a huge benefit from automatic link tracking. many html links, buttons will automatically be tagged for click usage under Activity map.(no spec events needed, out of box)
Views
Replies
Total Likes
Views
Likes
Replies