Struct google_dfareporting2d2::PlacementGeneratetagCall
[−]
[src]
pub struct PlacementGeneratetagCall<'a, C, A> where C: 'a, A: 'a { /* fields omitted */ }
Generates tags for a placement.
A builder for the generatetags method supported by a placement resource.
It is not used directly, but through a PlacementMethods
instance.
Example
Instantiate a resource method builder
// You can configure optional parameters by calling the respective setters at will, and // execute the final call using `doit()`. // Values shown here are possibly random and not representative ! let result = hub.placements().generatetags("profileId") .add_tag_formats("eirmod") .add_placement_ids("elitr") .campaign_id("gubergren") .doit();
Methods
impl<'a, C, A> PlacementGeneratetagCall<'a, C, A> where C: BorrowMut<Client>,
A: GetToken
[src]
A: GetToken
fn doit(self) -> Result<(Response, PlacementsGenerateTagsResponse)>
Perform the operation you have build so far.
fn profile_id(self, new_value: &str) -> PlacementGeneratetagCall<'a, C, A>
User profile ID associated with this request.
Sets the profile id path property to the given value.
Even though the property as already been set when instantiating this call, we provide this method for API completeness.
fn add_tag_formats(self, new_value: &str) -> PlacementGeneratetagCall<'a, C, A>
Tag formats to generate for these placements.
Append the given value to the tag formats query property. Each appended value will retain its original ordering and be '/'-separated in the URL's parameters.
fn add_placement_ids(self,
new_value: &str)
-> PlacementGeneratetagCall<'a, C, A>
new_value: &str)
-> PlacementGeneratetagCall<'a, C, A>
Generate tags for these placements.
Append the given value to the placement ids query property. Each appended value will retain its original ordering and be '/'-separated in the URL's parameters.
fn campaign_id(self, new_value: &str) -> PlacementGeneratetagCall<'a, C, A>
Generate placements belonging to this campaign. This is a required field.
Sets the campaign id query property to the given value.
fn delegate(self,
new_value: &'a mut Delegate)
-> PlacementGeneratetagCall<'a, C, A>
new_value: &'a mut Delegate)
-> PlacementGeneratetagCall<'a, C, A>
The delegate implementation is consulted whenever there is an intermediate result, or if something goes wrong while executing the actual API request.
It should be used to handle progress information, and to implement a certain level of resilience.
Sets the delegate property to the given value.
fn param<T>(self, name: T, value: T) -> PlacementGeneratetagCall<'a, C, A> where T: AsRef<str>
Set any additional parameter of the query string used in the request. It should be used to set parameters which are not yet available through their own setters.
Please note that this method must not be used to set any of the known paramters which have their own setter method. If done anyway, the request will fail.
Additional Parameters
- quotaUser (query-string) - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters. Overrides userIp if both are provided.
- oauth_token (query-string) - OAuth 2.0 token for the current user.
- key (query-string) - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
- prettyPrint (query-boolean) - Returns response with indentations and line breaks.
- userIp (query-string) - IP address of the site where the request originates. Use this if you want to enforce per-user limits.
- fields (query-string) - Selector specifying which fields to include in a partial response.
- alt (query-string) - Data format for the response.
fn add_scope<T>(self, scope: T) -> PlacementGeneratetagCall<'a, C, A> where T: AsRef<str>
Identifies the authorization scope for the method you are building.
Use this method to actively specify which scope should be used, instead the default Scope
variant
Scope::Dfatrafficking
.
The scope
will be added to a set of scopes. This is important as one can maintain access
tokens for more than one scope.
Usually there is more than one suitable scope to authorize an operation, some of which may encompass more rights than others. For example, for listing resources, a read-only scope will be sufficient, a read-write scope will do as well.