If chat loads a little delayed on websites so that it does not interfere with page load,will it affect the Lead numbers
Related
We are a digital media company. Lately for some of our clients whom we do dynamic display ads we have noticed a discrepancy in the tablet clicks and sessions.
I have analyzed our sessions, with our clicks and the clicks we get from adwords and there seems to be loads of discrepancy.
Can anyone help me in figuring why this could have happened? Could there be some issue in the url we are passing in the displays that have an issue on tablets.
I have seen this case many times and it varies greatly from client to client, campaign to campaign. See if there is some redirect of the campaign to another url, or if the bounce rate is too high, in line with the duration of the sessions, because if the user clicks on the ad and leaves the site quickly, the session is not counted.
Have you checked this guide?
https://support.google.com/analytics/answer/1034383?hl=en
I'm currently having some network issues, and my Wicket application does not react very nicely to the network being sluggish or down. I.e. I see no reaction in my webpage, not even the AjaxIndicator.
What would be the approach to tackle shaky networks in Wicket Ajax? And how to present this to the user in such a way that it is not annoyong (like pop-ups etc).
The application is responsible to show Ajax indicator when needed. E.g. you can show it always, or show it only after a delay of N ms [1].
You can also use the browser navigator's online/offline events to tell the user that her connection is down [2].
https://github.com/apache/isis/blob/587a8bd622c9511389b92102c4308f6dd0dfabab/core/viewer-wicket-ui/src/main/java/org/apache/isis/viewer/wicket/ui/pages/jquery.isis.wicket.viewer.js#L88-L96
https://developer.mozilla.org/en-US/docs/Online_and_offline_events
I am tracking several google analytics in my app and it recognized that it takes some time until they are shown in the GA Frontend.
Do you know if this is normal or if they are stuck somewhere?
Is there any possibility to debug this? The events are sent out successfully (HTTP 200).
It's completely normal for there to be a delay. It can be as long as 24-48 hours. The larger the amount of data that has to be processed for the profile the longer it takes, in my experience.
I recently implemented a small snippet of javascript in my Master page that does an ajax request every 30 seconds to keep session alive. I know there are several questions regarding keep alive but I haven't really been able to find answers to these specific questions.
My questions are:
Is it safe to do this? As in, will this have any adverse effects if there are many concurrent users/connections?
Can I implement an extended timeout using this method or will I have to use cookies?
I don't know much about cookies, but are these relatively acceptable to use now? or will there be users who don't allow them - will they be able to use my site?
Thanks everybody!
Yes it's safe. As far as load, that's up to your hardware and how you write it, but it has no worse effect than users refreshing the page (arguably less considering the overhead of an AJAX call over a standard page load).
You can adjust the timeout in the web.config if that's what you're asking...
That's a personal call on you. Cookies have their purpose, and I find them acceptable as long as it's your domain, but do realize some people disable them and so it comes down to having a fall-back.
Some things to keep in mind though:
Banks use the same methodology to keep your session going while you're checking your finances, but usually offer a popup just before to ask if you'd like to continue.
Keeping a user forcefully logged in for longer than a normal duration can be a security risk (picture someone logging in at a library or school computer and leaving their desk--should that session continue on in to the next day [or longer]?)
about the cookies, it is very acceptable to use.
almost all sites saving cookies on the users, they have to.
there are users that dont allow them but the proggramer can overcome it, by changing the security of the browser (There's a constitutional problem in this case).
you can see if the site saving cookie in your browser.
I have an incredibly simple application that simply fan gates and then offers a form to fill out (contest). I receive and parse the signed_request and display content based on the like_status. My average response time this week is 0.00495 on my index.php.
However, a number of page view requests NEVER reach me. A small percentage of users report seeing a white page. They do not see an error like a 404 or 501 etc., just a white page.
I can only find out about through disgruntled wall posts because I cannot calculate or diagnose requests that I never receive.
This has been happening MORE this week and it is causing immense issues with a client's contest. While I can offer the explanation that millions of people are hogging Facebook at certain times AND it's return to school week, it's not really helping.
So far an iframe app is like a black box and the wall is the only way to do customer care. If Facebook requests time out before reaching me then I may not be able to offer this service to clients even if it works for 99% of the time.
How have you dealt with these issues in the past because they affect ALL developers of iframe apps now that FBML has been deprecated.
Thanks.