Exported Experience Platform datasets
Adobe Journey Optimizer B2B Edition makes account, person, buying group, and journey information available in Adobe Experience Platform. A dataset is a collection of related records. For example, a person dataset describes people, a membership dataset connects people to accounts or journeys, and an event dataset records actions such as opening an email.
Use this guide to understand what each dataset contains, what its fields mean, and how related records connect. Dataset names follow this pattern:
AJOB2B-<datasetVersion>-<entity>
Here, <entity> describes the information, such as person, account_relational, or person_event. <datasetVersion> identifies the version of the dataset’s field definitions. The section headings show the documented names; your Experience Platform environment may also contain older versions.
For the namespace and schema setup that supports these exports, see B2B namespaces and schemas.
Reading this guide
- Field name: the exact name you see in Experience Platform. Dots separate levels within a field, such as
consents.marketing.email.val. - Record ID: identifies the record in that dataset.
- Relationship: names the dataset and field that the identifier matches. For example,
Matches AJOB2B-1_5_4-buying_group (_id)means the field refers to a buying group’s_id. Match the complete identifier; do not shorten it or try to rebuild it. - Standard Adobe format: uses Adobe’s shared field definitions.
- Related-record format: organizes information as records you can connect using matching identifiers.
For example, buying_group_member.buyingGroupID matches buying_group._id, and its personID matches person_relational._id or the Person dataset’s personKey.sourceKey. These links help you understand who belongs to a buying group. Experience Platform does not automatically create reports or audiences from the links alone.
Some identifiers refer to information that has no separate dataset in this guide, such as a marketing program. The Relationship column notes this instead of naming a dataset that does not exist here.
isDeleted is true when the record is marked as deleted and false when it is not. Do not treat it as a general active-member or consent indicator. lastUpdatedDate describes the record’s latest data update; for events, use timestamp to understand when the activity happened. A blank field means that information is unavailable or does not apply to that record.
The related-record datasets use version 1_5_4. Where a field is not currently populated or needs special handling, the relevant section explains the customer-visible limitation.
An audience is a group of people who meet selected criteria. Availability for audience creation depends on your Experience Platform setup for combining information into person profiles. A dataset’s presence in Experience Platform does not, by itself, mean it is available for segmentation.
Choosing a dataset
personaccount_relational, person_relationalaccount_member, account_personbuying_group, buying_group_member, buying_group_eventaccount_journey, account_journey_member, account_eventperson_journey, person_journey_memberaccount_journey_node, person_journey_node, journey_nodeperson_event, person_event_relationalThe following sections provide the full dataset names and field details. A journey describes the overall experience; a membership connects a person or account to that journey; an event describes something that happened.
AJOB2B-1_5_1-person
Each record describes a person, their identifiers, and their email marketing preference. Use it for person-level reporting and, where Profile is configured, to help build audiences.
Format: Standard Adobe format
personIDpersonKey.sourceIDpersonKey.sourceInstanceIDpersonKey.sourceTypepersonKey.sourceKeyidentityMapconsents.marketing.email.valn indicates an opt-out; y indicates no opt-out recorded in this field. This field alone does not establish permission to send marketing email.consents.marketing.email.timeconsents.marketing.email.reasonisDeletedWhen your organization uses its own configured account or person datasets, those records can also include isDeleted. See Customer-owned datasets.
AJOB2B-1_5_4-account_member
Each record links one account to one person. Use this dataset to report which people are associated with each account; it describes the relationship rather than either profile.
Format: Related-record format
_idaccountIDAJOB2B-1_5_4-account_relational (_id)personIDAJOB2B-1_5_4-person_relational (_id)isDeletedlastUpdatedDateAJOB2B-1_5_4-buying_group
Each record describes a buying group associated with an account, including its name, status, solution interest, and engagement and completeness scores. The buying-group stage is not currently populated.
Format: Related-record format
_idbuyingGroupNameengagementScorecompletenessScoreaccountIDAJOB2B-1_5_4-account_relational (_id)solutionInterestbuyingGroupStatusbuyingGroupStageisDeletedlastUpdatedDatebuyingGroupStage is currently blank. Do not use it to filter or group buying groups by stage.AJOB2B-1_5_4-buying_group_member
Each record links a person to a buying group and records that person’s role. Use it to report buying-group composition and role coverage.
isDeleted does not always indicate whether a person has been removed from a buying group. Do not use this field alone to determine current membership. The role name can be blank when no role information is available.
Format: Related-record format
_idbuyingGroupIDAJOB2B-1_5_4-buying_group (_id)personIDAJOB2B-1_5_4-person_relational (_id)buyingGroupMemberRoleisDeletedlastUpdatedDateAJOB2B-1_5_4-account_journey
Each record describes an account journey, with its name, status, and start and end dates. Use it to report journey lifecycle and status for accounts.
Format: Related-record format
_idaccountJourneyNameaccountJourneyStatusstartDateendDateisDeletedlastUpdatedDateAJOB2B-1_5_4-account_journey_member
Each record connects an account with an account journey. Use it to identify and report which accounts are participating in each journey.
Format: Related-record format
_idaccountIDAJOB2B-1_5_4-account_relational (_id)journeyIDAJOB2B-1_5_4-account_journey (_id)isDeletedlastUpdatedDateAJOB2B-1_5_4-person_journey
Each record describes a person journey, with its name, status, and start and end dates. Use it to report journey lifecycle and status for person-focused journeys.
Format: Related-record format
_idpersonJourneyNamepersonJourneyStatusstartDateendDateisDeletedlastUpdatedDateAJOB2B-1_5_4-person_journey_member
Each record describes a person’s membership in a journey, including the current journey node, membership and entry dates, and entry count. Use it to report enrollment, re-entry, and journey progress.
Format: Related-record format
_idmarketingProgramIDpersonIDAJOB2B-1_5_4-person_relational (_id)journeyIDAJOB2B-1_5_4-person_journey (_id)journeyNodeIDAJOB2B-1_5_4-person_journey_node (_id)membershipDatelastEntryDatereentryOpensAtentryCountcreatedDateupdatedDateisDeletedlastUpdatedDateAJOB2B-1_5_4-account_journey_node
Each record describes a step in a journey, including the kind of step and the journey it belongs to. A journey node is a step such as a start, wait, or decision. The same steps can appear in person_journey_node; match accountJourneyID to an account journey before treating a step as account-specific.
Format: Related-record format
_idaccountJourneyIDAJOB2B-1_5_4-account_journey (_id)uuidjourneyNodeTypeIDnodeTypeisDeletedcreatedDatelastUpdatedDateAJOB2B-1_5_4-person_journey_node
Each record describes a step in a journey, including the kind of step and the journey it belongs to. The same steps can appear in account_journey_node; match personJourneyID to a person journey before treating a step as person-specific.
Format: Related-record format
_idpersonJourneyIDAJOB2B-1_5_4-person_journey (_id)uuidjourneyNodeTypeIDnodeTypeisDeletedcreatedDatelastUpdatedDateAJOB2B-1_5_4-account_event
Each record captures an account journey event: an account being added to or removed from a journey, or moving between journey nodes. Use eventType and timestamp to build an account activity timeline; buyingGroupID is available when the event is buying-group attributed.
Format: Related-record format
eventType provides information about what happened. The following tables describe the fields for each kind of activity.
lastUpdatedDate is not currently populated for these events. Use timestamp for the activity date.
Account added to a journey (account.addAccountToJourney)
_ideventTypeaccount.addAccountToJourney.timestampaccountIDAJOB2B-1_5_4-account_relational (_id)journeyIDAJOB2B-1_5_4-account_journey (_id)journeyNodeIDAJOB2B-1_5_4-account_journey_node (_id)buyingGroupIDAJOB2B-1_5_4-buying_group (_id)lastUpdatedDateAccount removed from a journey (account.removeAccountFromJourney)
_ideventTypeaccount.removeAccountFromJourney.timestampaccountIDAJOB2B-1_5_4-account_relational (_id)journeyIDAJOB2B-1_5_4-account_journey (_id)journeyNodeIDAJOB2B-1_5_4-account_journey_node (_id)buyingGroupIDAJOB2B-1_5_4-buying_group (_id)lastUpdatedDateAccount moved between journey steps (account.changeAccountJourneyNode)
_ideventTypeaccount.changeAccountJourneyNode.timestampaccountIDAJOB2B-1_5_4-account_relational (_id)journeyIDAJOB2B-1_5_4-account_journey (_id)journeyNodeIDAJOB2B-1_5_4-account_journey_node (_id)previousJourneyNodeIDAJOB2B-1_5_4-account_journey_node (_id); values may not matchbuyingGroupIDAJOB2B-1_5_4-buying_group (_id)lastUpdatedDateAJOB2B-1_5_4-buying_group_event
Each record captures a change to a buying group’s status, including the new status and when it changed. The new-stage field is not currently populated.
Format: Related-record format
Buying-group status changed (buyingGroup.changeStatus)
_ideventTypebuyingGroup.changeStatus.timestampbuyingGroupIDAJOB2B-1_5_4-buying_group (_id)newStatusnewStagelastUpdatedDatenewStatus to report status changes. Do not use newStage to report stage changes, because it is currently blank.AJOB2B-1_5-person_event
Each record describes a person-level web, email, or other supported activity event. Use eventType and timestamp to analyze behavior over time, with event-specific details populated only for the matching event type.
Format: Standard Adobe format
eventType tells you what happened. The following tables describe the fields for each kind of activity. Details that do not apply to an event are blank.
Email sent (directMarketing.emailSent)
_ideventTypedirectMarketing.emailSent.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeydirectMarketing.emailSent.mailingKey.sourceIDdirectMarketing.emailSent.mailingKey.sourceTypedirectMarketing.emailSent.mailingKey.sourceInstanceIDdirectMarketing.emailSent.mailingKey.sourceKeydirectMarketing.emailSent.mailingName_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)Email delivered (directMarketing.emailDelivered)
_ideventTypedirectMarketing.emailDelivered.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeydirectMarketing.mailingKey.sourceIDdirectMarketing.mailingKey.sourceTypedirectMarketing.mailingKey.sourceInstanceIDdirectMarketing.mailingKey.sourceKeydirectMarketing.mailingNamedirectMarketing.email_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)Email unsubscribe (directMarketing.emailUnsubscribed)
_ideventTypedirectMarketing.emailUnsubscribed.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeydirectMarketing.mailingKey.sourceIDdirectMarketing.mailingKey.sourceTypedirectMarketing.mailingKey.sourceInstanceIDdirectMarketing.mailingKey.sourceKeydirectMarketing.mailingNamedirectMarketing.email_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)Email opened (directMarketing.emailOpened)
_ideventTypedirectMarketing.emailOpened.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeydirectMarketing.mailingKey.sourceIDdirectMarketing.mailingKey.sourceTypedirectMarketing.mailingKey.sourceInstanceIDdirectMarketing.mailingKey.sourceKeydirectMarketing.mailingNamedirectMarketing.email_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)device.isMobileDevicedevice.modelenvironment.browserDetails.userAgentenvironment.operatingSystemEmail link clicked (directMarketing.emailClicked)
_ideventTypedirectMarketing.emailClicked.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeydirectMarketing.mailingKey.sourceIDdirectMarketing.mailingKey.sourceTypedirectMarketing.mailingKey.sourceInstanceIDdirectMarketing.mailingKey.sourceKeydirectMarketing.mailingNamedirectMarketing.emaildirectMarketing.linkURL_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)device.isMobileDevicedevice.modelenvironment.browserDetails.userAgentenvironment.operatingSystemEmail bounced (directMarketing.emailBounced)
_ideventTypedirectMarketing.emailBounced.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeydirectMarketing.mailingKey.sourceIDdirectMarketing.mailingKey.sourceTypedirectMarketing.mailingKey.sourceInstanceIDdirectMarketing.mailingKey.sourceKeydirectMarketing.mailingNamedirectMarketing.emaildirectMarketing.emailBouncedCodedirectMarketing.emailBouncedDetails_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)Email soft bounce (directMarketing.emailBouncedSoft)
_ideventTypedirectMarketing.emailBouncedSoft.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeydirectMarketing.mailingKey.sourceIDdirectMarketing.mailingKey.sourceTypedirectMarketing.mailingKey.sourceInstanceIDdirectMarketing.mailingKey.sourceKeydirectMarketing.mailingNamedirectMarketing.emaildirectMarketing.emailBouncedCodedirectMarketing.emailBouncedDetails_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)Web page viewed (web.webpagedetails.pageViews)
_ideventTypeweb.webpagedetails.pageViews.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeyweb.webPageDetails.webPageKey.sourceIDweb.webPageDetails.webPageKey.sourceTypeweb.webPageDetails.webPageKey.sourceInstanceIDweb.webPageDetails.webPageKey.sourceKeyweb.webPageDetails.nameweb.webPageDetails.URLweb.webPageDetails.queryParametersweb.webPageDetails.webPageIDenvironment.browserDetails.userAgentweb.webReferrer.URLWeb link clicked (web.webinteraction.linkClicks)
_ideventTypeweb.webinteraction.linkClicks.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeyweb.webInteraction.webInteractionKey.sourceIDweb.webInteraction.webInteractionKey.sourceTypeweb.webInteraction.webInteractionKey.sourceInstanceIDweb.webInteraction.webInteractionKey.sourceKeyweb.webInteraction.linkIDweb.webInteraction.linkURLweb.webPageDetails.queryParametersweb.webPageDetails.webPageIDenvironment.browserDetails.userAgentweb.webReferrer.URLForm submitted (web.formFilledOut)
_ideventTypeweb.formFilledOut.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeyweb.fillOutForm.webFormKey.sourceIDweb.fillOutForm.webFormKey.sourceTypeweb.fillOutForm.webFormKey.sourceInstanceIDweb.fillOutForm.webFormKey.sourceKeyweb.fillOutForm.webFormIDweb.fillOutForm.webFormNameweb.webPageDetails.queryParametersweb.webPageDetails.webPageIDenvironment.browserDetails.userAgentweb.webReferrer.URLInteresting moment recorded (leadOperation.interestingMoment)
_ideventTypeleadOperation.interestingMoment.timestamppersonIDAJOB2B-1_5_1-person (personID)personKey.sourceIDpersonKey.sourceTypepersonKey.sourceInstanceIDpersonKey.sourceKeyleadOperation.interestingMoment.dateleadOperation.interestingMoment.descriptionleadOperation.interestingMoment.sourceleadOperation.interestingMoment.type_experience.journeyOrchestration.stepEvents.journeyIDAJOB2B-1_5_4-person_journey (_id)_experience.journeyOrchestration.stepEvents.nodeIDAJOB2B-1_5_4-person_journey_node (_id)AJOB2B-1_5_4-journey_node
Each record describes a journey step, the journey it belongs to, and the kind of step. The same steps can appear in the account- and person-journey step datasets. Match journeyID to the appropriate journey; do not count a step more than once because it appears in several datasets.
Format: Related-record format
_idjourneyIDAJOB2B-1_5_4-account_journey or AJOB2B-1_5_4-person_journey (_id)nodeTypeisDeletedlastUpdatedDateAJOB2B-1_5_4-account_relational
Each record describes an account, including its organization details, location, size, revenue, and custom fields. Use this information to add account context to buying-group and journey reports.
Format: Related-record format
_idaccountNameindustrycountrysicCodedomainNameprimaryEmailDomainstreetcitystatepostalCoderegionphoneNumberlogoUrlannualRevenuenumberOfEmployeescreatedDatesourceTypesourceInstanceIDsourceIDcustomAttributesisDeletedlastUpdatedDateAJOB2B-1_5_4-person_relational
Each record describes a person, including their contact information, job details, identifiers, and custom fields. Use it to add person information to membership, journey, and activity reports.
Format: Related-record format
_idemailfirstNamemiddleNamelastNamejobTitlepersonTypeisLeadisAnonymoussalutationphonemobilesourceTypesourceInstanceIDsourceIDidentityNamespaceidentityValuecustomAttributesisDeletedlastUpdatedDateAJOB2B-1_5_4-account_person
Each record links an account profile to a person profile. Use it to report relationships across the account and person profile datasets.
Format: Related-record format
_idaccountIDAJOB2B-1_5_4-account_relational (_id)account_relational._id).personIDAJOB2B-1_5_4-person_relational (_id)person_relational._id).createdDateisDeletedlastUpdatedDateAJOB2B-1_5_4-person_event_relational
Each record describes a supported person activity, such as viewing a web page, interacting with an email, or moving through a journey. Use eventType and activityTypeID to understand what happened. Only details relevant to that kind of activity are populated.
Format: Related-record format
The following field list covers all supported activity types. An individual record contains only the details that apply to its activity.
_id. Do not assume every activity has a usable record identifier. The dataset is not a guarantee of a complete activity history.Journey details (journeyID, journeyNodeID, journeyStepID, and similar fields) are provided for journey activities (person.journeyAdd, person.journeyRemove, person.journeyStart, person.journeyEnd, person.journeyNodeTransition, person.journeySplitNode) and for person.attributeChanged activities associated with an “Update person profile” journey step.
Attribute-change fields (attributeName, attributeID, attributeNewValue, attributeOldValue, attributeChangeReason) are populated for person.attributeChanged only.
_idtimestampeventTypeweb.webpagedetails.pageViews, web.formFilledOut, web.webinteraction.linkClicks, directMarketing.emailSent, directMarketing.emailDelivered, directMarketing.emailBounced, directMarketing.emailBouncedSoft, directMarketing.emailUnsubscribed, directMarketing.emailOpened, directMarketing.emailClicked, leadOperation.interestingMoment, person.attributeChanged, person.journeyAdd, person.journeyRemove, person.journeyStart, person.journeyEnd, person.journeyNodeTransition, person.journeySplitNode.activityTypeIDeventType to distinguish activities that share the same event label.personIDAJOB2B-1_5_4-person_relational (_id)journeyIDAJOB2B-1_5_4-person_journey (_id)journeyNodeIDAJOB2B-1_5_4-person_journey_node (_id)previousJourneyNodeIDAJOB2B-1_5_4-person_journey_node (_id)person.journeyNodeTransition and person.journeySplitNode).newJourneyNodeIDAJOB2B-1_5_4-person_journey_node (_id)person.journeyNodeTransition and person.journeySplitNode). Usually equals journeyNodeID.journeyStepIDjourneyChoiceNumberperson.journeySplitNode. Recorded as a whole number.journeyEntryCountjourneyProgramIDactivitySourcecampaignIDattributeNameperson.attributeChanged only).attributeIDperson.attributeChanged only).attributeNewValueperson.attributeChanged only).attributeOldValueperson.attributeChanged only).attributeChangeReasonperson.attributeChanged only).assetIDassetNamerecipientEmailpersonID. assetName identifies the email content, not the recipient’s address.bouncedCodebouncedDetailsisMobileDevicedeviceModeloperatingSystemuserAgentclickedLinkUrlwebPageUrlweb.webpagedetails.pageViews only).queryParameterswebPageIDreferrerUrlformIDweb.formFilledOut only).linkIDweb.webinteraction.linkClicks only).interestingMomentDateleadOperation.interestingMoment only).interestingMomentDescriptioninterestingMomentSourceinterestingMomentTypeisDeletedlastUpdatedDateField reference by activity type
The following tables show which details apply to each activity. Other details are blank. Some activities share the same eventType label: codes 8 and 48 both use directMarketing.emailBounced. Use activityTypeID to distinguish them.
Web page viewed (web.webpagedetails.pageViews) (Activity type 1)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamewebPageUrlqueryParameterswebPageIDreferrerUrluserAgentisDeleted, lastUpdatedDateForm submitted (web.formFilledOut) (Activity type 2)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNameformIDqueryParameterswebPageIDreferrerUrluserAgentisDeleted, lastUpdatedDateWeb link clicked (web.webinteraction.linkClicks) (Activity type 3)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamelinkIDqueryParameterswebPageIDreferrerUrluserAgentisDeleted, lastUpdatedDateEmail sent (directMarketing.emailSent) (Activity types 6, 39)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamecampaignIDisDeleted, lastUpdatedDateEmail delivered (directMarketing.emailDelivered) (Activity types 7, 45)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamecampaignIDisDeleted, lastUpdatedDateEmail unsubscribe (directMarketing.emailUnsubscribed) (Activity type 9)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamecampaignIDisDeleted, lastUpdatedDateEmail opened (directMarketing.emailOpened) (Activity types 10, 40)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNameisMobileDevicedeviceModeloperatingSystemuserAgentcampaignIDisDeleted, lastUpdatedDateEmail link clicked (directMarketing.emailClicked) (Activity types 11, 41)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNameclickedLinkUrlisMobileDevicedeviceModeloperatingSystemuserAgentcampaignIDisDeleted, lastUpdatedDateEmail bounced (directMarketing.emailBounced): hard bounce (Activity type 8)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamebouncedCodebouncedDetailscampaignIDisDeleted, lastUpdatedDateThis activity shares the directMarketing.emailBounced label with activity code 48, but recipientEmail is blank for code 8. Use activityTypeID to distinguish the two.
Email bounced (directMarketing.emailBounced): sales email soft bounce (Activity type 48)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamerecipientEmailbouncedCodebouncedDetailscampaignIDisDeleted, lastUpdatedDateEmail soft bounce (directMarketing.emailBouncedSoft) (Activity type 27)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)assetIDassetNamerecipientEmailbouncedCodebouncedDetailscampaignIDisDeleted, lastUpdatedDateInteresting moment recorded (leadOperation.interestingMoment) (Activity type 46)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)interestingMomentDateinterestingMomentDescriptioninterestingMomentSourceinterestingMomentTypeisDeleted, lastUpdatedDateassetID and assetName are not populated for this activity type.
Person field changed (person.attributeChanged) (Activity type 13)
Included only when the change is associated with a journey, such as an “Update person profile” step. Changes outside a journey are not included.
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)attributeNameattributeIDattributeNewValueattributeOldValueattributeChangeReasonjourneyIDAJOB2B-1_5_4-person_journey (_id)journeyNodeIDAJOB2B-1_5_4-person_journey_node (_id)journeyStepIDjourneyProgramIDactivitySourceisDeleted, lastUpdatedDatePerson added to or started a journey (person.journeyAdd, person.journeyStart) (Activity types 182, 184)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)journeyIDAJOB2B-1_5_4-person_journey (_id)journeyNodeIDAJOB2B-1_5_4-person_journey_node (_id)journeyStepIDjourneyEntryCountjourneyProgramIDactivitySourceisDeleted, lastUpdatedDatePerson removed from or ended a journey (person.journeyRemove, person.journeyEnd) (Activity types 183, 185)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)journeyIDAJOB2B-1_5_4-person_journey (_id)journeyNodeIDAJOB2B-1_5_4-person_journey_node (_id)journeyStepIDjourneyProgramIDactivitySourceisDeleted, lastUpdatedDatePerson followed a journey branch (person.journeySplitNode) (Activity type 186)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)journeyIDAJOB2B-1_5_4-person_journey (_id)journeyNodeIDAJOB2B-1_5_4-person_journey_node (_id)previousJourneyNodeIDAJOB2B-1_5_4-person_journey_node (_id)newJourneyNodeIDAJOB2B-1_5_4-person_journey_node (_id)journeyNodeID).journeyStepIDjourneyChoiceNumberjourneyProgramIDactivitySourceisDeleted, lastUpdatedDatePerson moved between journey steps (person.journeyNodeTransition) (Activity type 600)
_id, timestamp, eventType, activityTypeID, personID_id; personID matches AJOB2B-1_5_4-person_relational (_id)journeyIDAJOB2B-1_5_4-person_journey (_id)journeyNodeIDAJOB2B-1_5_4-person_journey_node (_id)previousJourneyNodeIDAJOB2B-1_5_4-person_journey_node (_id)newJourneyNodeIDAJOB2B-1_5_4-person_journey_node (_id)journeyNodeID).journeyStepIDjourneyProgramIDactivitySourceisDeleted, lastUpdatedDateCustomer-owned datasets customer-owned-datasets
Your organization may use its own Experience Platform datasets for accounts or people. When configured, Adobe Journey Optimizer B2B Edition can add information to those datasets instead of creating another account or person dataset.
Their names and available fields depend on your organization’s setup. Use the configured account or person identifier to recognize matching records. Having records in these datasets does not automatically make them available for audiences; availability depends on your Experience Platform configuration.