It's a violation of the Google Adsense TOS to refresh the page several times because I have to try out changes on it?
https://support.google.com/adsense/answer/48182?hl=en
Clicks on Google ads must result from genuine user interest. Any
method that artificially generates clicks or impressions on your
Google ads is strictly prohibited. These prohibited methods include,
but are not limited to, repeated manual clicks or impressions,
automated click and impression generating tools and the use of robots
or deceptive software. Please note that clicking your own ads for any
reason is prohibited.
Can't you turn off Adsense while you are testing changes? Or at least turn them off in your development enviroment.
Or, you could add a rule not to show them when your ip visits the site.
Related
my website is http://howtolinuxs.com/ and connected with Blogger with good traffic. I applied for adsense application. but every time I received an email from google adsense that.
It’s important for sites displaying Google ads to offer significant value to the user. As a publisher, you must provide unique and relevant content that gives users a reason to visit your site first.
Don’t place ads on auto-generated pages or pages with little to no original content.
Your site should also provide a good user experience through clear navigation and organization. Users should be able to easily click through your pages and find the information they’re seeking.
I only want to know that:
what the problem is and how I can fix this.
PLEASE REPLY ME AS SOON AS.
Thanks in advance
Try to apply for Adsense through Earning Tab from Blogger.
After visiting Zalando.com and viewing a few products, I am often presented with retargetting Flash ads through Google AdSense showing those very same products. Clicking on one of those products will take me to the Zalando product page for that product.
The tracking behind this does not really interest me, but having multiple links in the ad does, as my employer has asked me about creating a banner with 3 similar products or categories so the user can simply click through to the product/category of their choice, rather than a single landing page.
Now, afaict from the image ads policy, in particular the section about clicktags and animated image ads, this does not seem to be possible, as it seems this requires changing the destination URL in the clicktag.
Are Zalando (and others) doing something in violation of the policy, both by tracking the user behaviour (and loading external content) as well as by having different URLs or am I missing something?
Can I create the banner my employer asks, without violating AdSense policy?
I'm trying to submitting built-in like action.
First time, I used a button on my site labeled with 'like' and without any logo and linked it to the action, but I've got the following feedback:
Your Like or Recommend button branding conflicts with Section 5.6 of
the Facebook Terms and Section I.8 of the Platform Policy
(https://developers.facebook.com/docs/guides/policy/examples_and_explanations/branding/).
Please resubmit with a different graphic that reflects your own
branding and the ux of your site.
Then I change the button text to 'Useful?', but I've go the following feedback:
Your action conflicts with section IV.3 of the Platform Policies
(https://developers.facebook.com/policy/). You must make it clear to
the user that you will be publishing a story to facebook and get their
permission before actually publishing the story. Additionally, your
action must not be confusing or misleading and should accurately
represent the action the user took within your app.
This confusing, I'm not sure what the problem is, please help :)
Thank you in advance.
It's all explained near the bottom of the the Facebook branding page. On your first attempt you used 'like' and that is not allowed on your custom button. The second time you used 'Useful?' and that is not clear enough and is confusing.
I suggest you read the branding policy examples and the other material.
Section 5.6 of the Facebook Terms
You will not use our copyrights or trademarks (including Facebook, the Facebook and F Logos, FB, Face, Poke, Book and Wall), or any confusingly similar marks, except as expressly permitted by our Brand Usage Guidelines or with our prior written permission.
Section I.8 of the Platform Policy
You must not use or make derivative use of Facebook icons, or use terms for Facebook features and functionality, if such use could confuse users into thinking that the reference is to Facebook features or functionality.
Section IV.3
If a user grants you a publishing permission, actions you take on the user's behalf must be expected by the user and consistent with the user's actions within your app.
I have a question about increasing visibility of Facebook app notifications.
As far as I can tell, there are only 2 places where Facebook app requests appear for users who don't click the "Apps & Games" section - in the top right section (https://skitch.com/nicksoman/8172w/facebook) or in the jewel (https://skitch.com/nicksoman/81737/2-facebook) - I believe the wording is a bit different on this one if recipients haven't used the app, as it references an invite rather than a request.
As other have noted, neither of these channels provides any context around the request. In the past I've seen context for apps like BranchOut and FarmVille, but I can't replicate this behavior by sending invites from these apps now (can anyone)?
Has anyone found a Facebook-approved way to either provide more context around these app requests or make them more visible?
I'm familiar with the history of Facebook tweaking channels due to abusive apps - just want to make sure I'm current on best practices today.
Are you referring to users who haven't authorized your app or users who did?
Basically, facebook calls this Social Channels and you have a few options, again, depending on if the user is already using your app or not.
If the user is using your app, you have the bookmarks bar which can be used by issuing a App-generated requests.
If the user isn't using your app then a friend of his that is using your app can send him a User-generated request.
You can and should encourage your users to publish your app stories to their friends' feed and/or to send them to friends.
There's that "Automatic Channels" which is discussed in the first link in this answer.
More options are to use the Social Plugins in your website, and to have a mobile version of your app.
I know about test accounts, but during beta I'd like to allow access only to my friends, and then later friends-of-friends, and then only eventually Kevin Bacon and his friends.
That would probably suck, wouldn't it? The app would be listed (is there a way to prevent listing?) and someone I don't know might try it and get a "sorry, this is in development message." I imagine they'd be irritated and not come back.
From what I've read, only a few apps take off, but when they take off, they REALLY take off. Do developers just release these things fully baked?
Anyone start out with OpenSocial or other smaller-than-Facebook networks?
Any ideas for a soft, gradual, restricted roll-out?
Once you've set up your application, there is a setting in the Developer application control panel for your app: Your app -> Advanced -> Sandbox Mode.
Sandbox mode lets you restrict access to only those people listed as developers (under the Basic section).
In terms of expanding the app, Facebook doesn't provide much more flexibility that the Sandbox mode. Unfortunately, adding everyone as Developers of the app doesn't work very well for a beta, as people can access the application control panel once they are a developer. I ended up putting a whitelist of Facebook Ids into the front controller of my application for a previous beta, and it worked fairly well.
The apps are only listed in the App Directory if you submit them and they are accepted. There's no issue about preventing listing, it's something you have to apply for.
As for restricting users, you can accomplish it with a script in the application that checks whether the currently logged-in user is within your restricted user set. For example, if you only want friends of yourself, check whether the current user is friends with your user id. If not, simply display an error/message page or redirect them to the Facebook home page (or wherever). Add this check to the rest of the start-up logic run each page (such as connecting to your DB and authenticating with Facebook).
What I have done in some cases is keep a database table with the user id's of users who are allowed access, essentially a "whitelist". If the user isn't in the table, redirect them.