A company has a secure website that requires visitors to log in prior to accessing any content beyond the homepage. A visitor can log out manually, or their website will automatically log them out at the end of their browser session. The visitor must log back in to continue browsing.
The company has a business requirement to track the login status of their visitors.
Which three login statuses should the Architect recommend capturing? (Choose three.)
Answer : A, D, E
Business Requirement: Track the login status of visitors on a secure website.
Potential Login Statuses:
'Unregistered / Logged Out': Tracks users who have not registered or have logged out.
'Anonymous': Generally used for visitors who browse without logging in, but does not apply in a secure login-required context.
'Registered / Logged Out': Important for tracking users who have accounts but are currently logged out.
'Registered / Logged In': Essential for tracking active, logged-in users.
'Incomplete Registration': Useful for identifying users who started but did not complete the registration process.
'Unregistered / Logged In': Typically not applicable as unregistered users cannot be logged in.
Explanation:
'Unregistered / Logged Out': Helps in understanding the behavior of users who visit but have not completed registration or logged out.
'Registered / Logged In': Critical for identifying and analyzing the behavior of active users.
'Incomplete Registration': Helps in identifying and addressing barriers in the registration process.
Verification: According to Adobe Analytics best practices, capturing various login statuses helps in comprehensive user behavior analysis (Adobe Analytics User Guide).
While auditing an Adobe Analytics implementation, an Architect discovers that reports built using the Marketing Channel dimension show a large proportion of "None'' visits.
Which two steps should be taken to diagnose the problem? (Choose two.)
Answer : B, D
Overview of the Issue: The 'None' value in Marketing Channel reports indicates visits that are not attributed to any of the defined marketing channels.
Potential Diagnostic Steps:
Break down 'None' Marketing Channel by Tracking Code: This can provide insights but does not directly address the underlying configuration issues.
Review Marketing Channel Processing Rules: Ensures that the rules are correctly defined and applied. Incorrect or missing rules can result in visits being categorized as 'None'.
Review Marketing Channel Data Feeds: Useful for data validation but not for configuration troubleshooting.
Check that Internal URL Filters are configured correctly: Ensures that internal traffic is filtered out and does not interfere with marketing channel attribution.
Review Marketing Channel Data Connector settings: Relevant for integrations but not for basic processing rule configurations.
Explanation:
Review Marketing Channel Processing Rules: Essential to verify that all necessary rules are correctly set up to attribute visits to the correct channels.
Check that Internal URL Filters are configured correctly: Ensures that visits from internal sources do not affect marketing channel data, preventing incorrect attribution to 'None'.
Verification: According to Adobe Analytics Implementation documentation, reviewing processing rules and internal URL filters is crucial for accurate channel attribution (Adobe Analytics Implementation Guide).
A company wants to make their Adobe Analytics data GDPR-compliant. They collect gender and age data during registration.
Which privacy settings should the Architect apply to the two variables?
Answer : C
To make Adobe Analytics data GDPR-compliant, specific privacy settings need to be applied to the variables that collect personal data. The following privacy settings are relevant:
12: This identifier is for data elements that are directly related to individuals.
DEL-PERSON: This setting indicates that the data should be deleted if requested by the user under GDPR.
ACC-PERSON: This setting allows access to the data by the individual upon request.
By applying these settings to the variables collecting gender and age data, the company ensures compliance with GDPR regulations, allowing for the necessary control and access to personal data.
An Architect is implementing Adobe Analytics across 3 different websites using one Adobe Launch property. Each website is on its own domain and has its own report suite in Adobe Analytics.
What should the Architect do to determine the report suite IDs when pages load?
Answer : D
Business Requirement: Determine the appropriate report suite IDs for different websites using one Adobe Launch property.
Method:
Data Element: Utilizes a data element to dynamically determine and populate the report suite ID based on the domain or other contextual information.
Data Element: Provides flexibility to dynamically assign the correct report suite ID for each website based on defined conditions or context.
Verification: According to Adobe Launch best practices, using data elements to populate report suite IDs ensures accurate and context-specific tracking across multiple domains (Adobe Launch Documentation).
====
For internal search terms, a company wants to give credit to the original keyword used to find a product. On the first visit, a customer searches for "Mobile" and views the Nebulous Pro.
During the second visit, the customer refines this search to "5G Mobile" and views the Nebulous Pro again. The customer then purchases the Nebulous Pro for S200 on the third visit. The company wants "Mobile" to receive credit.
Which configurations should the Architect apply?
Answer : D
Business Requirement: The company wants to ensure that the original search term ('Mobile') receives credit for the purchase, despite subsequent searches.
Understanding Merchandising eVars: Merchandising eVars are used to attribute success events (like purchases) to specific values captured earlier (like search terms).
Allocation and Expiration Settings:
Original Value (First) Allocation: This setting ensures that the first value captured (in this case, 'Mobile') remains attributed to the visitor, regardless of subsequent values.
Expiration Setting: Setting the expiration to the purchase event ensures that the value ('Mobile') remains active until the visitor makes a purchase.
Explanation:
Configure an eVar as Merchandising Variable: This allows tracking specific values like search terms in relation to product views and purchases.
Original Value (First) Allocation: Ensures that the initial search term ('Mobile') gets credit.
Expiration to Purchase Event: Keeps the eVar value until the purchase is made, ensuring accurate attribution.
Verification: According to Adobe Analytics documentation on Merchandising eVars, using Original Value allocation with appropriate expiration settings ensures correct attribution of original search terms to final purchases (Adobe Analytics Implementation Guide).
A retail company is tracking the following:
* An event for clicks on navigation
* An eVar for navigation items clicked on
* A conversion syntax merchandising eVar tracking navigation as a product finding method (PFM)
The company is in the beginning stages of a site redesign and wants to optimize their navigation system.
Before they can optimize, the company needs to benchmark how effectively their current navigation system brings visitors deeper into the site to find products.
Which metric should the Architect use?
Answer : C
To benchmark the effectiveness of the current navigation system, the Architect should look at the navigation usage rate per visit. This metric, calculated by multiplying the number of navigation clicks by the number of visits, provides insight into how often visitors are engaging with the navigation system on a per-visit basis. It helps to understand the relative frequency of navigation usage, which is crucial for optimizing the system and ensuring that it effectively helps users to explore the site and find products.
An Architect has defined the following tracking specifications:
* A userlD variable must be set in the data layer
* The userlD value must be mapped to eVar5
* The userlD value must be used as the Adobe visitor identification method.
The tagging engineer confirms that Adobe Launch is configured as requested.
An Analyst notices that the eVar5 report is not being populated.
The Architect can see that the userlD data object is populated in the data layer after the page loads.
What is causing this problem?
Answer : A
Business Requirement: Ensure userID is set in the data layer and mapped to eVar5, and used for visitor identification.
Issue Identification:
The userID data object must be available in the data layer before the Adobe Launch rule executes.
Explanation:
visitorID is not available in the data layer when the Adobe Launch rule runs: If the visitorID is not present in the data layer at the time the rule executes, the mapping to eVar5 will not occur, resulting in an empty eVar5 report.
Verification: According to Adobe Launch documentation, the timing of data layer availability is crucial for rule execution. Ensuring data is present before rules execute is necessary for accurate data capture (Adobe Launch Implementation Guide).