i have a main page where i have a service, the user can enter a text and the text is processed to have to user a response.
I can do it by two ways, reloading the page with http post method in a form or with ajax(laravel livewire) to no reload the page.
The question is, i have google adsense in this page, is better to reload the page in every user request when the user send the form to serve more ads or is better proccess with ajax the form and not reload the ads.
With ajax:
The user enter in page and send the form, only i print 1 time the ad, if the user send 5 times the form, only i showed 1 ad.
With http form request:
The user enter in page and if the user send the form, the page is reloaded because the user send by POST method the form, if the user send the request 5 times, the ad is showed 5 times.
I don't know if the CPC will go down because many impressions are made in the event that the page is reloaded when the user submits the form.
¿What do you think that is better to get the best earnings?
Reloading a page on Google AdSense can cause the ad units on that page to refresh, potentially resulting in new ads being displayed. However, reloading a page too frequently can negatively impact the user experience and may result in lower ad revenue.
It is generally not recommended to reload pages on Google AdSense too frequently, as it can lead to lower ad revenue and increased bounce rates. If you want to refresh the ads, you can use the async feature of Adsense which will refresh the ads without reloading the entire page.
Additionally, Google AdSense has a policy against automatically refreshing pages in order to increase ad impressions. This is considered to be a violation of their policies and can result in your account being terminated.
It is better to avoid reloading Adsense pages unless it's really necessary, and if you really have to do it, make sure you are doing it in a way that is not against Adsense policies.
Related
Let us say the user is on the Settings page but goes away from the keyboard for a while.
Technically the user is not authenticated but is able to "surf" his/her settings page until the user hits a page where some new data from the server is requested.
Currently, I just catch the "Unauthenticated" response and reload the page so the user gets to /login.
I'm using Laravel, but the setting page is based on Vue + Vue router. The setting is thus a single page but acts as it has many.
So how do you handle this kind of situation? Are you checking the authentication status like every 1 minute?
In my application we have a summary page having a link to take the user to the different pages of the application. For example, we have separate pages for collecting personal details, address details, education details etc., and there is a summary page giving the summary of a student's data. Users of the application will go to the summary page and then navigate to any individual pages in case if the data is not filled up yet. After the user goes to the individual page, they can enter the required details, and upon saving the entered details, they will be eventually redirected back to the summary page.
I have implemented the above functionality as below at the moment,
When the user clicks on a link to the address details page from the summary page, I will pass the redirect url as a query string to the summary page, and upon the user saves the address details in the address page, I will redirect the user back to the summary page using the redirect url passed on the query string.
Each individual pages have a common base class
Redirection logic is present in each individual pages now. This logic checks if there was a redirection url present in the query string, then if present it will direct the user to the summary page after the user clicks on the save button on the current page.
I feel the above solution is elementary, there is potential for adding new pages to our application.
I wonder if there is anyway to implement the above requirement in a elegant way in such a way that the redirection logic is separated as a angular service, route or any other angular technique so that we dont have to do any thing extra for the new pages that will be added in the future.
I have an application in which I am displaying dynamic advertisements. There are some ads displayed on pages without logging in, and others on pages that you have to log in to access them.
First, I want to be able to track how many clicks have been made on a given ad accessible anonymously.
I added this code to the onclick event of the ad
onclick="ga('set', 'dimension1', '#item.Id')" // #item.Id is the Id of the Ad
I can see that the event is triggered in the GA Debugger in Chrome, but I cannot see the result in GA even after 24h.
Second, I want to be able to track the Ids of the users who have clicked on the a given ad. And I don't know if this can be done using GA.
An ideas ?
Custom Dimensions and Metrics are necessarily connected to an interaction and cannot be sent on their own - they must always be followed by an interaction hit (pageview, event, transaction etc).
I am trying to load up http://developers.facebook.com/apps page but i always get redirected to my 'adverts & pages' page. I cant add the Developer app either as i get redirected also to the same page. Im simply trying to register my website as an app. I need to set a fb:app_id value for our Like buttons
I have a recorded mobile number & credit card so our page should be verified
Any thoughts ?.
You are currently logged in as a page account and not a real user account. Only user accounts can create facebook apps.
We're creating a website where we will be giving out code snippets to our users which they can place on their own websites. These snippets contain a link a javascript include. When clicking the link, an iframe containing the login dialog to our site opens. The user then authenticates inside the iframe, does his work and when he leaves the iframe his session is closed. We've got it working allready and it's very slick.
Our main concern though is phishing. The user has absolutely now way of veryifying where the login page is really coming from. On the other hand, phising attacks are also succesfull even if the user can see the fake-url in the address bar.
Would you enter your (OpenId) credentials in an iframe? Does anyone know a pattern with which we could minimise the chances of a phishing attack?
The user has absolutely now way of veryifying where the login page is really coming from.
There are ways around that, by having the user choose a secret that the real login page can display back at them to identify itself. Usually this is done with easily-identifiable pictures.
However that is not the only issue. If you allow your login page to be framed (and the user comes to expect that), you also open yourself to clickjacking attacks. The third-party site can frame your login page, then position: absolute their own HTML elements on top of it. Elements like inputs directly on top of yours, sniffing each keypress to nab the password.
You can allow a simple “start login process” button to be framed, and maybe a username/identifier, but the form into which a password should be typed must open in its own browser window (either in the main window or in a popup) with its own address bar and SSL indicator.
Would you enter your (OpenId) credentials in an iframe?
Goodness no.
I would recommend not using an IFrame as they defeat accessibility, seo, and semantics unless you want those defeated. If you are asking people to login via an IFrame then you have a definite accessibility barrier that may be considered legally discriminatory in certain countries.