First Party Journeys
- 10 Nov 2023
- 3 Minutes to read
- DarkLight
First Party Journeys
- Updated on 10 Nov 2023
- 3 Minutes to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Summary
First Party Journeys extend Activate’s capabilities by enabling you to identify and monitor for customer activity on your own websites - in addition to the shopping data provided by Jornaya’s Partner Network. This article describes the steps to begin capturing data from First Party Journeys.
Don't have First Party Journeys enabled yet?
Contact your Jornaya Customer Success Manager to learn more or send an email to customersuccess@jornaya.com
First Party Journey Field Names
First Party Journeys include the same data points as Activate 3.0. The naming of the First Party data point fields is based on how a journey is named within your Jornaya account.
The tables below explain each data point and its corresponding naming convention. The custom journey name from your account replaces the text within brackets [ ].
Daily In-Market Indicator Per Journey (DIMI)
This data point will be returned for each First Party Journey that has been enabled and indicates whether Jornaya witnessed any shopping activity for that consumer in that journey for the past day.
| Column | Description | Data type | Example | Value Definition |
|---|---|---|---|---|
| [First Party Journey Name]_1Day | Whether Jornaya has witnessed any in-market events for that consumer in that journey over the past day. | Integer | 1 | 1 = Jornaya has witnessed activity for that consumer in that journey. NOTE: No value indicates Jornaya has NOT witnessed activity for that consumer in that journey |
Number of Events Witnessed Per Journey (Past Day and Past 7 Days)
These data points will be returned for each First Party Journey that has been enabled and provides the number of events Jornaya witnessed for that journey.
| Column | Description | Data type | Example |
|---|---|---|---|
| [First Party Journey Name]_Events_1Day | The number of in-market events Jornaya has witnessed for that consumer in that journey over the past day | String | 1 to 2 3 to 4 5 to 6 7+ NOTE: No value indicates Jornaya has NOT witnessed activity for that consumer in that journey |
| Number of Events Witnessed – Last 7 Days | The number of in-market events Jornaya has witnessed for that consumer in that journey over the past 7 days | String | 1 to 2 3 to 4 5 to 6 7+ NOTE: No value indicates Jornaya has NOT witnessed activity for that consumer in that journey |
Time of Day Shopping (Past Day and Past 7 days)
These data points analyze the time of day Jornaya saw a consumer shopping across the specific First Party Journey:
| Columns | Description | Data type | Example Values |
|---|---|---|---|
| [First Party Journey Name]_Time_of_Day_Shopping_Min_1Day | The earliest time Jornaya witnessed the consumer shopping in that journey the past day rounded down to the nearest hour in GMT | String hh:mm AM/PM GMT | 08:00 AM GMT |
| [First Party Journey Name]_Time_of_Day_Shopping_Max_1Day | The latest time Jornaya witnessed the consumer shopping in that journey the past day rounded down to the nearest hour in GMT | String hh:mm AM/PM GMT | 2:00 PM GMT |
| [First Party Journey Name]_Time_of_Day_Shopping_Min_7Day | The earliest time Jornaya witnessed the consumer shopping in that journey the past 7 days rounded down to the nearest hour in GMT | String hh:mm AM/PM GMT | 11:00 AM GMT |
| [First Party Journey Name]_Time_of_Day_Shopping_Max_7Day | The latest time Jornaya witnessed the consumer shopping in that journey the past 7 days rounded down to the nearest hour in GMT | String hh:mm AM/PM GMT | 7:00 PM GMT |
IMPORTANT!
- The brackets shown in the Field Name Format are to indicate which part of the field name will change. You should NOT include brackets in the name when mapping your fields
- These fields follow the same format as the standard Activate 3.0 data points, as detailed in our specifications, found here.
Updating your Platform Integration(s)
Jornaya has several out-of-the-box platform integrations that connect Jornaya data directly to your system of record (ex: Salesforce, Velocify, etc.). Configuring an integration includes mapping Jornaya’s journeys to fields in your system via myJornaya.
First Party Journey names are unique to a given account and so need to be typed into the integration wizard rather than selected from the dropdown list.
When using Jornaya’s integration wizard, type in the full field names for each First Party Journey data point and click the “set to” option that will appear below the input field as shown in the screenshot below:
Map your First Party Journey fields to the relevant fields in your system of choice, by selecting from the list of system fields on the right-hand side of the wizard.
Updating your SFTP Integration(s)
Jornaya also offers the option to receive output files via SFTP. If using an SFTP integration, the new First Party Journey fields will appear within the same file you are already receiving. These fields will be additional columns appended to the dataset. No updates will be required to how Jornaya delivers the data, however, you should be sure to update your internal automation to recognize and ingest the new data points each day.
What's next?
Jump back to finish setting up First Party Journeys in our First Party Journey implementation guide
Was this article helpful?
