AWS.Tools.AWSMarketplaceCommerceAnalytics.XML
|
<?xml version="1.0"?>
<doc> <assembly> <name>AWS.Tools.AWSMarketplaceCommerceAnalytics</name> </assembly> <members> <member name="T:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet"> <summary> Given a data set type and data set publication date, asynchronously publishes the requested data set to the specified S3 bucket and notifies the specified SNS topic once the data is available. Returns a unique request identifier that can be used to correlate requests with notifications from the SNS topic. Data sets will be published in comma-separated values (CSV) format with the file name {data_set_type}_YYYY-MM-DD.csv. If a file with the same name already exists (e.g. if the same data set is requested twice), the original file will be overwritten by the new file. Requires a Role with an attached permissions policy providing Allow permissions for the following actions: s3:PutObject, s3:GetBucketLocation, sns:GetTopicAttributes, sns:Publish, iam:GetRolePolicy. </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet.CustomerDefinedValue"> <summary> <para> (Optional) Key-value pairs which will be returned, unmodified, in the Amazon SNS notification message and the data set metadata file. These key-value pairs can be used to correlated responses with tracking information from other systems. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet.DataSetPublicationDate"> <summary> <para> The date a data set was published. For daily data sets, provide a date with day-level granularity for the desired day. For weekly data sets, provide a date with day-level granularity within the desired week (the day value will be ignored). For monthly data sets, provide a date with month-level granularity for the desired month (the day value will be ignored). </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet.DataSetType"> <summary> <para> <para>The desired data set type.</para><para><ul><li><strong>customer_subscriber_hourly_monthly_subscriptions</strong><para>From 2014-07-21 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>customer_subscriber_annual_subscriptions</strong><para>From 2014-07-21 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>daily_business_usage_by_instance_type</strong><para>From 2015-01-26 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>daily_business_fees</strong><para>From 2015-01-26 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>daily_business_free_trial_conversions</strong><para>From 2015-01-26 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>daily_business_new_instances</strong><para>From 2015-01-26 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>daily_business_new_product_subscribers</strong><para>From 2015-01-26 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>daily_business_canceled_product_subscribers</strong><para>From 2015-01-26 to present: Available daily by 5:00 PM Pacific Time.</para></li><li><strong>monthly_revenue_billing_and_revenue_data</strong><para>From 2015-02 to 2017-06: Available monthly on the 4th day of the month by 5:00pm Pacific Time. Data includes metered transactions (e.g. hourly) from two months prior.</para><para>From 2017-07 to present: Available monthly on the 15th day of the month by 5:00pm Pacific Time. Data includes metered transactions (e.g. hourly) from one month prior.</para></li><li><strong>monthly_revenue_annual_subscriptions</strong><para>From 2015-02 to 2017-06: Available monthly on the 4th day of the month by 5:00pm Pacific Time. Data includes up-front software charges (e.g. annual) from one month prior.</para><para>From 2017-07 to present: Available monthly on the 15th day of the month by 5:00pm Pacific Time. Data includes up-front software charges (e.g. annual) from one month prior.</para></li><li><strong>disbursed_amount_by_product</strong><para>From 2015-01-26 to present: Available every 30 days by 5:00 PM Pacific Time.</para></li><li><strong>disbursed_amount_by_product_with_uncollected_funds</strong><para>From 2012-04-19 to 2015-01-25: Available every 30 days by 5:00 PM Pacific Time.</para><para>From 2015-01-26 to present: This data set was split into three data sets: disbursed_amount_by_product, disbursed_amount_by_age_of_uncollected_funds, and disbursed_amount_by_age_of_disbursed_funds.</para></li><li><strong>disbursed_amount_by_instance_hours</strong><para>From 2012-09-04 to present: Available every 30 days by 5:00 PM Pacific Time.</para></li><li><strong>disbursed_amount_by_customer_geo</strong><para>From 2012-04-19 to present: Available every 30 days by 5:00 PM Pacific Time.</para></li><li><strong>disbursed_amount_by_age_of_uncollected_funds</strong><para>From 2015-01-26 to present: Available every 30 days by 5:00 PM Pacific Time.</para></li><li><strong>disbursed_amount_by_age_of_disbursed_funds</strong><para>From 2015-01-26 to present: Available every 30 days by 5:00 PM Pacific Time.</para></li><li><strong>customer_profile_by_industry</strong><para>From 2015-10-01 to 2017-06-29: Available daily by 5:00 PM Pacific Time.</para><para>From 2017-06-30 to present: This data set is no longer available.</para></li><li><strong>customer_profile_by_revenue</strong><para>From 2015-10-01 to 2017-06-29: Available daily by 5:00 PM Pacific Time.</para><para>From 2017-06-30 to present: This data set is no longer available.</para></li><li><strong>customer_profile_by_geography</strong><para>From 2015-10-01 to 2017-06-29: Available daily by 5:00 PM Pacific Time.</para><para>From 2017-06-30 to present: This data set is no longer available.</para></li><li><strong>sales_compensation_billed_revenue</strong><para>From 2016-12 to 2017-06: Available monthly on the 4th day of the month by 5:00pm Pacific Time. Data includes metered transactions (e.g. hourly) from two months prior, and up-front software charges (e.g. annual) from one month prior.</para><para>From 2017-06 to present: Available monthly on the 15th day of the month by 5:00pm Pacific Time. Data includes metered transactions (e.g. hourly) from one month prior, and up-front software charges (e.g. annual) from one month prior.</para></li><li><strong>us_sales_and_use_tax_records</strong><para>From 2017-02-15 to present: Available monthly on the 15th day of the month by 5:00 PM Pacific Time.</para></li></ul></para> </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet.DestinationS3BucketName"> <summary> <para> The name (friendly name, not ARN) of the destination S3 bucket. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet.DestinationS3Prefix"> <summary> <para> (Optional) The desired S3 prefix for the published data set, similar to a directory path in standard file systems. For example, if given the bucket name "mybucket" and the prefix "myprefix/mydatasets", the output file "outputfile" would be published to "s3://mybucket/myprefix/mydatasets/outputfile". If the prefix directory structure does not exist, it will be created. If no prefix is provided, the data set will be published to the S3 bucket root. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet.RoleNameArn"> <summary> <para> The Amazon Resource Name (ARN) of the Role with an attached permissions policy to interact with the provided AWS services. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.NewMCADataSetCmdlet.SnsTopicArn"> <summary> <para> Amazon Resource Name (ARN) for the SNS Topic that will be notified when the data set has been published or if an error has occurred. </para> </summary> </member> <member name="T:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet"> <summary> Given a data set type and a from date, asynchronously publishes the requested customer support data to the specified S3 bucket and notifies the specified SNS topic once the data is available. Returns a unique request identifier that can be used to correlate requests with notifications from the SNS topic. Data sets will be published in comma-separated values (CSV) format with the file name {data_set_type}_YYYY-MM-DD'T'HH-mm-ss'Z'.csv. If a file with the same name already exists (e.g. if the same data set is requested twice), the original file will be overwritten by the new file. Requires a Role with an attached permissions policy providing Allow permissions for the following actions: s3:PutObject, s3:GetBucketLocation, sns:GetTopicAttributes, sns:Publish, iam:GetRolePolicy. </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet.CustomerDefinedValue"> <summary> <para> (Optional) Key-value pairs which will be returned, unmodified, in the Amazon SNS notification message and the data set metadata file. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet.DataSetType"> <summary> <para> <para> Specifies the data set type to be written to the output csv file. The data set types customer_support_contacts_data and test_customer_support_contacts_data both result in a csv file containing the following fields: Product Id, Product Code, Customer Guid, Subscription Guid, Subscription Start Date, Organization, AWS Account Id, Given Name, Surname, Telephone Number, Email, Title, Country Code, ZIP Code, Operation Type, and Operation Time. </para><para><ul><li><i>customer_support_contacts_data</i> Customer support contact data. The data set will contain all changes (Creates, Updates, and Deletes) to customer support contact data from the date specified in the from_date parameter.</li><li><i>test_customer_support_contacts_data</i> An example data set containing static test data in the same format as customer_support_contacts_data</li></ul></para> </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet.DestinationS3BucketName"> <summary> <para> The name (friendly name, not ARN) of the destination S3 bucket. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet.DestinationS3Prefix"> <summary> <para> (Optional) The desired S3 prefix for the published data set, similar to a directory path in standard file systems. For example, if given the bucket name "mybucket" and the prefix "myprefix/mydatasets", the output file "outputfile" would be published to "s3://mybucket/myprefix/mydatasets/outputfile". If the prefix directory structure does not exist, it will be created. If no prefix is provided, the data set will be published to the S3 bucket root. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet.FromDate"> <summary> <para> The start date from which to retrieve the data set in UTC. This parameter only affects the customer_support_contacts_data data set type. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet.RoleNameArn"> <summary> <para> The Amazon Resource Name (ARN) of the Role with an attached permissions policy to interact with the provided AWS services. </para> </summary> </member> <member name="P:Amazon.PowerShell.Cmdlets.MCA.StartMCASupportDataExportCmdlet.SnsTopicArn"> <summary> <para> Amazon Resource Name (ARN) for the SNS Topic that will be notified when the data set has been published or if an error has occurred. </para> </summary> </member> </members> </doc> |