DPS integration with Adobe Analytics

This section covers core concepts and basic functionality related to how the Adobe Digital Publishing Suite (DPS) integrates with Adobe Analytics (formerly known as SiteCatalyst), which is part of the Adobe Marketing Cloud.

Report Suite Creation for DPS

Perform Report suite creation for DPS in the DPS Account Administration web application. When a DPS Admin role account is used to configure an account and enable the Application role, the Company Name field and Report Suite Name field become editable.

Customers who have an Adobe Analytics Service contract should put their Company Login Name in the Company Name field if they want the report suite created for that Application role account visible in their Adobe Analytics web application. If it is not done, the data put into the resulting report suite may not be later accessible in their AAS account. If they do not want the report suite accessible from AAS, and don't want to be billed for its activity, they should leave the Company Name field empty.

DPS Enterprise customers must enter a report suite name regardless of whether they have a valid AAS (Omniture) Company Login name to use or not.

DPS Professional customers can only enter a report suite name if they have a valid AAS Company Login name to include. If they do not have an AAS contract, their application role account is assigned a report suite that is shared with other DPS Professional Application accounts. The DPS Account ID is used to filter only that account's data when displayed in the DPS Analytics web application.

Creating a report suite for existing application account

The Report Suite Name shown in the DPS Account Administration application is used to display inside the Adobe Analytics Service web app. If you want to change how it's displayed, that can be done using Administrator tools in the AAS web app. See the online Help for more information on changing the "Site Name" of a report suite.

If an actual new report suite is needed for some significant reason, it requires the assistance the DPS Enterprise Support team. Use the contact information visible in the DPS dashboard when logged in with a DPS Professional or Enterprise account.

The process involves removing the existing settings from the DPS account on the back end. You can then use the Account Administration tool to add a value for the Report Suite Name, and include the Company Name if it was omitted previously.

WARNING: Changing the report suite for an application role account requires any apps built with that account to be rebuilt and delivered to end users before data appears in the new report suite. Information in the old report suite is no longer  visible in the DPS Analytics web app. And, it may not be possible to view in the AAS web app without data migration services from an Adobe Consulting team.

Viewing DPS Analytics data in the DPS web client

DPS Analytics for a single DPS application role account can be viewed when logged into the DPS Dashboard using the credentials for that account. Because it is possible to build multiple apps using the same DPS account, this display may include data from more than one app. This view is often referred to as Baseline Analytics, because it is limited in it's capabilities compared to using Adobe Analytics to view the data. For details, see the DPS Analytics Tutorial page.

Missing data

In this context, missing data means that there is no data at all, or there is no data for date ranges where it is expected. Below are some possible causes, and solutions.

  1. You are not logged in to the dashboard with the Adobe ID used to publish the folios for your application. Log in using the same Adobe ID used as the Title ID when building the app. (Make sure that it's the same that is used when publishing any folios that are expected to appear in that app.) Sign out, and close all browser windows, then sign back in with the correct Adobe ID.

  2. Your app was built using Analytics Report Suite details that do not match the one that is currently in your DPS Account configuration. Contact Adobe Gold Support. Provide them with the Adobe ID used, the Application name, and its Bundle ID created in iTunes Connect (iOS) or in the App Builder (Android).

  3. While rare, it's possible that your Report Suite is not properly configured to be compatible with DPS. Again, contact Gold Support to determine if this issue is the cause.

Missing Articles in Content Views

Article Title is a metadata field that you can edit in either the Folio Builder panel, or the Folio Producer web user interface. The field is not mandatory. If the content view event occurs for an Article with no Title, the statistics for that article are not included in the Dashboard analytics values. To ensure that your articles all have proper titles shown in Analytics, make sure that they have a value. Enter the value in the Folio Producer, then select the folio and click Update. Ensure that you select "Update Contents," or the metadata isn't updated.

There is one other case where "none" appears as the Folio or Issue Name. It's in Folio Purchase reports that are generated when the purchase is the first folio entitlement from a subscription purchase from an app market place (in-app-purchase). In this case, it doesn't always record a folio name.

Viewing DPS analytics in the Adobe Analytics web client.

SiteCatalyst reports are associated with DPS application IDs. They appear in the Adobe Digital Marketing Suite website under SiteCatalyst > Reporting. They are listed in a pop-up menu at the top of that page. For details, see the DPS Analytics Tutorial page.

Missing data

The cause and solution for this issue are the same as listed under Baseline Analytics above.

Missing report suites

There are two common causes for this issue, listed below.

  1. When editing the account for your application in the DPS Account Administration tool, you didn't enter your Omniture Company Login name. Without this value, there is no way to know which Adobe Company Login to associate the report suite with.

    To resolve this issue, contact the Adobe Gold Support with the Adobe ID used as for the Application role. If your Omniture company login is in the same data center that the report suite is in, it's simple to make the relationship. Otherwise, it can be more complicated. See "Implications of changing report suites after app has gone live," at the bottom of this page.

  2. Your report suite was defined in the Account Administration tool in the last five days. The process for associating the report suite to your Omniture company login name is manual. It can take up to five business days to complete. If you are urgent to access the report suite in your SiteCatalyst account, contact Adobe Gold Support and ask them to expedite the process.

Various fields show "none" as value

There is one additional reason you can see a label of "none" for some content in the SiteCatalyst analytics.

There are some activities that the application reports that have no context for content. For example, First App Launch, App Start, and App Close, all happen when there is no folio open. However, they do contribute to some metrics.

if you run some reports such as Issue Name Article Name, or other content, and include metrics such as Visitors and Time Spent, there are significant contributions that come while the app is launched without a folio open.

In these cases, Issue Name (Article name, and so on) "none" is expected. If you are interested only in the data related to events in which a Folio is being viewed in the app, ignore all entries with "none" as a value for some type of content.

 

Additional information

There are other, more serious and difficult-to-resolve cases when you find it necessary to change the report suite, after your app has already been in the market and gathered meaningful data that you want to preserve. These scenarios are outlined here.

Implications of changing report suites after app has gone live

  1. You didn't include your existing Omniture Company Login Name when adding the application role to an Adobe ID in the Account Administration tool. If you are a pro user, the following occurs.

    Instead of creating a report suite, you are assigned an existing report suite that is shared with multiple DPS accounts. Your data is kept private by using a "segment," or filter. It ensures that only you see the data from apps defined with your application role's Adobe ID.

    This data cannot be made visible in a new report suite under your dedicated Omniture account without custom code, which can have costs associated with it.

    Note: If you created your app while you had a pro account, with no Omniture subscription, and then add an Omniture account, the same issue applies.

  2. You have both DPS Enterprise and Omniture accounts, but don't include the correct value in the Company Name field when creating the application role. If the report suite generated is not in the same data center as your Omniture account, you can't view the earlier data without some custom code that could have costs associated with it.

    Note: The same applies if you add SiteCatalyst after you previously used DPS without an Omniture account.

In either of the cases above, it's imperative that you contact your Adobe Gold Support as soon as possible. They can help establish the best solution to begin getting your analytics data into a report suite that you can see in your Omniture SiteCatalyst report. And, they can put you in touch with someone who can discuss options for restoring access to the legacy data from the same.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy