Google's New Policy for Call Extensions (15)
This is going to cause a logistical nightmare for me...
Dear AdWords Advertiser,
Beginning June 2nd, 2015, we'll be updating the AdWords advertising policy for ads with phone numbers. To continue showing phone numbers with your ads after this change, you'll need to verify that the phone numbers you include with your ads belong to the business featured in the same ad.
Verify your phone numbers
Your AdWords account contains at least one call extension and one location extension with an unverified phone number. Starting June 2nd, 2015, call and location extensions with unverified phone numbers will be disapproved. You can verify your phone numbers using one of these three methods:
1Ensure the phone number used in your extension appears in text on the website featured in your ad.
2.Link your Google Webmaster Tools and AdWords accounts.
3.Add your unique AdWords conversion tracking code snippet to the landing page featured in your ad.
Next steps
To confirm which numbers require verification, go to the "Call extensions" or "Location extensions" view of the Ad extensions tab. Phone numbers requiring verification will appear with an "unverified" or "unverified phone" notation, respectively.
Why would this be difficult if you are running your own landers?
Though I can see it being a problem for people still using someone else's sites for QS.
Because I use the same lander for multiple campaigns and ad groups, that have different phone numbers for call extensions. You can't track calls by KW, so I created campaigns that allow me to do that. However, now I am going to have to have every phone number used by a landing page, listed on that landing page.
Ah ok... well why not just pass the phone number as a url variable so you can display it on the lander? That would be a pretty quick edit.
It's my understanding you can create a subpage that mirrors your landing page or homepage with the number that matches the ad, since it's a call only no traffic is going to go there, it's literally just for verification.
I drive users directly from my search ad to the phone call, so they aren't hitting the lander first. Otherwise, that would work!
Originally Posted by hypertargeteric
Originally Posted by tbranley
-> http://adwords.blogspot.nl/2014/08/i...nversions.html
Originally Posted by mikeyboy
For many of my campaigns, user goes from Ad > Phone Call.
More details on the new policy:
https://support.google.com/adwords/a...=notifications
If you use the same lander just pass the number as variable to and display it dynamically.
domain.com/?utm_source=goog&campaign=empire-roofing&kw=[keyword]&pn=888-555-5555
<?php
$callNumb = $_GET['pn'];
?>
Print in on the page now.
<div><?php echo $callNumb;?></div>
You could even split the numbers in 3 sections or whatever.
Its not that bad. At least they didnt forbid marketers from running call ads for others. They very well could and cut the middle men. Which wouldnt be a surprise when it comes to big god G.
Google and Yelp and these big shots is the new mafia of the century . Can you belive what Al Capone would be today if he owned Yelp?
Google didn't like Twilio for phone# verification though am I right? Also, if you're cloaking for compliancy, you've got to setup the compliant website yourself to include the phone# now..
What will you guys recommend using for verifying phone#'s now? Cause VoIP doesn't generally seem to work.. quite messy to scale with SIM cards..
Pain2k's solution is real nice as well.
Home > Paid Traffic Sources > Pay Per Call