Overview: Basic/Core Integration Field Menu

Basic lead data is information typically collected via a lead form — things like name, email address, and phone number.

Core Data is descriptive, behind-the-scenes information automatically collected when a respondent visits an ion experience. You can learn more about Core Data here.

Query string data is information passed to ion via a query string on the URL — such as UTM or other source tracking parameters.

BASIC LEAD DATA

ion field name	description	sample data	core?
FirstName	First name	John	no
LastName	Last name	Smith	no
EmailAddress	Email address	[email protected]	no
Phone	Phone number	617-555-1212	no
Fax	Fax number	617-555-1212	no
ContactPreference	Method by which respondent prefers to be contacted	email	no
Title	Job title	Marketing Technologist	no
Organization	Organization or company name	ion interactive	no
WebSite	Website URL	ioninteractive.com	no
OptIn	Opt-in to receive email	yes	no
Address1	Address line 1	101 Main Street	no
Address2	Address line 2	c/o ion interactive	no
Address3	Address line 3	Floor 15	no
City	City	Cambridge	no
State	State or province	Massachusetts	no
Province	Province	Ontario	no
Country	Country (full name)	United States	no
ProductInterest	The product a respondent expressed interest in	Blue Widget	no

 

ION CORE DATA

GEOLOCATION

ion field name	description	sample data	core?
GeoCountry	Respondent’s country location with 99% accuracy	US	yes
GeoCity	Respondent’s city with 70% accuracy	BOSTON	yes
GeoDomainName	Respondent’s domain name with 75% accuracy	COMCAST.NET	yes
GeoRegion	Respondent’s region/state with 75% accuracy	MASSACHUSETTS	yes

ION PORTFOLIO, CAMPAIGN, CREATIVE

ion field name	description	sample data	core?
PortfolioID	Unique numeric ID automatically assigned to each portfolio	59	yes
PortfolioLabel	Label you assign when adding or editing a portfolio	My Portfolio	yes
CampaignID	Unique numeric ID automatically assigned to each campaign	194	yes
CampaignLabel	Label you assign when adding or editing a campaign	My Campaign	yes
PathID	Unique numeric ID automatically assigned to each creative	826	yes
PathLabel	Label you assign when adding or editing a creative	My Creative	yes

ION TRAFFIC SOURCE

ion field name	description	sample data	core?
SourceID	Unique numeric ID given to Traffic Sources opened in your ion console	515	yes
MediaName	The category selected when adding a traffic source in your ion console	Email	yes
VehicleName	The sub-category selected when adding a traffic source in your ion console	Newsletter	yes
TrafficSourceLabel	The URL the respondent clicked on to visit an ion creative	https://myurl.com	yes
TrafficSourceDesc	A description that can optionally be added when opening or editing a traffic source	Quarterly newsletter link	yes

CORE ENGAGEMENT

ion field name	description	sample data	core?
Converted	Y (for Yes) or N (for No) value that indicates if the respondent is marked as converted	Y	yes
ConvertedDate	Timestamp that reflects when a respondent converted (central time zone)	03/08/2018 22:36:35	yes
FirstContact	Timestamp generated when a respondent first visits a creative (Central time zone)	6/22/2017 4:24:20 PM	yes
LastContact	Timestamp generated when a respondent last visits a creative (Central time zone)	6/22/2017 4:24:20 PM	yes
FirstPrimaryTag	First tagged element a respondent engaged with	Question 1	yes
SecondPrimaryTag	Second tagged element a respondent engaged with pre-conversion	Question 2	yes
Tags	All actions labeled via assigning tags in your creative or using ion’s external tag script	Question 1, Question 2, Question 3, Question 4, Question 5, Share (footer): Facebook	yes
NActions	The number of tagged elements a respondent engages with in the creative they visit	3	yes
NUserResponses	The total number of times a respondent has visited any ion creative managed in your console	11	yes
NVisits	The number of times a respondent has visited a creative using the same traffic source	5	yes

UNIQUE IDENTIFIERS

ion field name	description	sample data	core?
RespondentID	A unique, sequential numeric value that is assigned to each respondent upon visiting an ion traffic source URL	1234567	yes
UserID	A unique, sequential numeric value that identifies someone who has visited your ion experiences. Whereas the RespondentID is unique for each traffic source, the UserID will remain the same across visits to different traffic source URLs to tie the visitor data to a single person.	12345	yes

OTHER

ion field name	description	sample data	core?
UserAgent	Identifies the client software originating the request	Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_2 like Mac OS X) AppleWebKit/603.2.4 (KHTML, like Gecko) Version/10.0 Mobile/14F89 Safari/602.1	yes
IPAddress	Respondent’s IP address	12.34.567.*	yes
Referrer	The URL that referred the respondent to your traffic source URL	https://www.facebook.com	yes
Grade	Grade assigned to a respondent based on advanced rules that move the grade value up or down as they navigate through your creative	C	yes
UserTimelineUrl	Link to timeline showing visits to all experiences, data collected across those experiences, as well as Sell-Side insights	https://myurl.com	yes

 

QUERY STRING DATA

ion field name	description	sample data	core?
[custom]	Information passed to ion via a query string on the URL — such as UTM or other source tracking parameters	email ^where key = utm_medium and query string contained “utm_medium=email”	no

If you select an ion Basic/Core 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!

---

If you have any questions, please contact us at [email protected].