Before using Adobe Real-Time CDR a telecommunications company was directly uploading a segment of likely-to-churn customers from SalesForce Marketing Cloud into Facebook for its social campaigns every 7 days. Now, the company can stream this data into RTCDP for segmentation and share with the Facebook connector in near real-time.
Which two metrics can be tracked to calculate the value of RTCDP for this customer? (Choose two.)
Answer : B, C
Two metrics that can be tracked to calculate the value of RTCDP for this customer are time-to-market and CPA. Time-to-market measures how quickly the customer can reach their target audience with relevant offers and messages using RTCDP's near real-time segmentation and activation capabilities. CPA (cost per acquisition) measures how much it costs the customer to acquire a new customer or retain an existing one using RTCDP's data-driven optimization and personalization features.
An Adobe Real-Time CDP Business Practitioner wants to create a batch segment of users for a financial services client who opened account in the last rolling 30 days. The analytics team needs an updated segment count prior to a campaign launch.
What would the practitioner need to do to achieve this task?
Answer : C
According to the Adobe documentation, segment job is a feature that allows running an on-demand evaluation of segments using batch datasets and getting an updated segment count within minutes. Segment job can be used to achieve this task by selecting the segment and clicking on ''Run segment job'' from the action bar. Reference: https://experienceleague.adobe.com/docs/experience-platform/segmentation/ui/segment-job.html?lang=en
As a Real-Time Business Practitioner, it is required to create a custom merge policy in Adobe Experience Platform for an upcoming use case to ensure profile attributes to take precedence from latest datasets and are applied across all datasets automatically.
Which merge method should the practitioner select?
Answer : B
According to the Adobe documentation, timestamp ordered is a merge method that can be used to create a custom merge policy in Adobe Experience Platform for an upcoming use case to ensure profile attributes take precedence from latest datasets and are applied across all datasets automatically. Timestamp ordered merge method prioritizes profile attributes based on their ingestion timestamp, with newer values taking precedence over older values. Timestamp ordered merge method also applies globally across all datasets within a tenant. Reference: https://experienceleague.adobe.com/docs/experience-platform/profile/merge-policies/methods.html?lang=en#timestamp-ordered
A Real-Time CDP Business Practitioner is working with a client who requires automatic authentication Which type of ingestion should the practitioner choose?
Answer : A
According to the Adobe documentation3, batch ingestion is the type of ingestion that supports automatic authentication. Batch ingestion enables data to be ingested periodically from sources such as databases, cloud storage, or CRM systems.Batch ingestion also supports authentication methods such as OAuth 2.0, API key, or username and password. Reference:3https://experienceleague.adobe.com/docs/experience-platform/ingestion/home.html?lang=en#batch-ingestion
A banking and insurance company has "memberid" as the unique user id for customers who land on their website from Google organic search and authenticate.
Which namespace is recommended to fetch profiles for known customers?
Answer : C
According to the Adobe documentation, a custom namespace is a namespace that is created by the user to define a specific type or source of identity value that is not available in the predefined namespaces. A custom namespace for memberid would be recommended to fetch profiles for known customers who land on their website from Google organic search and authenticate, because memberid is a unique user id that is specific to this use case and not covered by any predefined namespace. Reference: https://experienceleague.adobe.com/docs/experience-platform/profile/identity-service/namespace.html?lang=en#custom-namespaces
A Real-time CDP business practitioner needs to determine how data will be prioritized and what data will be combined to create that unified view of a customer profile.
Which feature should be used?
Answer : A
According to the Adobe documentation, merge policies are a feature of Real-Time CDP that can be used to determine how data will be prioritized and what data will be combined to create a unified view of a customer profile. Merge policies define the rules and logic for merging profile attributes from different data sources into a single profile. Merge policies can be either predefined or custom, and they can be applied at the dataset level or the tenant level. Reference: https://experienceleague.adobe.com/docs/experience-platform/profile/merge-policies/overview.html?lang=en#merge-policies-overview
A Real-Time CDP Business Practitioner must create a new destination. As the final step in creating the new destination, they are unable to indicate the intent for which data will be exported to the destination.
What must they do in order to complete the new destination creation?
Answer : C
According to the Adobe documentation, if none of the predefined marketing actions match the intent for which data will be exported to the destination, the practitioner can create their own marketing action by selecting ''Other'' and providing a name and description for it. Reference: https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/destination-actions.html?lang=en#creating-a-new-marketing-action