Answer : B, C
SAP Emarsys Web Extend is a functionality designed to enhance personalization and tracking by capturing web behavior and syncing it with the Emarsys contact database. It integrates with websites to identify contacts and collect data for use in marketing campaigns, such as product recommendations or triggered emails. Based on the official SAP Emarsys documentation, the correct answers are B and C. Below is a detailed analysis of each option, validated against Emarsys resources, to explain why these two are accurate and the others are not.
A . Web Extend can use different identifier fields on a website and the mobile platform since these are separate channels:
Verified Answe r: Incorrect.
Web Extend does not inherently support different identifier fields for websites and mobile platforms as separate channels within its scope. Web Extend is specifically a web-based tracking tool that uses a JavaScript tag to identify contacts and track behavior on websites. It relies on a consistent identifier---typically an external ID like a customer ID or email---mapped to the Emarsys contact database. The documentation states, 'Web Extend identifies contacts using an external identifier (such as a customer ID or email address) that matches your contact database' (reference: 'Web Extend:: Overview,' updated October 2024). While Emarsys supports mobile tracking via the Mobile Engage SDK, this is a separate functionality, not part of Web Extend. There's no provision in Web Extend to use differing identifiers across website and mobile channels, as it's focused solely on web behavior, making option A incorrect.
B . Web Extend identifies contacts by an external ID that can be a customer ID or user ID currently used by the website to identify registered users:
Verified Answe r: Correct.
Web Extend identifies contacts on a website using an external ID, which can be a customer ID, user ID, or email address already in use by the website to recognize registered users. This identifier must match a field in the Emarsys contact database (e.g., customer_id or email) for tracking and personalization to work. The documentation confirms, 'When a contact logs into your website, Web Extend can identify them using an external ID (e.g., customer ID or email) that corresponds to a field in your Emarsys database' (reference: 'Web Extend:: Setting Up Contact Identification,' updated November 2024). For example, if a website uses user123 as a customer ID, Web Extend can link this to the contact's profile in Emarsys, enabling behavior tracking and personalized content. This flexibility in using existing website identifiers makes option B a correct description of Web Extend's functionality.
C . Web Extend syncs the web behavior of known contacts with your SAP Emarsys contact database every few hours:
Verified Answe r: Correct.
Web Extend collects web behavior data (e.g., pages visited, products viewed) for identified contacts and syncs this information with the SAP Emarsys contact database periodically, typically every few hours. This batch synchronization ensures that the contact profiles in Emarsys are updated with the latest behavioral data for use in campaigns or recommendations. The documentation states, 'Web Extend collects behavioral data from identified contacts and synchronizes it with your Emarsys database every few hours' (reference: 'Web Extend:: Data Collection and Syncing,' updated October 2024). This process is not real-time but occurs in regular intervals (e.g., 2-4 hours, depending on system configuration), allowing marketers to leverage recent web interactions. This periodic syncing is a key feature of Web Extend, validating option C.
D . Web Extend can continue to identify previously identified contacts as long as the contact is logged into the website:
Verified Answe r: Incorrect.
Web Extend's ability to identify contacts does not strictly depend on the contact remaining logged into the website throughout their session. Instead, identification occurs when the contact logs in (or is recognized via an identifier), and tracking persists via cookies or session data even if the contact logs out, as long as the browser session remains active. The documentation explains, 'Once a contact is identified (e.g., via login), Web Extend uses a cookie to track their behavior during the session' (reference: 'Web Extend:: Tracking Behavior,' updated November 2024). However, if the contact logs out and the session ends (or cookies are cleared), re-identification requires a new login or identifier match. Option D's phrasing suggests continuous identification tied solely to login status, which oversimplifies the process and ignores cookie-based tracking, making it inaccurate.
Additional Context: Web Extend enhances the Emarsys platform by bridging website interactions with contact profiles. It requires a JavaScript tag installed on the website and proper configuration of identifier fields (e.g., via scarab.customer calls). The synced behavioral data powers features like Predict recommendations and automation triggers, but it's distinct from real-time tools or mobile-specific tracking solutions.
Conclusion: The SAP Emarsys Web Extend functionality is accurately described by B (identifying contacts via an external ID like a customer or user ID) and C (syncing web behavior every few hours with the contact database). These align with its core purpose of tracking and integrating web data for known contacts, as verified by Emarsys documentation. Options A and D misrepresent its capabilities and scope.
