| Name : perl-Yahoo-Marketing
| |
| Version : 7.03
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 62.84
| Date : 2024-08-05 18:18:41
|
| Group : Development/Libraries/Perl
| Source RPM : perl-Yahoo-Marketing-7.03-62.84.src.rpm
|
| Size : 0.42 MB
| |
| Packager : (none)
| |
| Summary : An Interface for Yahoo! Search Marketing\'s Web Services
|
Description :
Yahoo\'s Marketing API allows you to manage your search marketing account in
an automated fashion rather than manually. The API is exposed as a standard
SOAP service that you can make calls to. This set of modules is designed to
make using the SOAP service easier than using SOAP::Lite (for example)
directly. There are 2 main types of modules available. The service modules
(CampaignService, AdGroupService, BidInformationService, etc) are used to
make the actual calls to each of the SOAP services in the API. The other
type of module provided are the complex type modules, each of which
represents one of the complex types defined in one of the WSDLs of the SOAP
service. Examples include Campaign, AdGroup, Ad, PendingAd, CreditCardInfo,
etc.
Yahoo::Marketing will call LocationService for you, and cache the results.
This should be completely transparent. See the documtation for cache,
cache_expire_time, purge_cache and clear_cache in Yahoo::Marketing::Service
for more details.
The calls you can make to the various services are documented on YSM\'s
Technology Solutions Portal. See
http://searchmarketing.yahoo.com/developer/docs/index.php
Where the documentation indicates that a complex type must be passed in to
a particular service call, you must pass in the appropriate
Yahoo::Marketing::ComplexType object. For example,
CampaignService->addCampaign requires that a Campaign be passed in:
use Yahoo::Marketing::Campaign;
use Yahoo::Marketing::CampaignService;
my $campaign = Yahoo::Marketing::Campaign->new
->startDate( \'2006-07-16T09:20:30-05:00\' )
->endDate( \'2007-07-16T09:20:30-05:00\' )
->name( \'test campaign\' )
->status( \'On\' )
->accountID( 123456789 )
;
my $campaign_service = Yahoo::Marketing::CampaignService->new;
my $campaign_response = $campaign_service->addCampaign( campaign => $campaign );
my $added_campaign = $campaign_response->campaign;
Note that Yahoo::Marketing is smart enough to upgrade status from a simple
string to the CampaignStatus simpleType for you. All simpleTypes referenced
in the WSDLs are automatically handled for you - just pass in an
appropriate string, and let Yahoo::Marketing do the rest.
When a method expects that multiple values will be set for a parameter, you
must pass an anonymous array. An example would be
AdGroupService->deleteAdGroups:
my $ad_group_service = Yahoo::Marketing::AdGroupService->new;
$ad_group_service->deleteAdGroups( adGroupIDs => [ \'9167298\', \'2932719\', \'1827349\' ] ); # existing Ad Group IDs
If a call returns data, you will receive an array if you make the call in
an array context:
my AATTad_groups = $ad_group_service->getAdGroups(
adGroupIDs => [ \'9167298\', \'2932719\', \'1827349\'],
);
Or just the first (or only element, if only one returned object is
expected) if you make the call in a scalar context:
my $ad_group = $ad_group_service->getAdGroups(
adGroupIDs => [ \'9167298\', \'2932719\', \'1827349\'],
);
Suggestions for improving how multiple return values should be handled in a
scalar context are welcome.
If a SOAP Fault is encountered (whenever a call fails), the
Yahoo::Marketing service will croak with the fault by default. If you set
the immortal option, Yahoo::Marketing will not die, $service->fault will be
set to the SOAP fault. The \"immortal mode\" is similar to how SOAP::Lite
behaves by default.
Note that all get/set methods (and many other methods) are \"chainable\".
That is, they return $self when used to set, so you can chain them
together. See examples of this above and below in this documentation.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl:/CPAN-Y/openSUSE_Tumbleweed/noarch |
