ACK Analytics Service

You can use the Alexa Connect Kit (ACK) analytics service to collect, store, and analyze data about the performance and use of your ACK products. If you choose to collect logs or metrics, the ACK analytics service gathers and stores the requested data from your ACK-based devices. The analytics service can collect data from the following categories: product logs, operational metrics, product metrics, heartbeat metrics, and registration metrics.

All collected data is securely stored within the ACK analytics service, and you can access your data at any time. To link your Amazon Web Services (AWS) developer account to the analytics service or request a custom data collection, you submit a request through your designated ACK support engineer.

You can also request assistance from your ACK support engineer to help troubleshoot or resolve issues with your ACK products. To help troubleshoot, Amazon may use your logs and metrics to fulfill that request. To request the analytics service, see Get Support for the Alexa Connect Kit and include the data collection categories to enable.

Data management

You can access, delete, and manage the retention period of the logs and metrics stored for your ACK products. To manage your data, follow these instructions.

Access – You always have access to your data. Your ACK support engineer can share access to the logs and metrics collected from your devices with your AWS developer account. You can also request a downloadable copy of your ACK logs and metrics for an individual device or a group of products based on device capability or a particular log or metric. To submit an access request from the ACK developer portal, navigate to the Product page and then choose the Data settings tab. After you request access, Amazon sends you an email with a link to the requested data within five business days. The link expires after seven days.
Deletion – You can delete your ACK logs and metrics for all devices at one time or for an individual device. A deletion request results in the deletion of all logs and metrics associated with the specified device but does not de-register the device. To submit a deletion request from the ACK developer portal, navigate to the Product page and then choose the Data settings tab.
Retention – You determine how long to store ACK product logs and metrics. The default retention period is 365 days, but you can set your preferred retention period when you configure the logs and metrics for your device or at any time thereafter. Shortening the retention period automatically deletes logs and metrics older than the specified period. To change your data retention settings, contact your support engineer.

Data access and security

ACK uses industry standard encryption protocols to encrypt logs and metrics in transit from your device and at rest. The ACK analytics service retains the encrypted data in an AWS S3 bucket. To help you understand device performance and troubleshoot device issues, your ACK support engineer can share access to the S3 bucket with your AWS developer account. If you open a troubleshooting ticket for help with your ACK product, Amazon grants access to ACK support engineers to view the logs and metrics associated with your devices. This access lasts until you close the troubleshooting request.

Product logs

When you enable product logs, the ACK analytics service stores the collected logs in the S3 bucket to help you troubleshoot ACK device issues. Logs are used to collect detailed information about the sequence of events and the code or workflow that leads to a given condition. Product logs should include the information necessary to help you debug device issues. You define the payload of the log types that you want to collect and determine how to command your device to upload its logs for debugging purposes. Include information, such as timestamp, device type, and device serial number.

To collect product logs, a customer can trigger a log upload, if you implemented that feature. Or, you can request your ACK support engineer to trigger the upload remotely. Your ACK support engineer gives you access to the uploaded logs. The ACK analytics service doesn't collect product logs on a schedule or automatically.

Metrics

When you enable metrics for your product, the ACK analytics service collects metrics from the ACK-based devices that you specified. The analytics service collects following metrics: operational metrics, product metrics, heartbeat metrics, and registration metrics. ACK support engineers may use metrics collected from your devices to monitor device health and detect anomalies during critical periods, such as launch, OTA updates, or negative trends in customer reviews.

Operational metrics

Analysis of operational metrics allows you to continually monitor for and proactively troubleshoot issues that arise with device performance or Alexa service integration.

Amazon defines operational metrics based on the capabilities of your device, which might change over time. In general, each operational metric collected from your device includes metadata, such as the fields listed in the following table.

Field	Description
`boot_time`	Timestamp of the last time the device rebooted, formatted as epoch time.
`device_serial_number`	Serial number of the device.
`firmware_version`	Device firmware version for ACK SDK or ACK SDK for Matter, or module firmware version for ACK Module.
`metric_type`	Domain of the metric, such as `ack_perf`.
`timestamp`	Time of the event, formatted as epoch time.
`data_type`	Unit of the metric, such as milliseconds or count.
`name`	Name of the metric, such as `ack_free_memory`.
`counter`	Value of the metric, such as 1 for occurrence of a counter metric or 1000 milliseconds.

Product metrics

Use product metrics to learn how customers use your ACK products and to detect if your devices have potential issues. When you configure your ACK product firmware, you define the product metrics that you want to collect. For example, you can define product metrics that correspond to the capabilities your device offers customers, such as on/off or various device modes. The ACK analytics service uploads product metrics each time the designated event occurs.

Tip: To get started, ACK provides sample applications that show examples of useful product metrics.

The ACK analytics service provides a predefined metadata schema for product metrics, including the fields shown in the following table. You can customize the payload content for each field to capture your desired information.

Field	Description
`boot_time`	Timestamp of the last time the device rebooted, formatted as epoch time.
`device_serial_number`	Serial number of the device.
`firmware_version`	Device firmware version for ACK SDK or ACK SDK for Matter, or module firmware version for ACK Module.
`metric_type`	Domain of the metric, such as `AppUserActivity`.
`timestamp`	Time of the event, formatted as epoch time.
`data_type`	Unit of the metric, such as gauge or count.
`name`	Name of the metric, such as `brightness, onoff`.
`counter`	Value of the metric, such as `1` for occurrence of a counter metric.
`number`	Value of the metrics for gauges, such as `254` for brightness setting.

Heartbeat metrics

Heartbeat metrics provide engagement data to help you troubleshoot ACK products and understand customer device usage patterns. If you enable heartbeat metrics, the ACK analytics service collects two key metrics: power status (Is the device receiving power?) and Wif-Fi connectivity status (Is the device connected to Wi-Fi?). The ACK analytics service collects and uploads the following metadata as part of these heartbeat metrics each time a device event occurs.

Field	Description
`boot_time`	Timestamp of the last time the device rebooted, formatted as epoch time.
`dsn`	Serial number of the device.
`device_type`	Identified kind of device.
`software_version`	Device firmware version for ACK SDK or ACK SDK for Matter, or module firmware version for ACK Module.
`metric_type`	Domain of the metric, such as `ack_perf`.
`device_record_date`	Date of the event, formatted as epoch day.
`device_record_time`	Time of the event, formatted as epoch time.
`name`	Name of the metric, such as `PowerOn`, `PowerOnHeartbeat`, `WifiConnected`, `WifiConnectedHeartbeat`.

Registration metrics

You can choose to collect registration metrics to help you track and monitor the registration status of your ACK devices. These metrics enable you to observe registration patterns over time and quickly identify potential issues when sudden or unexpected changes occur in registration status.

The ACK analytics service captures registration data when a customer registers, de-registers, or re-registers a device. When these events occur, the service automatically records and uploads the following registration metrics

Note: The ACK analytics service includes registration metrics for ACK SDK for Matter devices in the Operational metrics.

Field	Description
event_complete_date	Date of the event, formatted as epoch day.
event_complete_time	Time of the event, formatted as epoch time.
event_type	Kind of event. If a device is re-registered, without explicitly being de-registered, a de-register metric is still created.
device_serial_number	Serial number of the device.

Was this page helpful?

Provide feedback

Last updated: Mar 07, 2025