Thanks Janet. I know how to add code to the header and footer though, which I typically do through the Theme editor. I already have several Google tracking scripts that I have added. In fact, I have already added the code for the _googWcmGet function which is the first step in making the forwarding numbers work.
But in this case, Google is telling me to take an additional step and add code to the body of the page, and create this “onload” event. I don’t see any Body tags anywhere…just a bunch of PHP.
I don’t think it would work to add this code to the header. Or am I wrong?
The Google instructions are here: https://support.google.com/adwords/answer/1722054?hl=en
Navigate to “Track calls from a web site” / “Step 2: Paste the code into your website’s HTML”
Did you get this figured out? I have to do the same thing.
make a specific php file for that page
For Page: page-[slugname].php
For Post: single-[slugname].php
For Category: category-[categoryname].php
… or stick this where you want that number to appear.
<?php if ( is_page('page-name') ) { ?>
...
<?php } else {} ?>
Change ‘page-name’ to your page slug, and you’re good to go.
dauidus, thanks but I’m not sure you fully understand what I want to do. I also want to insert a bit of code in the body tag itself for specific pages, like so…
<body onload=”_googWcmGet(‘number’, ‘1-800-123-4567’)”>
Thanks Jordydme for chiming in! Dauidus and rolabrazaldo, thanks as well. Rola, I assume by “specific php file”, you are saying create a new template, then build the page with this new template, and that this template could have a body tag in it. Correct? I don’t see any body tags in any of the existing php files. Should I copy one, like page.php, and then simply add a body tag at the end?
There’s got to be an easier way than that.
I agree, but I would build a new php file if that would do the trick, because that is quite easy to do, as long as you have ftp access to the files…you just duplicate an existing one and give a new name…then it shows up in your theme editor in WP. And then you can just choose it as your template while you build your page in WP.
The trick is, how to build that php file to contain the body tag and the body onload instruction?
We’re trying to figure out this exact thing as well. Google’s a bit sloppy with this program as the script they want you to insert between the head tags lacks the surrounding script tags….something they acknowledged over the phone with us after we brought it up. Anyway, I think the solution might be to just to copy the header file (if you’re using a Master/Child theme setup) into your child theme’s directory and add the onload code to it.
Many times the <body> tag is in the theme’s header.php file. It sounds like you already edited that file and know where it is. I would do a ctrl+f to find body. Often, the body tag includes PHP already. It could look like this:
<body <?php body_class(); ?>>
In that event, just add the onload before or after the PHP:
<body <?php body_class(); ?> onload=”_googWcmGet(‘number’, ‘1-800-123-4567’)”>
Hope that helps 🙂
P.S. I just added that same call conversion code to my site yesterday and have not gotten it to work. I tested it with a test function and the onload did work:
<script>
function testFunction(){alert(“This Works”);}
</script>
<body <?php body_class(); ?> onload=”testFunction()”>
This leads me to believe I either have to wait a few more days to see this Google code working or something else is going wrong. Good luck to you all
We got the code to work eventually…but it was a process. We use the Genesis theme platform for most of our websites. I copied over the header.php file from Genesis into our child theme and added the onload tag to the body tag there (after the PHP body_class part, yes). There’s probably a more elegant solution, but the goal was just to get the code to work. At that point, we had the onload code, the HEAD conversion code, and the class tag around the phone number, but nothing was working. Then a Google engineer sent us a new block of HEAD conversion code to try, replacing the original. Magically, everything started to work…
We gave our feedback to them about the process. I think it’s still a half-baked system at this point.
Burnspot, would you mind posting the header code and and other code used. I’m sure there are many that would appreciate it. Myself included. 🙂
Heh, well, this is funny. I just went through and compared the original HEAD code provided by the AdWords interface to the code the Google engineer sent us…it is a MATCH except that the AdWords interface doesn’t provide it with the opening and closing <script> tags. I didn’t compare this code earlier simply because the “new” code was sent to me late in the evening, at home….just plugged it in and let it go. With that, I have a feeling this is more about an adjustment made by Google on their end (either that or they thought we copied it wrong and wanted to check).
Anyway, the call conversion code that goes in the <head> area is the code provided through the AdWords Call Conversions page…just add <script> to the front and </script> to the end of it when placing it. Probably not wise to post it here as I think it might contain a client identifier. In our case, I just plopped the code into Genesis’ Theme Settings, the Header/Footer Scripts area. So long as the code ends up before the closing </head> in your particular theme, you should be fine.
The body tag on the child theme’s header.php file looks like this:
<body <?php body_class(); ?> onload = "_googWcmGet('phone','AdWordsphone-Number-Here')">
I added it as mentioned in my previous post…copying over the header.php file to our child theme from the master Genesis installation and manually editing the <body> tag.
The client in question has two phone numbers in the body of their home page, the “phone” class, which is referenced by the ONLOAD code, surrounds both of them so that they are changed to the AdWords-provided phone number when a visitor comes into the site from an AdWords clickthru:
<h5 class=”phone”>Call FIRST NUMBER / SECOND NUMBER</h5>
That’s what worked for us. Of course, the inbound must have clicked on an AdWords Ad to see it. After we installed it, the engineer we’d been working with checked it and sent us a verification email that it was working properly.
