Thnks Data Model
Thnks Object

Thnks Record Creation
The following events trigger a change on the Salesforce side (either creating or updating records):- A new Thnks is sent
- The status of an existing Thnks is changed (e.g. opened, undelivered, redeemed, etc.)

- Is there a Contact to match?
- If no Contact is found, is there a Lead to match?
- If a Contact is found, is there an open Opportunity to match?
Thnks Record Updates
After the initial Thnks is sent and the subsequent Thnks record in Salesforce is created (and potentially a Task), there will be no additional new records being created. Instead, all that will be changing is the Status field (API name of thnksdev1__RecipientTransactionStatus__c) on the Thnks record whenever the status on the Thnks side is updatedTask Logging for Thnks
If you have enabled “Task Syncing” in the Configuration tab, then every time a Thnks is sent, a Task will be automatically generated. There are two standard fields on Tasks for association with other records: Name and Related To (API Names of WhoId and WhatId, respectively). The WhoId (Name) field can only be related to Leads or Contacts. The WhatId (Related To) can be related to any other object. For our purposes, the WhatId will always be related to the Thnks record.- If the Thnks is associated with a Lead, then the Task will only be associated with the Thnks record via the Related To field (WhatId). The WhoId cannot be used in this scenario due to Salesforce limitations.

Task for a Thnks Record Associated with a Lead
- If the Thnks is associated with a Contact, then the Task will be associated with the Thnks record via the Related To field (WhatId), as well as the Contact via the Name (WhoId) field.

Task for a Thnks Record Associated with a Contact
- If the Thnks is not associated with a Lead nor a Contact, then the Task will only be associated with the Thnks record via the Related To field (WhatId),