#Email Marketing3 人正在讨论

The approaches mentioned above (API + Automation Studio, webhooks, or middleware) are all valid. 👍 I'd just add a few considerations based on webinar setups I've seen over time.

If Zoom is already a fixed requirement, I'd like @EDGAR Joes suggests, lean towards webhooks or scheduled API syncs over relying heavily on middleware logic/third party apps like Zapier. Keeping Marketing Cloud responsible for segmentation and journeys, while treating the webinar software as the source of engagement data, tends to be easier to maintain.

If you're still evaluating the webinar platform itself, it's also worth looking at solutions with native Salesforce integrations (for example Univid) that can pass registrations, attendance, watch time and other engagement signals directly into the Salesforce ecosystem, instead of building/maintaining the integration yourself. That can reduce the amount of custom integration work over time, as things update and change.

Curious what approach you ended up taking.

Subscriber Key Mapping: When creating a Sendable Data Extension, you must define which field relates to the Subscribers > Subscriber Key. If you accidentally map a field that doesn't exist in All Subscribers, or if you fail to set this relationship at all, the "send" will find 0 valid targets and effectively fail to deploy.

Correct answer is C - '

We used to have a similar setup (picklist lead source field in Salesforce, populated by our marketing automation tool) and found it was pretty much useless when it came to actually running reports and understanding where our leads were coming from.

The problem with a single "Lead Source" picklist is that it tries to do too many things at once. Is "Inbound - LinkedIn" referring to someone who came from a LinkedIn ad? An organic LinkedIn post? And what about the context of how they converted, or what page they landed on? 

We ended up switching to a three-field setup that gave us way more insight: 

The first set of fields we called "Lead Source" and "Lead Source Detail", and they captured information about how the person became a lead. So if someone filled out a Get a Quote form, it would be something like Lead Source = Web, Lead Source Detail = Get a Quote. If they downloaded an eBook, it would be Lead Source = Content, Lead Source Detail = Name of the eBook. We populated these using Pardot completion actions or automation rules based on which form was submitted. 

The second set of fields were what we called the Channel fields (Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3). These captured where the person came from, so they'd be populated with values like Organic Search, Paid Search, Paid Social, etc. along with further detail like the campaign name, ad group, keyword, etc. These were populated by a tool called Attributer. It tracked where people came from when they first landed on the site, stored it in a cookie, and then passed it through with each form submission. 

The third set of fields were Landing Page and Landing Page Group. These tracked the first page the visitor landed on. So it might be something like Landing Page = yoursite.com/blog/example-post

and Landing Page Group = /blog. These were also populated by Attributer and helped us understand what content on our site was actually generating leads. 

With these three sets of fields together, we could look at a lead and see the full picture. Like, this person came from our Google Ads, landed on our pricing page, and requested a quote. Or this person came from Organic Search, landed on a blog post, and downloaded an eBook. Those two leads are very different, and it was really useful to be able to separate out the high-intent leads from the content leads that were probably never going to convert into customers.

Hope this helps

Aaron