Pete and Jan, The URL with parameters included looks like the following:
http://example.com/?av=165dc333bd Naturally, all of the destination URL's contain this same format with a unique code that is exactly 10 characters in length. There is only one parameter (obviously, the unique ad code). I went ahead and took a screenshot of one of the ads from within AdWords: http://s154.photobucket.com/albums/s267/positus-reputo/?action=view¤t=ad_screenshot.jpg - Don On Dec 3, 4:06 pm, "Pete Lavetsky (AdWords API Guru)" <[EMAIL PROTECTED]> wrote: > Can you post just the parameter side of a destination URL you're > working with so we can take a look? Or just use example.com with all > your parameters appended on. Maybe there's something screwy like > multiple ?'s or something where you'll have to use URL encoding ... > please post the parameter side verbatim. > > Thanks > Pete > > On Dec 3, 3:01 pm, positus <[EMAIL PROTECTED]> wrote: > > > Thank you for your response, Pete. Yes, all of the destination URL's > > contain the required parameters, and clicking on them from within > > AdWords will maintain the integrity of the URL & parameters. However, > > not so with clicking any of the live ads. Clicking on one of the live > > ads renders a URL such as the following: > > >http://www.google.com/aclk?sa=L&ai=Bldn1puQ2Sc7DBofKtgeM-OXMAqCrl2n-l... > > > At the end of the google URL it redirects to the destination URL > > appended to it, but none of the parameters are intact. I am at a loss > > as to why, and what to do about it. > > > On Dec 3, 3:40 am, "Pete Lavetsky (AdWords API Guru)" > > > <[EMAIL PROTECTED]> wrote: > > > Are you seeing the full URL in the MCC? We use URL parameters on all > > > our destination URLs and have no issues. > > > > Pete > > > > On Dec 2, 4:32 pm, positus <[EMAIL PROTECTED]> wrote: > > > > > Thank you for your prompt response, Jeff. I have posted the question > > > > in the AdWords forum (http://www.google.com/support/forum/p/AdWords/ > > > > thread?tid=10042a5ad5994e1f&hl=en). > > > > > On Dec 2, 2:59 pm, AdWords API Advisor <[EMAIL PROTECTED]> > > > > wrote: > > > > > > Hello, > > > > > > I'm surprised you're seeing that behavior, as snipping off the query > > > > > portion of destination URLs seems like it would cause a whole variety > > > > > of issues if AdWords always did that. Perhaps someone in this group > > > > > has seen similar behavior and knows of a workaround. > > > > > > That being said, the best way to get help about this issue is to > > > > > either post in the general AdWords forum: > > > > > > http://www.google.com/support/forum/p/AdWords > > > > > > or to contact AdWords support by following the steps at > > > > > > http://adwords.google.com/support/bin/request.py?fhc=1&ctx=cuffhelp > > > > > > While you're using the AdWords API to create these ads, it sounds like > > > > > the actual issue you're experiencing isn't API related, but rather > > > > > something going on with AdWords itself. > > > > > > Cheers, > > > > > -Jeff Posnick, AdWords API Team > > > > > > On Dec 2, 1:46 pm, positus <[EMAIL PROTECTED]> wrote: > > > > > > > Also, in case this extra bit of information is helpful, the > > > > > > destination URL with the appended code looks something like > > > > > > this:http://example.com/?av=c4b8f491db --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
