This article guides you through the process of aligning the field names, data types, and specific data content provided by DNA Behavior with the corresponding fields in your application.
Integrating your systems with DNA Behavior through Zapier opens up a world of possibilities for automating and enhancing your behavioral data workflows. However, the crux of a successful integration lies in the meticulous data mapping process. It's a fundamental step that can't be overlooked because even the slightest misstep can reroute your data to unintended destinations or prevent your Zaps from functioning altogether.
DNA Behavior's integration with Zapier features two "Zaps", both provide the same set of data, or as developers call it, "the payload." This payload, comprising structured JSON format data, is handled by Zapier to offer a seamless and user-friendly interpretation, thereby eliminating the need for prior coding knowledge.
Create custom fields in third-party apps:
To successfully integrate and automate processes between DNA Behavior and your third-party application, you'll need to ensure that your application is setup to accept the data. This means meticulously creating corresponding fields within the third-party application to receive the incoming data.
Choosing the data to sync:
It is not a requirement to synchronize all available data. Users have the flexibility to selectively determine which specific data fields are pertinent for their integration purposes. This selective data sync allows for a more streamlined and relevant transfer of information to your third-party application, ensuring that only the necessary data is captured and processed.
Decide on a method of record matching:
When setting up your Zap, it's imperative to establish a method of matching records between DNA Behavior and your external application. Typically, this is accomplished by using a unique identifier that is consistent across both platforms. In most cases, the client's email address serves as this unique identifier. It's crucial to map the email address field correctly between DNA Behavior and your third-party app to ensure that the data is associated with the correct client records. This step is essential for maintaining data integrity and facilitating a seamless integration process.
Categories of data available:
The DNA Behavior to Zapier integration offers two key data categories. Participant Data provides essential identifiers like Person ID, names, Email, Language, Credit ID, and Tags. DNA Insights reveal behavioral profiles with Unique Style, Financial and Business DNA 5-scores, and Communication Keys. These categories combine demographic specifics with behavioral insights to inform user engagement.
Learn more about the DNA Insights available:
- Unique Style
- Financial DNA 5-scores (Financial Behavior)
- Business DNA 5-scores (Work Talents)
- Communication Keys
Fields available:
The table provided below details the complete range of fields transmitted from DNA Behavior to Zapier. The "Field Name" column specifies the name of the data attribute, serving as a key identifier for each piece of data sent. The "Data Type" column clarifies the format of the data, indicating whether it's a Text String, Number, etc., to ensure proper handling and integration in your processes. Lastly, the "Example Data" column offers a glimpse into the actual data as represented in the DNA Behavior system, giving you illustrative insights into what to expect in each field. It's important to closely align these fields with the corresponding fields in your third-party app to facilitate a seamless data transfer.
Field Name | Data type | Example Data |
PersonId | Alphanumeric string | 9f167be9-0625-4db8-b399-1a765dc8151b |
FirstName | Text String | Lily |
LastName | Text String | Michelle |
Email Address | lily.michelle@gmail.com | |
Unique Style | Text String | Community Builder |
LanguageID | Number | 22 |
CreditID | Number | 384 |
TagsList | Comma Separated List | Participant |
FDNA5Scores: RiskBehaviorValue | Number | 24 |
FDNA5Scores: RiskBehaviorDescription | Text String | Safely manages risks and able to see pitfalls |
FDNA5Scores5Scores: FinancialRelationshipManagementValue | Number | 90 |
FDNA5Scores5Scores: FinancialRelationshipManagementDescription | Text String | Delegates to advisers and relationship driven |
FDNA5Scores5Scores: FinancialPlanningManagementValue | Number | 12 |
FDNA5Scores5Scores: FinancialPlanningManagementDescription | Text String | Desire to spend and appreciates spending freedoms |
FDNA5Scores5Scores: WealthBuildingMotivationValue | Number | 2 |
FDNA5Scores5Scores: WealthBuildingMotivationDescription | Text String | Prefers flexible goals and is often OK with a content life |
FDNA5Scores5Scores: FinancialEmotionalIntelligenceValue | Number | 10 |
FDNA5Scores5Scores: FinancialEmotionalIntelligenceDescription | Text String | Has emotional impulses and makes spur of the moment decisions |
BDNA5Scores: ResultsVsRelationshipsValue | Number | 90 |
BDNA5Scores: ResultsVsRelationshipsLabel | Text String | Relationships |
BDNA5Scores: ResultsVsRelationshipsDescription | Text String | Patiently builds relationships with others |
BDNA5Scores: DaringVsCarefulValue | Number | 76 |
BDNA5Scores: DaringVsCarefulLabel | Text String | Careful |
BDNA5Scores: DaringVsCarefulDescription | Text String | Cautious and calculated in making decisions |
BDNA5Scores: AbstractVsConcreteValue | Number | 76 |
BDNA5Scores: AbstractVsConcreteLabel | Text String | Concrete |
BDNA5Scores: AbstractVsConcreteDescription | Text String | Works with known pathways forward |
BDNA5Scores: SystematicVsFlexibleValue | Number | 84 |
BDNA5Scores: SystematicVsFlexibleLabel | Text String | Flexible |
BDNA5Scores: SystematicVsFlexibleDescription | Text String | Will be flexible in approach but may not prepare or be organized enough |
BDNA5Scores: PromotingVsOperatingValue | Number | 59 |
BDNA5Scores: PromotingVsOperatingLabel | Text String | Promoting |
BDNA5Scores: PromotingVsOperatingDescription | Text String | Engaging and relational with others but also enjoys operating alone |
CommunicationKey1: EnvironmentKey1ID | Number | 110 |
CommunicationKey1: EnvironmentKey1Description | Text String | Focus on my life balance needs |
CommunicationKey2: EnvironmentKey2ID | Number | 111 |
CommunicationKey2: EnvironmentKey2Description | Text String | Keep the conversation easy-going |
CommunicationKey3: EnvironmentKey3ID | Number | 112 |
CommunicationKey3: EnvironmentKey3Description | Text String | Give me the directions to move forward |
CommunicationKey4: EnvironmentKey4ID | Number | 38 |
CommunicationKey4: EnvironmentKey4Description | Text String | Remember my desire to be included |
CommunicationKey5: EnvironmentKey5ID | Number | 39 |
CommunicationKey5: EnvironmentKey5Description | Text String | Keep the conversation with me friendly |
Access our Google Sheets template:
If you're venturing into constructing a DIY Zap, our team recommends initiating the process with Google Sheets as a preliminary integration point. Google Sheets serves as an ideal sandbox environment to collate and interact with all data points from DNA Behavior before progressing to a more intricate third-party application with a complex field structure and dependencies.
This approach allows you to test and confirm the flow of data in a more controlled and forgiving setting, ensuring that each piece of data lands in the right place. Once you've established that the information is syncing correctly with Google Sheets, you can then move on to integrate with your desired application, confident that your data mapping is accurate. To streamline this process, below is a Google Sheets template designed to help you effectively sync and organize your DNA Behavior data.
Download the Google Sheets Template.