#AccountEngagement2 personnes en discutent

@Patience Adaobor

Hi Patience,

Certification preparation are great ways to start. There are two Account Engagement certifications : Specialist and Consultant. Following the Specialist preparation trailmix (every cert has an associated trail mix to guide you through the prep.) is a good start.

Hope this helps 😎

#SharingIsLearning #AccountEngagement 

François.

PS : In order other Trailblazers to be pointed directly the correct answer, please do not forget to click “Accept this answer” below the correct one.

@alexandre lavorel

Hi Alexandre, 

I'd suggest you leverage the Exit Rules of the Segment Triggered Flow (remove a Unified Individual from the Flow interview when a set of condition is met, like a member status). 

Hope this helps 😎 

#SharingIsLearning #AccountEngagement

François. 

PS : In order other Trailblazers to be pointed directly the most helpful answer, please do not forget to click “Accept this answer” below it. 

@SUNNY PATWA This isn't really helpful at all.  We get the same error simply when dragging the OOTB  Pardot (MCAE) "Engagement Metrics" component onto a Campaign Lightning Record Page.  There is nothing to "check" here, nowhere to enter ID's or anything configure, etc.  You're already on the Campaign record page in Lightning App Builder, so it should be inheriting/pulling the recordId from that page (which is a valid and active Campaign). Note also that the component itself seems to render fine -- it's just an error thrown in Lightning App Builder when dragging the component onto the page or refreshing the page. 

I also tried manually removing every single Metric Type element in the component and resaving, and it still throws a single error (instead of one for each Metric Type):

Error creating info component: Failed to initialize a component [An invalid record ID was supplied: 'undefined'] 

D.error()@

https://[OrgName].lightning.force.com/auraFW/javascript/REdtNUF5ejJUNWxpdVllUjQtUzV4UTFLcUUxeUY3ZVB6dE9hR0VheDVpb2cxMy4zMzU1NDQzMi41MDMzMTY0OA/aura_prod.js:1032:298

eval()@

https://[OrgName].lightning.force.com/components/builder_framework/visualEditorInfoComponentWrapper.js:2:175

As I am not a developer, this is mostly gibberish to me... I'm a Salesforce Admin with MCAE admin access ('Marketing User' is checked on my Profile and I'm in the Account Engagement User profile and can access and admin Pardot without issues). 

Instead of providing canned troubleshooting responses, can someone provide the actual root cause of this seeminly out-of-the-box Marketing Cloud Account Engagement (MCAE) component error in Lightning?

@Deekshita M - Did you or anyone else here ever find the real root cause? 

#AccountEngagement #Pardot B2b Marketing Automation #Pardot Lightning App #MCAE

@Aishwarya Pawar

Hi! 

1. Not yet, but coming. 

2. It may be better to wait for BUs 

3. Not easily as-is, so far there are no custom preferences center (they are coming too) 

4. You can create multiple Workspaces and manage access per user (however the campaign templates will generate assets into the default one, created during setup) 

Hope this helps 😎 

François. 

PS : In order other Trailblazers to be pointed directly the correct answer, please do not forget to click “Accept this answer” below the correct one.

@Patrik Lundgren

Hi Patrick,  

If you add Fields to the Individual DMO, they will be added to the Unified Individual DMO by the identity resolution process and you will be able to define what value will be used for the Identity Resolution (last modified, source priority, etc). 

If you keep the fields on the related object, you will have to define what to display when used as Merge Fields. I'd say extend your Unified Individual model with Fields that are mandatory for the business and keep others in related objects. 

To your last point, previous emails will keep being bound to the previous DG after you change the default. 

Hope this helps 😎 

François. 

PS : In order other Trailblazers to be pointed directly the most helpful answer, please do not forget to click “Accept this answer” below it.

@Patrik Lundgren

Hi Patrick, 

Yes, there is a solution. 

You will simulate the "Wait for Click" activity, by taking advantage that MCG/A stores the Engagement information in the "Email Engagement" DMO. This idea is to send the email, wait for some minutes and then check for a link click in the DMO. If you find a record in Data Cloud, the user is DOI, else you may resend an email. See screenshot. 

Hope this helps 😎 

#SharingIsLearning #AccountEngagement

François. 

PS : In order other Trailblazers to be pointed directly the most helpful answer, please do not forget to click “Accept this answer” below it.