Skip to content

Commit

Permalink
Update contact-and-lead-matching.md
Browse files Browse the repository at this point in the history
  • Loading branch information
dwhitig authored May 21, 2024
1 parent 0baeabb commit 599f64c
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion docs/advanced-features/contact-and-lead-matching.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,5 @@ has_children: true
Registration information is always stored in the Registration object. Optionally, you can also attach registration information to a Contact or Lead or create a new Contact or Lead if needed. When associating registrations to Contact or Lead record, you'll want to setup the Contact and Lead Matching information on your Summit Event. Use the Table of Content links below to explore how to setup Contact or Lead matching.


*Note: This is optional functionality, if your organization does not want to match Summit Events Registration records with Contacts or Leads then this information does not apply.*
*Note: This is optional functionality and not required for Summit Events to function. If your organization does not want to match Summit Events Registration records with Contacts or Leads then this information does not apply.*
**IMPORTANT: Currently Summit Events contact matching feature DOES NOT support person accounts. If your instance uses person accounts, do not enable contact matching. Person accounts will be addressed in a future release.**

0 comments on commit 599f64c

Please sign in to comment.