This is a core concept
You can enhance contact information by including ion Core Data in your integration. These descriptive behind-the-scenes data points are automatically available when a respondent visits an ion experience and can often map to existing external field(s). ion Core Data can be used in your target platform for qualification and/or correlation. This integration type aims to remain simple and should only require a small amount of work on your end, to ensure your target platform is ready to receive ion Core Data.
To view all Core Data fields available, check out the ion Glossary of Core Fields. Below are examples of Core Data fields commonly included in data integrations and how they can be leveraged.
CampaignLabel: When creating campaigns in ion, you'll add a label to describe the experiences you store within the campaign. You can strategically label campaigns so that the value gives your target platform context around what ion campaign the contact was generated from.
PathLabel: When publishing creatives in ion, you'll add a label to describe the experience. You can strategically label experiences so that the value gives your target platform context around what ion experience the contact was generated from.
GeoCountry: ion's geolocation tool saves the respondent's country location with 99% accuracy. You can leverage this field to export a country value to your target platform without collecting this field on your ion forms.
GeoRegion: ion's geolocation tool saves the respondent's region/state with 75% accuracy. You can leverage this field to export a region/state value to your target platform without collecting this field on your ion forms.
MediaName: When you create traffic source URL's in ion, you specify the media being used to drive traffic into the URL. The "category" drop-down menu is used to specify the media type (search, email, display, website, etc.) and this value can be included in your data integration to provide context around how the contact discovered the ion experience.
VehicleName: This value is a more granular indication of how traffic is being driven into your ion URL's. After selecting a "category", you'll specify a "sub-category" when creating ion URL's. If your category value is Search, your sub-category value could indicate the specific search engine, like Google. This value can be included in your data integration to provide deeper context around how the contact discovered the ion experience.
TrafficSourceQueryString: If you append tracking parameters to you ion URL's, you can leverage this core field to include the entire query string in your data integration.
Grade: You can use Rules to grade a respondent as they navigate through your ion experiences. If you strategically implement a grading system in ion, this value can be included in your data integration to be leveraged as an actionable data point your target platform.
Tags: Tag can be added to any actionable element in your ion experiences through Rules. If you strategically implement tags, you can include in your data integration a comma delimited list of the tagged actions the respondent took while navigated through the experience.
If you select an ion Core Data integration, you may need to create a limited number of fields in your target platform to receive these data points. The team here will collect the technical details needed, set-up and thoroughly test the integration. If you seek a more robust integration that includes Dialogue Data garnered from interactive content, a Global Dialogue Data or an Experience-Specific Dialogue Data solution could be a better fit. To learn more, please contact your Account Manager to get the ball rolling!