Feb 11, 201911:11 AM - edited Feb 11, 201911:12 AM
Member
Associate customProperties and dealProperties w Contact during a Transactional Email
SOLVE
Thank you for your response.
"Deal properties can't be sent through this [Single-Send API/Transactional Email] API at all."
I'm surprised, because the Transactional Email is sent as a confirmation of the actual Deal (marketing campaign went out, the user clicked the link, and made a donation, and this Transactional Email 'receipt' is the result of the Donation 'Deal').
If the process of sending Transactional Email receipt doesn't help move towards a 'Deal' (as we were led to believe), then customers should be instructed on the blessed method of adding the transaction dealProperties to the Contact history.
We need to find out how to get that associated with the HubSpot Contact now, and we figured that since the Transaction is happening through HubSpot, it would be a done ‘deal’ if you forgive the pun.
Now we have hundreds? Thousands? of transactions that are not associated via dealProperties. Since we don’t require authentication before accepting a donation, we don’t know if they’re Contacts or not, until the 'Deal' is made.
We're working with HubSpot support on how to proceed, but I wanted to let others know that Transactional Emails are not linked to Contacts as Deals.
Associate customProperties and dealProperties w Contact during a Transactional Email
SOLVE
Hi @webmaestro , are you specifically using the Single Send API, and not the SMTP API? If you're using the Single Send API, from what you're describing it sounds like everything is working as expected. Contact properties sent through this API will update on a contact record if that contact property exists. Deal properties can't be sent through this API at all. Custom properties sent through this API are properties you want included in the email itself, but wouldn't either a.) make sense to hold in a contact property on a contact in HubSpot, or b.) you don't need to access as persisting contact property information on the actual contact record. If all of this info is necessary to be accessed via the contact record, you might want to create custom properties inside of HubSpot to store the information you're sending through the API, and send all/most info as contactProperties instead of customProperties.
Feb 11, 201911:11 AM - edited Feb 11, 201911:12 AM
Member
Associate customProperties and dealProperties w Contact during a Transactional Email
SOLVE
Thank you for your response.
"Deal properties can't be sent through this [Single-Send API/Transactional Email] API at all."
I'm surprised, because the Transactional Email is sent as a confirmation of the actual Deal (marketing campaign went out, the user clicked the link, and made a donation, and this Transactional Email 'receipt' is the result of the Donation 'Deal').
If the process of sending Transactional Email receipt doesn't help move towards a 'Deal' (as we were led to believe), then customers should be instructed on the blessed method of adding the transaction dealProperties to the Contact history.
We need to find out how to get that associated with the HubSpot Contact now, and we figured that since the Transaction is happening through HubSpot, it would be a done ‘deal’ if you forgive the pun.
Now we have hundreds? Thousands? of transactions that are not associated via dealProperties. Since we don’t require authentication before accepting a donation, we don’t know if they’re Contacts or not, until the 'Deal' is made.
We're working with HubSpot support on how to proceed, but I wanted to let others know that Transactional Emails are not linked to Contacts as Deals.