Re: Tracking Template on AdGroup Level (or higher)

2015-06-01 Thread ralf.s
Hello Josh,

what if final-url contains parameters and final-mobile-url not?
Would it be possible, to set a correct tracking-template with additional 
parameters?
I think NOT.

Kind Regards
Ralf

Am Mittwoch, 20. Mai 2015 22:39:52 UTC+2 schrieb Josh Radcliff (AdWords API 
Team):
>
> Hi Ralf,
>
> The {lpurl} parameter will be escaped unless it's at the beginning of your 
> tracking template. If that parameter value is escaped, will you still have 
> the problem with two question marks since the one coming from *lpurl* will 
> have an escaped question mark?
>
> Thanks,
> Josh, AdWords API Team
>
> On Wednesday, May 20, 2015 at 2:43:07 AM UTC-4, ralf.s wrote:
>>
>> Hi Josh,
>>
>> Thanks for your quick answer.
>> According to it, Tracking templates on ad or higher level are only 
>> possible, if all final-urls follow the same scheme: all having already 
>> parameters or none have parameters.
>> Because in real life, you cannot ensure this, tracking templates on ad 
>> level ist NOT possible.
>>
>> Kind Regards
>> Ralf
>>
>> Am Dienstag, 19. Mai 2015 22:48:27 UTC+2 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Ralf,
>>>
>>> The substitution is a simple replacement, so in your example, you would 
>>> get the URL from option #1.
>>>
>>> You may want to check out our *Upgraded URLs* presentation on the AdWords 
>>> API Workshops site <http://www.adwordsapiworkshops.com/#res>, as it 
>>> contains both a video of the presentation and the accompanying slides.
>>>
>>> In addition, we recently published a guide on upgraded URL expansion 
>>> rules 
>>> <https://developers.google.com/adwords/api/docs/guides/serving-url-expansion-rules>
>>>  that 
>>> may be helpful.
>>>
>>> Cheers,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, May 19, 2015 at 5:54:46 AM UTC-4, ralf.s wrote:
>>>>
>>>> Hello,
>>>>
>>>> we want to use tracking templates on adgroup level (or higher).
>>>> We would like to set it to eg.
>>>>   {lpurl}?para2=value
>>>>
>>>> Will this work for all final URLs of all ads and keywords in this 
>>>> adgroup?
>>>> What happens, if a final URL already contains a question mark? eg.
>>>>   http://www.anydomain.com?para1=x
>>>>
>>>> How will the target URL in this case look like?
>>>> Either
>>>> 1. http://www.anydomain.com?para1=x?para2=value
>>>> or
>>>> 2. http://www.anydomain.com?para1=x¶2=value
>>>>
>>>> The first case would create an invalid URL. Most Browsers will evaluate 
>>>> parameter para1 as "x?para2=value" and will miss para2.
>>>>
>>>> What is the preffered way to set a tracking template and adgroup level?
>>>>
>>>> Kind Regards
>>>> Ralf
>>>>
>>>>
>>>>
>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/3360c320-7640-49e3-9ab0-33c44c5f0221%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Tracking Template on AdGroup Level (or higher)

2015-05-19 Thread ralf.s
Hi Josh,

Thanks for your quick answer.
According to it, Tracking templates on ad or higher level are only 
possible, if all final-urls follow the same scheme: all having already 
parameters or none have parameters.
Because in real life, you cannot ensure this, tracking templates on ad 
level ist NOT possible.

Kind Regards
Ralf

Am Dienstag, 19. Mai 2015 22:48:27 UTC+2 schrieb Josh Radcliff (AdWords API 
Team):
>
> Hi Ralf,
>
> The substitution is a simple replacement, so in your example, you would 
> get the URL from option #1.
>
> You may want to check out our *Upgraded URLs* presentation on the AdWords 
> API Workshops site <http://www.adwordsapiworkshops.com/#res>, as it 
> contains both a video of the presentation and the accompanying slides.
>
> In addition, we recently published a guide on upgraded URL expansion rules 
> <https://developers.google.com/adwords/api/docs/guides/serving-url-expansion-rules>
>  that 
> may be helpful.
>
> Cheers,
> Josh, AdWords API Team
>
> On Tuesday, May 19, 2015 at 5:54:46 AM UTC-4, ralf.s wrote:
>>
>> Hello,
>>
>> we want to use tracking templates on adgroup level (or higher).
>> We would like to set it to eg.
>>   {lpurl}?para2=value
>>
>> Will this work for all final URLs of all ads and keywords in this adgroup?
>> What happens, if a final URL already contains a question mark? eg.
>>   http://www.anydomain.com?para1=x
>>
>> How will the target URL in this case look like?
>> Either
>> 1. http://www.anydomain.com?para1=x?para2=value
>> or
>> 2. http://www.anydomain.com?para1=x¶2=value
>>
>> The first case would create an invalid URL. Most Browsers will evaluate 
>> parameter para1 as "x?para2=value" and will miss para2.
>>
>> What is the preffered way to set a tracking template and adgroup level?
>>
>> Kind Regards
>> Ralf
>>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/9474984a-4867-47fd-8279-e3c3204a8021%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Tracking Template on AdGroup Level (or higher)

