#Pardot B2b Marketing Automation36 人正在讨论

@Adam Erstelle

sorry to bug you here again! 

We're about to try and implement this and I have one question: what if there is no Lead/Contact ID at the time of the form submission? In other words, they're a new Prospect and not synced to Salesforce, but then 2 minutes later the record syncs to SF and we get an ID, but the FLOW already ran and created the form submission record. How would we related the form submission custom object to their record in Salesforce then?  

Thanks!

1. User License: Our Pardot users currently have a Chatter/Chatter Free-type license. What license is actually required for Pardot Lightning access — will Chatter-licensed users work, or do they need to be upgraded first? 
   If you are referring to an "identity" license, these still work, but it still retains the limitations in that you can't access certain necessary features, like Salesforce campaigns. Ideally admins should have full salesforce licenses. 
2. Pre-Migration Checklist: What key things should we check or prepare before starting the switch — any pre-migration steps people often overlook? 
   Normally what trips people up is getting the visibility of the app to the correct profiles.  Follow the setup instructions carefully.  Also the user/role mapping if you migrate Account Engagement user management to Salesforce is quirky.  You still map profiles to roles in AE, but there's a whole different mapping in Salesforce. This article has some good tips.  
3. Existing Assets: Will our current email templates, forms, prospects, scheduled email for campaigns, and email domains carry over automatically, or do some need manual migration? 
   There's really no change. It's just looking at the same data in a different interface. However, going on lightning also gives you access to the new CMS, landing page and email builders (which also have to be configured and access given to your users). These are in addition to, not replacing, the current Pardot resources. 
4. Sales Cloud Impact: Does this migration affect our existing Sales Cloud (Lightning) production data in any way? 
   Only that there's a new Account Engagement App for the people that use it. 
5. Classic Access Post-Migration: After Lightning is set up, will pi.pardot.com (Classic) still be accessible, or is it fully deprecated at that point? 
   Yes. 
6. Nonprofit Cloud Compatibility: Is Pardot Lightning compatible with Nonprofit Cloud orgs? Does the setup/migration process work the same way as it does for a standard Sales Cloud org?  
   I would think so but I am not certain of that. 

hello  

I find this articles 

may be it's going to help you. 

regards

Hi @Sam Vanrintel

appreciate the response here!  

The other item to note about forcing MCAE/SF to generate a new Lead (always) is that this will create duplicate records, which will split engagement data + can create a mess quickly (if Sales isn't merging records correctly)  

Yeah... I think this is the last missing piece for Campaign Influence. Campaign Influence will never be perfect and to me it's used more for trends, but to me this is a big missing piece. I thought of updating the Campaigns regularly as well, but that creates more admin. burden/risk of missing one (I will note that sites can have many generic pages with request more information/consultation forms that sit for a while) + isn't the 100% solve as we could get Prospects submitting the same form multiple times before we create a fresh campaign and associate it to the content.  

The Flow is a good idea to automatically create new campaigns for  "always on" campaigns. We'd just need to remember to associate the new campaigns to the applicable content in MCAE.  

One idea I have is to create SF Tasks from MCAE. With that, use External Actions to create a File/Note on the task of the form submission + define the task subject line (use a Flow). Then, we align the task status field (or custom field) that Sales uses to work the "re-engagement". If the status/custom field reaches a certain stage, then an Opportunity is automatically created using a Flow + the task is related on the activity. With using naming conventions, we can report on Activity (Tasks/Subject Line) + Opportunities. We would then use both Campaign Influence + this Task reporting to get the full view.  

Another possible idea would be to send the campaign information when the External Action is executed in MCAE and associate it to the SF Task using a custom field, then the campaign could be auto-populated on a custom field on the Opportunity if the specific status/custom field reaches a certain stage on the Task. With this set-up, the custom campaign field on the Opportunity works the same way as the PCS model, but we include a time frame on the custom field to make this more accurate as the PCS field takes whatever campaign is the most recent create date.  

Added this to the IdeaExchange -

Thanks!

Using tools like Zapier to send conversions to the LinkedIn conversions API isn’t ideal. The reason is that although you can send the basic lead details like name, email, and phone number via Zapier, LinkedIn's conversions API (and the Meta conversion API, Google Ads, and all of the others) all basically need browser-based information like the LinkedIn click ID, the IP address, the user agent, and a whole bunch of other stuff to really get a good match rate between the initial ad click and the actual conversion that happened. 

This is because if you're just sending name and email, there isn't quite enough information there. Millions of people have the same name and quite often the email address that they are entering into your form might not match the email address that they use for their LinkedIn account. If you combine the name and the email with the LinkedIn click ID, the IP address, and all that other stuff, then you get close to 100% match rate. 

You can of course custom code this yourself to capture the LinkedIn click ID, the IP address, the user agent, and stuff in Salesforce and then send it back via Zapier, but there are tools like Converly which do this for you out of the box. They integrate with hundreds of different form builders, including Pardot and Salesforce web2lead forms, and they'll grab the name, the email, and phone number. They'll also grab the LinkedIn click ID, the IP address, the user agent, and send it all over to LinkedIn's conversions API for you