CRM integration & data model — found from sitemap — Customer.io

Cited by

Facts read from this source

• Salesforce sync templates Report an error

  “When you set up your Salesforce integration, sync templates automatically configure common mappings for contacts, leads, accounts, and account-contact relationships.”

• Salesforce AI field suggestion Report an error

  “You can also use Agent to suggest fields based on your goals.”

• Salesforce typical mappings Report an error

  “People identify Contacts, Leads* Events track Tasks Custom Objects group Accounts, Opportunities, Automations, Leads* Relationships group Account-Contact Relationships, Opportunity-Contact Roles”

• Salesforce lead mapping options Report an error

  “Leads fill multiple roles in Salesforce, so you might map them to people, objects, or both.”

• Salesforce email identity Report an error

  “We identify leads and contacts by email address.”

• Salesforce id attributes Report an error

  “you should make sure that you store the lead_id and contact_id attributes in Customer.io.”

• Salesforce who id coalesce Report an error

  “you’ll use the coalesce function to use the contact ID if it exists, and fall back to the lead ID if it doesn’t in the format coalesce($.customer.contact_id, $.customer.lead_id).”

• Salesforce field rename Report an error

  “If you want to map a Salesforce field to an existing attribute in Customer.io, you can rename the field so it maps to your existing attribute instead of creating a new one.”

• Salesforce relationship attributes defaults Report an error

  “The Account-Contact Relationships sync template includes the Roles and IsActive fields by default.”

• Salesforce timestamp conversion Report an error

  “Set Convert dates to Unix timestamps to True. Then we’ll automatically convert incoming timestamps to Unix format to support Customer.io.”

• Salesforce reverse sync Report an error

  “If you want to send contact and lead data from Customer.io back into Salesforce, you’ll need to store Contact IDs or Lead IDs in Customer.io.”

• Salesforce relationship sync identifiers Report an error

  “The Field Containing Person ID to either the Contact ID or Contact.email The Field Containing Object ID to the Opportunity ID”

• Salesforce custom object name Report an error

  “The Custom Object Name is simply an attribute we set in Customer.io that tells us what kind of Salesforce data your object (or relationship) originates from.”

• Salesforce data types capabilities Report an error

  “If you want to send messages to it, or you want to log events it performs, it's a person.”

• Salesforce lead conversion model Report an error

  “When you qualify a lead in Salesforce, the record splits into those three things: a Contact related to an Account and an Opportunity.”

• Salesforce task event mapping Report an error

  “we suggest that you map tasks to events”

• Salesforce email uniqueness Report an error

  “By default, emails aren’t required to be unique in Salesforce, but they are required to be unique by default in Customer.io.”

• Salesforce resync rename behavior Report an error

  “If your sync is active, the rename takes effect at the next sync interval and applies to records that change from then on. To apply it to records you’ve already synced, resync all data.”

• Salesforce scheduled syncs Report an error

  “Scheduled syncs”

• Salesforce sync interval resync Report an error

  “Resyncing data only populates the new attribute with the values from the Salesforce field; it doesn’t remove the values from the old attribute.”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.