A company wants to report on the internal search keywords and their contribution to the revenue.
The Architect instructs the developer to create the digitalData.search.keyword'' data object in the data layer so it can be
mapped to eVarl.
Which syntax should the Architect recommend?
A)
B)
C)
D)
Business Requirement: The company needs to report on internal search keywords and their contribution to revenue by creating the digitalData.search.keyword data object in the data layer.
Recommended Syntax: The syntax must be correctly structured to allow Adobe Analytics to map the data object to eVar1 efficiently.
Explanation:
An Architect needs to create a segment of users that started a visit from a campaign and completed an order.
A specific product demo page and coupon page can be viewed in any order between the landing page and the order confirmation page.
What should the Architect use to meet the requirements?
In Adobe Analytics, non-sequential segments allow for the inclusion of conditions that do not necessarily occur in a specific order. Since the specific product demo page and coupon page can be viewed in any order between the landing page and the order confirmation page, non-sequential containers are the appropriate choice. They allow for the creation of a segment where users must have started their visit from a campaign and completed an order, without enforcing a strict sequence for intermediate steps.
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?
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.
A company has an email marketing tool that is used for both SMS and email.
The tool generates the following campaign URLs:
SMS link: www.website.com?cid=em:campaign_name-txt Email link: www.website.com?cid=em:campaign_name
How should the Architect configure Marketing Channel Processing Rules to identify the SMS channel?
Business Requirement: Distinguish between SMS and email campaigns using the 'cid' query string parameter.
Configuration Steps:
Identify SMS Links: Using the query string parameter 'cid' ending with '-txt'.
Processing Order: Ensuring the SMS channel is processed before the email channel.
Explanation:
Query String Parameter 'cid' Ends with '-txt': This setting ensures that any link containing 'cid' ending with '-txt' is identified as an SMS link.
Processing Order: Placing the SMS channel rule above the email channel ensures that SMS links are correctly categorized before the system checks for email links.
Verification: According to Adobe's Marketing Channel Processing Rules documentation, properly configuring query string parameters and processing order is crucial for accurate channel attribution (Adobe Analytics Marketing Channel Processing Rules Guide).
A new business requirement is submitted to start capturing the shipping cost of each order. After updating the product string on the confirmation page to collect the shipping cost in event1 00, no results show up for this event in Adobe Analytics.
s.products = ";car stereo;1;820;event100:123=23
Which code change should be made?
The issue in the original code lies in the incorrect placement of the event syntax. In Adobe Analytics, when defining events in the product string, the correct format must be followed to ensure the event is captured properly. Specifically, there needs to be a double semicolon (;;) before the event definition.
The corrected code s.products = ';car stereo;1 ;820;;event100=23' ensures that the event is recognized correctly by Adobe Analytics.
