Order of operations during event registration processing

To help in troubleshooting challenges during the setup process, we've outlined the order of operations that happens when an event registration is processed using a Events app page.

1. If applicable, a payment request is sent to the payment gateway for approval
2. If applicable, the payment gateway response is sent back to Soapbox Engage
3. If applicable, if the payment was approved, Soapbox Engage prepares to send data to Salesforce
4. Soapbox Engage creates a Lead record in Salesforce
5. Soapbox Engage creates Ticket_Temp__c records in Salesforce, one for each ticket purchased
6. Soapbox Engage creates a Campaign Member record in Salesforce
7. An after insert trigger on the Campaign Member object fires in Salesforce
8. The Lead conversion process begins based on the previous trigger
9. An Account record is created, if applicable, as part of Lead conversion in Salesforce
10. A Contact record is created, if applicable, as part of Lead conversion in Salesforce
11. An Opportunity record is created as part of the Lead conversion in Salesforce
12. An after insert trigger on the Opportunity object fires in Salesforce
13. Based on the previous trigger, the Ticket_Temp__c records are moved to the Ticket__c object and related to the newly created Opportunity
14. The Lead record is updated, as part of the Lead conversion in Salesforce
15. An after update trigger on the Lead object fires in Salesforce
16. Data from the updated Lead record is sent back to Soapbox Engage
17. Soapbox Engage's Events app sends the registrant to either the redirect page or the thank you page
18. If applicable, confirmation emails are sent