Schema Reference
The application schema is used to configure the objects returned from a connector.
Note
-
The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.
-
The schema attributes that are not present by default must be defined as strings if not specified.
The Drip connector uses the following default correlation and object configurations.
Default Account Schema
Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.
The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.
Default Account ID
SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.
Caution
Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
To resolve issues caused by changing account IDs, reconfigure them to their default values.
The following table lists the default account IDs for this connector:
| Account ID | Schema Object Type |
|---|---|
| id | Account |
Default Account Attributes
The Drip connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
| Attribute Name | Description |
|---|---|
| Utc Offset | UTC offset for the contact's time zone |
| Country | Country of the contact's address |
| City | City of the contact's address |
| Created At | Timestamp when the contact was created |
| Lifetime Value | Lifetime value of the contact |
| State | State or province of the contact's address |
| First Name | First name of the contact |
| Email address of the contact | |
| User Agent | User agent string from the contact's browser |
| Zip | ZIP or postal code of the contact's address |
| Address2 | Secondary address line of the contact |
| Eu Consent Message | EU consent message associated with the contact |
| Address1 | Primary address line of the contact |
| Custom Fields | Custom fields associated with the subscriber in Drip |
| Last Name | Last name of the contact |
| Base Lead Score | Base lead score of the contact |
| Ip Address | IP address associated with the contact |
| Time Zone | Time zone of the contact |
| Original Referrer | Original referrer URL that brought the contact to the site |
| Landing Url | Landing page URL where the contact first arrived |
| Tags | Tags assigned to the contact for segmentation |
| Prospect | Whether the contact is marked as a prospect |
| Sms Consent | Whether the contact has given SMS consent |
| Lead Score | Current lead score of the contact |
| Phone | Phone number of the contact |
| Visitor Uuid | Unique visitor identifier for tracking purposes |
| Sms Number | SMS phone number for the contact |
| Status | Current status of the contact in Drip |