2015-05-19 Thread ralf.s
Hello,

we want to use tracking templates on adgroup level (or higher).
We would like to set it to eg.
  {lpurl}?para2=value

Will this work for all final URLs of all ads and keywords in this adgroup?
What happens, if a final URL already contains a question mark? eg.
  http://www.anydomain.com?para1=x

How will the target URL in this case look like?
Either
1. http://www.anydomain.com?para1=x?para2=value
or
2. http://www.anydomain.com?para1=x¶2=value

The first case would create an invalid URL. Most Browsers will evaluate 
parameter para1 as "x?para2=value" and will miss para2.

What is the preffered way to set a tracking template and adgroup level?

Kind Regards
Ralf



-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/7a77aaa2-aa82-43e8-8637-a3c951753e31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


AdWords API Re: InfoService with API 200909

2010-02-05 Thread ralf.s
Hi Eric,

we always use the MCC-user to get the auth-token and we use the email
of the specific account in the soap-header of the services.
we tried the InfoService also with the MCC-user in the soap-header -
but both variants do not work.

Thanks
Ralf

On Feb 3, 8:25 pm, AdWords API Advisor 
wrote:
> Hi Ralph,
>
> One of the caveats of the newInfoServiceis that it currently only
> works if your email and password used to generate the authToken is for
> the MCC account that owns the developer token (has the AdWords API
> Center tab in the web interface).  Please ensure that you are using
> this MCC user when generating your authToken and try again.
>
> Best,
> - Eric Koleda, AdWords API Team
>
> On Feb 2, 10:20 am, "ralf.s"  wrote:
>
>
>
> > We still get have problems with theInfoServiceof Version V200909.
> > V13 works fine here.
> > We do exactly whats listed in the Per-Call Migration Guide.
> > We use java and the adwords-api-6.3.0-loner.jar lib.
>
> > Example 1:
> > InfoSelector selector = new InfoSelector();
> > selector.setApiUsageType(ApiUsageType.UNIT_COUNT);
> > selector.setDateRange(new DateRange("20100101", "20100201"));
> > ApiUsageInfo res = service.get(selector);
>
> > always return 0 costs, while V13 Version getUnitCount(startDate,
> > endDate) works fine.
>
> > Example 2:
>
> > InfoSelector selector = new InfoSelector();
> > selector.setClientEmails(new String[] { "" });
> > selector.setApiUsageType(ApiUsageType.UNIT_COUNT_FOR_CLIENTS);
> > selector.setDateRange(new DateRange("20100101", "20100201"));
> > ApiUsageInfo res = service.get(selector);
>
> > throws an error [ApiUsageError.INVALID_CLIENT_EMAIL @ selector] also
> > the specified email is a valid account in the mcc-acount.
>
> > Any suggestions?
>
> > Thanks
> > Ralf
>
> > By the way. Sample Code for Java is still for V200906 and not all
> > Services are included.

-- 
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-...@googlegroups.com.
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en.



AdWords API InfoService with API 200909

2010-02-02 Thread ralf.s
We still get have problems with the InfoService of Version V200909.
V13 works fine here.
We do exactly whats listed in the Per-Call Migration Guide.
We use java and the adwords-api-6.3.0-loner.jar lib.

Example 1:
InfoSelector selector = new InfoSelector();
selector.setApiUsageType(ApiUsageType.UNIT_COUNT);
selector.setDateRange(new DateRange("20100101", "20100201"));
ApiUsageInfo res = service.get(selector);

always return 0 costs, while V13 Version getUnitCount(startDate,
endDate) works fine.


Example 2:

InfoSelector selector = new InfoSelector();
selector.setClientEmails(new String[] { "" });
selector.setApiUsageType(ApiUsageType.UNIT_COUNT_FOR_CLIENTS);
selector.setDateRange(new DateRange("20100101", "20100201"));
ApiUsageInfo res = service.get(selector);

throws an error [ApiUsageError.INVALID_CLIENT_EMAIL @ selector] also
the specified email is a valid account in the mcc-acount.

Any suggestions?

Thanks
Ralf

By the way. Sample Code for Java is still for V200906 and not all
Services are included.


-- 
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-...@googlegroups.com.
To unsubscribe from this group, send email to 
adwords-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/adwords-api?hl=en.