QuestionQ46

VerifiedSection 3: Reporting and Attribution

An Adobe Marketo Engage customer recently adopted a new survey platform to measure Net Promoter Score (NPS). This platform has been in use for three months. Each month, the company sends survey invitations in a batch to an imported list of customers who meet certain criteria drawn from Salesforce Custom Object data. The company already has the native Salesforce sync configured. The invitation email is sent from Marketo Engage, and it currently links to the survey platform using a generic URL to start the survey. Because the link is generic, the company has no way to know whether a given customer actually completed the survey or what responses they submitted. Additionally, the company does not want to keep a history of NPS scores — they only want to know each customer's most recent NPS score.

Which three important architectural recommendations should an Architect suggest to scale this platform and its integration with Marketo Engage?

Choose three
Explanation

Automating the sync of relevant Salesforce Custom Object data and the triggering of survey invitations removes the manual monthly batching bottleneck, allowing the process to scale. Passing a unique customer identifier with each survey invite is required so that when the customer completes the survey on the external platform, their response can be matched back to the correct person record — without this, individual completions and responses can never be tracked. Because the business explicitly does not want to retain NPS history and only needs the latest score, survey responses should be integrated back into standard custom fields on the person record (which get overwritten with the newest value) rather than into a Custom Object, which is designed to store multiple, time-stamped related records and would introduce unnecessary complexity, added API consumption, and unwanted historical data.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!