important notes for adobe cert

  • Cohort Analysis

    • Cohort Analysis does not support non-segmentable metrics (including calculated metrics), non-integer metrics (such as Revenue), or Occurrences.

    • Only metrics that can be used in segments can be used in Cohort Analysis, and they can only be incremented by >1 at a time.

  • Segment Comparison 

    • Top Metrics: Metrics added to this table after the segment comparison has finished do not receive a Difference Score.

    • Top Dimensions: Dimension items added to this table after the segment comparison has finished do not receive a Difference Score.

    • Top Segments: Segments added to this table after the segment comparison has finished do not receive a Difference Score.

  • Anomaly Detection

    • Adobe Analytics Select and Adobe Analytics Foundation customers have access only to “daily-granularity” Anomaly Detection in Workspace. For more information, see Anomaly Detection and Contribution Analysis Entitlements.

  • Marketing Channels

    • Apply channels from a template before you apply rule sets. Your channels must be the same across all report suites when performing this procedure.

    • There might be still some channel traffic that can fall into the No Channel Identified category. For example: A visitor comes to the site and bookmarks a page and in the same visit comes back the page via the bookmark. Since this is not the first page of the visit, it will go neither in the Direct channel nor in the Other channel because there is no referring domain.

    • You cannot delete a channel. If you do not want to use a channel, you can disable or rename it, and preserve it for later use.

  • Advertising Analytics 

    • This integration creates a new set of dimensions through classifications of the AMO ID variable. These new dimensions do not impact or modify your existing marketing channels or campaign tracking variable dimensions. The AMO ID is connected to a visitor’s profile when a visitor land on the site from a paid search ad. As such, the AMO dimensions can be used to break down both the AMO metrics provided by this integration as well as any data captured downstream by the visitor (visits, visitors, page views, bounce rate, orders, revenue, custom events, etc). They can also be broken down by other dimensions when reporting on other onsite metrics.

    • The classifications for these metrics are updated daily. As such, if you make changes to the meta data in a search engine, you may not see those changes reflect until the following day when the classifications are updated.

  • Unique Visitors

    • Each Analytics visitor ID is tied to a profile on Adobe’s servers. These visitor profiles are deleted after at least 13 months of inactivity regardless of any visitor ID cookie expiration.

  • Bot Rules

    • The Adobe Experience Platform Edge Network provides a bot detection service which labels hits identified as being from bots. The bot detection process used in Adobe Analytics is separate and does not reference the bot score included on data arriving through the Edge Network. However, the two systems use the same IAB bot list.

    • The user interface allows for 500 rules to be manually defined. After this limit is reached, rules must be managed in bulk through the Import File and Export Bot Rules options.

    • Before removing bot traffic, communicate with stakeholders to make sure they can make the necessary adjustments to key performance indicators as a result of this change. If possible, we recommend first removing bot traffic from a small report suite to estimate the potential impact.

    • To match a bot using a combination of rules joined with an OR (for example, user agent or IP address), provide an identical name for all rules that you want to combine in the bot name field. AND matches are not supported.

    • Hits marked as bots are billed as server calls.

  • Conversion var

    • Only a single value can be stored in an eVar in an image request. If multiple values are desired in an eVar value, we recommend that you implement List variables (list vars).

    • You must first configure eVars to ‘Counter’ in the Admin Console before using counter eVars. See Conversion variables in the Admin guide.

  • Data Exclusion

    • Processing rules cannot exclude data or send data to another report suite. However, certain variables can be conditionally set, and a segment can be used to exclude that data from reporting.

  • Fallout Analysis

    • Segments used as checkpoints in Fallout must use a container that is at a lower level than the overall context of the Fallout visualization. With a visitor-context Fallout, segments used as checkpoints must be visit or hit-based segments. With a visit-context Fallout, segments used as checkpoint must be hit-based segments. If you use an invalid combination, the fallout will be 100%. We have added a warning to the Fallout visualization that will display when you add an incompatible segment as a touchpoint. Certain invalid segment container combinations will lead to invalid Fallout diagrams, such as

  • Sharing Projects

    • Consider the following when sharing an Analysis Workspace project with people who don’t have access to Adobe Analytics:

      • The ability to share a project in this way can be disabled by the Analytics administrator, as described in Preferences. If you can’t share a project as described in this section, your Analytics administrator has disabled this ability.

      • Projects with more than 50 expanded visualizations can’t be shared with people who don’t have access to Adobe Analytics.

      • Users you share the project with can view any filters that were applied to the project during curation.

      • Users you share with can change the project date range. The date range you set for the project is shown by default.

      • A project might become inaccessible if many users attempt to access a given link at the same time. By default, more than 190 people can access a single link every 5 minutes. If your organization reaches this limit, wait 5 minutes and then try accessing the link again.

  • Curating Projects

    • Product profiles are the primary mechanism governing which components a user can see. They are managed through the Adobe Experience Cloud Admin Console. Curation is a secondary filter.

    • Virtual report suite curation is always applied before project curation. This means that even if your curated project includes certain components, they will be filtered out if the curated Virtual report suite does not include them.

  • Panel

    • If a (purple) date range component is used within a table, visualization or panel drop zone, it overrides the panel calendar.

  • Data Warehouse

    • When segmenting on classified values, Analysis Workspace and Data Warehouse treat ‘unspecified’ values differently. ‘Unspecified’ in Workspace refers to values that are not classified, whereas ‘Unspecified’ in Data Warehouse refers to values that you classified as “Unspecified”.

    • Data Warehouse reports the first value encountered in the reporting period.

  • Server calls

    • You must be an Analytics administrator or a user with the Server call usage permission in order to have access to server call usage.

  • Segments

    • When stacking two segments, they are by default joined by an AND statement. This cannot be changed to an OR statement.

  • Sequential Segments

    • A Logic Group can only be defined in a sequential segment, meaning that the THEN operator is used within the expression.

  • Publish Segments

    • Adobe Campaign (Classic and Standard) behaves differently in that it incurs an additional 24-hour latency on top of the 8-hour latency.

    • Once a week, all data will be fully synced to account for any deltas or discrepancies not captured in the previous week.

    • You cannot unpublish a segment that is currently in use by any of the following Adobe solutions: Analytics (in Audience Analytics), Campaign, Advertising Cloud (for Core Service & Audience Manager customers) and all other external partners (for Audience Manager customers). You can unpublish a segment that is in use by Target.

  • Statistical Tests

    • In all three tables, the difference statistic is based on an appropriate sample of visitors to make the process run as quickly as possible while remaining statistically accurate. While the difference score is based on a sample, the results presented in the table are not sampled. To ensure statistical significance, each statistical test relies on a dynamic allocation algorithm such that the smaller segment contains a sample size that provides less than 3% margin of error. If a segment contains very few visitors (less than 1,000), we use all available data and do not sample in computing the difference score.

  • Rule Builder 

    • The Rule Builder does not support Numeric 2 classifications.

    • As a best practice, regular expressions are best suited for tracking codes that use delimiters.

    • If the tracking code is URL encoded, it will not be classified by the Rules Builder.

    • In reports, classifications apply to any time frame specified, whenever a key exists. The date range of a report does not affect reporting.

    • Rule Set

      • In this procedure, you must apply the rules to one or more report suites. The recommended number of rules per rule set is between 500 and 1000, although there are no limits. If you have over 100 rules, consider simplifying your rule set by using sub-classifications.

    • Report Suites

      • Report suites display on this page only when the following conditions are met:

        • The report suites have at least one classification defined for that variable in Admin Tools. (See Variable in Classification Rule Sets for an explanation about this prerequisite.)

        • You selected the report suite on the Available Report Suites page, which displays after you click Add Rule Set to create the rule set.

    • If a key matches multiple rules that set the same classification (in the Set Classification column), the last rule that matches the classification is used. See About Rule Priority above for more information about sorting rules.

  • Event ID Serialization

    • Data Sources does not support event serialization or de-duplication.

    • If you want to de-duplicate the purchase event, use the purchaseID variable instead.

  • Classifications

    • Renaming a classification can cause issues with existing rules created in the Classification rule builder. If you rename a classification that has classification rules, make sure that you correct each rule so it points to the renamed classification.

    • Adobe recommends that you limit the number of import and export columns to 30.