Search traffic and Ringpools (3)
So what I've understood is that ringpools auto-populate your landing pages with tracking phone#s unique to each visitor.
Can someone possibly shed light on:
1)With Google's new policy we need to have the phone# (for both call-only and call-extension campaings) we used to setup the ad campaign matching the phone# on the landing page for verification. As a few guys have posted on here, if you use a specific amount of numbers you already know you can use php to display the unique numbers on your lp depending on the URL token. But if each phone# is unique with each visitor, it seems we can't use ringpools.
2) Pay per call search ads generally get most people to call before they ever visit the LP. Therefor are ringpools only for display traffic?
And for search traffic we should just use Twilio or something and assign 1 number per ad group. Limited data..but better than nothing..
Thanks 
)
Originally Posted by turqoise
Can someone possibly shed light on:
1)With Google's new policy we need to have the phone# (for both call-only and call-extension campaings) we used to setup the ad campaign matching the phone# on the landing page for verification. As a few guys have posted on here, if you use a specific amount of numbers you already know you can use php to display the unique numbers on your lp depending on the URL token. But if each phone# is unique with each visitor, it seems we can't use ringpools.
2) Pay per call search ads generally get most people to call before they ever visit the LP. Therefor are ringpools only for display traffic?
And for search traffic we should just use Twilio or something and assign 1 number per ad group. Limited data..but better than nothing..
Thanks
)1. Yes, the phone number on the landing page needs to match the phone number used in the extension. If the landing page is using dynamic number insertion, then you probably won't be able to get the ad approved.
2. If you're using call-only campaigns, then yes, you'll have the users clicking directly on the ad and generating a call. However, if you use desktop or tablet traffic you could send users to a landing page and have them call from there. So, in that case you could use RingPools.
Another option is to use Google's call tracking code for websites. So, you'd use their tracking numbers on your page. Might be a good option.
-Mike
Oyeah I totally forgot about verifying yourself with Google's tracking code instead of verifying with the phone# on the page. So Google would still approve the ads even if phone#'s didn't match on verification URL, just as long you have the tracking code on there?
But generally still, even if you do search ads with the call extension + 300% bid modifier + worse lp/adcopy for desktop then most of your traffic comes from mobile and goes straight to call instead of LP, making ringpools useless.
So best bet it seems with search traffic (both call-only and 300% modifier ones) is still to just assign 1 phone# per ad group and just use 1 lp (which also acts as the verification URL) for all ad groups and add the php code that displays the phone# dynamically depending on the URL token.
Home > Paid Traffic Sources > Pay Per Call