Do you have a question about Digital Analytics? We're happy to answer them all.

If you can't find what you were looking for, please enter a help ticket with Acoustic support.

Creating segments on standard reports

Q: Can I change the date range on a segment that is already applied to a standard report?

A: When applying a segment to a standard report, you’ll need to set the date range as far back as you would like to use the segment on the report. This date range cannot be modified once the segment is applied to the report and begins processing. If you need to make adjustments to the segment date range, you’ll need to remove the segment from the report and re-apply it completely.

Unique metrics in reports

Q: How do I know when unique-based metrics, such as unique visitors, are unique in reports?

A: In some cases, when you add preset date ranges to reports, unique-based metrics, such as unique visitors, are summed and not deduplicated. When summation occurs instead of deduplication, metrics are no longer unique.

Metrics are deduplicated for all date ranges in ad hoc reports. For standard reports, deduplication logic follows these rules:

• Daily: deduplicated by day
• Weekly: deduplicated by week
• Monthly: deduplicated by month
• Quarterly: deduplicated by quarter for Top Line Metrics only; summed by day (not deduplicated) for all other reports
• Yearly: not deduplicated; summed by quarter for Top Line Metrics only, summed by month for all other reports
• Custom date ranges are not deduplicated.

Metrics are unique when the following trend by options are selected for date ranges in reports:

• Day range, trend by day
• Week range, trend by week
• Month range, trend by month
• Quarter range, trend by quarter for Top line reports only; not unique for all other reports.

Reminder: Sampling is applied to all date ranges over 93 days in one-time reports.

Note: Only the daily, weekly, and monthly date ranges are deduplicated in all reports; the Week-to-date, Month-to-date, Quarter-to-date, and Year-to-date date ranges are not deduplicated.

Displaying personal information in reports

Q: Why is personal information displayed as "xxx" in reports?

A: Only users with permission to view personal data can view a subject's personal information in reports, segments, and filters.

Administrators can set permission for a user in user management.

When a GDPR deletion request is submitted, all personal data associated with that request's visitor(s) is removed from Digital Analytics. In older reports that have already run, the personal data that has been removed will then appear as “xxx”.

Implementation test tool (ITT)

Q: How long will I be able to use the ITT?

A: ITT was available until September 1st. You will still be able to use the Tagbar and your test environment. There are other tools outside of Acoustic, like Fiddler that you can evaluate for your testing needs.

How can I use data unavailable in the reports I am creating?

When a user has no permission to access personal information and tries to create a report, the user is restricted from using breakouts, segments, filters, metrics, and custom groups that contain personally identifiable information (PII).

PII is any information that can be used (either on its own or with other information) to identify, contact, or locate an individual. Such information might be a customer's name, credit card information, address, phone number, identification number, and so on.

Products listed under No Category Assigned in the Product Categories report

Products that are listed under No Category Assigned in the Product Categories report indicate a problem with either the Category Definition File (CDF) or the Digital Analytics tags.

Install the Digital Analytics Plug-in to access the Digital Analytics TagBar.

Products are listed in the top-level No Category Assigned category when Digital Analytics receives category information from a product tag, but the category ID is not present in CDF. Products are listed in a No Category Assigned subcategory (No Category Assigned > No Category Assigned) when the products do not send category ID information in the Digital Analytics tag.

1. Open the Digital Analytics TagBar.
2. Check the tags for the products under No Category Assigned.
1. For products listed under No Category Assigned at the top level, check the category ID in the corresponding Product View tags and ensure that the category ID is mapped correctly in the CDF.
2. Ensure that the Product View tags contain the correct Category ID for products listed in a No Category Assigned subcategory.
3. Make any necessary changes to your Product View tags or CDF.
4. If you make changes to the CDF file, the updated file must be uploaded to Digital Analytics.

The next time the report is processed, the Product Categories report reflects the updated category structure.

How do I know when unique-based metrics, such as unique visitors, are unique in reports?

In some cases, when you add preset date ranges to reports, unique-based metrics, such as unique visitors, are summed and not deduplicated. When summation occurs instead of deduplication, metrics are no longer unique.

Metrics are deduplicated for all date ranges in ad hoc reports. For standard reports, deduplication logic follows these rules:

• Daily: deduplicated by day
• Weekly: deduplicated by week
• Monthly: deduplicated by month
• Quarterly: deduplicated by quarter for Top line reports only; summed by day (not deduplicated) for all other reports
• Yearly: summed by day (not deduplicated)
• Custom date ranges are not deduplicated

Sampling is applied to all date ranges over 93 days in one-time reports.

Note: Only the daily, weekly, and monthly date ranges are deduplicated in all reports; the Week-to-date, Month-to-date, Quarter-to-date, and Year-to-date date ranges are not deduplicated.

Why are my reports now showing dimensions for some registrants?

The new DDR implementation provides many optimized algorithms that result in improved data quality in metrics.

In cases where the data pool is small, or the data type uses a metric (such as orders) based on a customer implementation, you might see some discrepancies or overall skewed results. If you see these types of discrepancies, contact Support for an explanation. In some cases, a detailed report can be provided.

For example, one type of discrepancy can occur with registration dimensions.

In legacy Digital Analytics and earlier releases of the new Digital Analytics UI, the following registration dimensions were marked empty (or zero for Lifetime Orders and Lifetime Sales) when a registrant had a large number of unique cookie_ids per day (for example, 100 cookie_ids):

• Age
• Education Level
• Email Address
• Gender
• Income Level
• Lifetime Orders
• Lifetime Sales
• New/Repeat Buyer
• Registered City
• Registered Country
• Registered State
• Registered ZIP Code

In this case, if a report included one or more registration dimensions and a registrant with a large number of cookie_ids per day, dimensions for the registrant were missing from the report. For example, the table shows the report results for RegistrationId 123 with 100 or more unique cookie_ids.

In the latest release of Digital Analytics, registration dimensions are populated in the report for registrants with a large number of cookie_ids. For example, the table shows the report results for RegistrationId 123 with 100 or more unique cookie_ids.

Additionally, in cases where the registration id is missing from the report, legacy Digital Analytics aggregates the report data. For example, the following tables show report results for legacy Digital Analytics and the new UI where the registration id is not included in the report: Legacy DA

New UI

Why is personal information displayed as "xxx" in reports?

Only users with permission can view a subject's personal information in reports, segments, and filters in Digital Analytics. Users without permission cannot open the report at all.

When a GDPR request to delete personal information occurs, personal information is deleted for all users, regardless of user permission. In this case, users with permission see "xxxxx" in place of personal information.

Administrators can set permission for a user by opening a support ticket.