Create a data feed

Select the data view that contains the data that you want to export.

Consider the following when selecting a data view:

• If multiple data feeds are created for the same data view, each data feed must have different column definitions.
• The list of available columns depends on the login company where the selected data view belongs. If you change the data view, the list of available columns can change.

The following dimensions are included by default in every data feed and cannot be removed:

Customer Journey Analytics standard dimensions cannot be included in data feeds. The following table lists these dimensions:

The following Customer Journey Analytics standard metrics cannot be included in data feeds:

The following dimensions cannot be used together with the User Agent or Mobile ID dimensions:

• Browser Type
• Browser
• Mobile Manufacturer
• Mobile Device Type
• Mobile Audio Support
• Mobile DRM
• Mobile Java VM
• Mobile Information Services
• Mobile Image Support
• Mobile Color Depth
• Mobile Net Protocols
• Mobile Device Number
• Mobile Max Email Length
• Mobile Mail Decoration
• Mobile Push To Talk
• Mobile Screen Width
• Mobile Max Browser URL Length
• Mobile Operating System (deprecated)
• Mobile Screen Height
• Mobile Video Support
• Mobile Cookie Support
• Mobile Max Bookmark Length
• Mobile Screen Size
• Mobile Device Name
• Operating System Types
• Operating Systems

The following Customer Journey Analytics metrics must be substituted:

Select the type of feed you want to create:

• Live feed: Exports current and future data.
• Backfill feed: Exports historical data.

Select how often the data feed should be sent. Events with timestamps that fall within the frequency window are included in the data feed delivery. The Lookback date range and Processing delay fields can also affect which events are included in the data for the delivery frequency that you choose.

For live feeds, select to include either one hour’s worth of data or one day’s worth of data. For backfill feeds, this field is locked to Daily, meaning that data is grouped into daily chunks.

• Daily: Feeds contain a full day’s worth of data, from midnight to midnight in the data view’s time zone.

  This option is required for backfill feeds and is optional for live feeds.

• Hourly: Feeds contain a single hour’s worth of data.

  This option is available for live feeds only.

Controls how far back Customer Journey Analytics looks when processing the data feed delivery. The default is 30 days.

The frequency window (hour or day) determines which events are included in the data feed, while the lookback date range provides the needed historical context to classify those events correctly.

Segment qualification, dimension persistence, session calculation, and derived field transformations can all affect the events that are included.

Before configuring this option, see the details and examples described in the section below, Understand the lookback date range.

Choose the amount of time to wait before processing a data feed file. The default is 2 hours. Any late-arriving events that come in during the processing delay are included in the data feed.

Processing delays are useful for various reasons, such as to give mobile implementations an opportunity for offline devices to come online and send data, or to accommodate your organization’s server-side processes in managing previously processed files.

Sessions must start after the processing delay cutoff in order to be included; sessions that start before the cutoff and end within the processing delay are not included.

Customer Journey Analytics dynamically determines the optimal delay based on how long late-arriving events typically take for your feed, but you can manually set it to delay for 2, 3, 4, or 8 hours.

Select the compression format for the Parquet output files delivered to your cloud destination. Choose from the following formats:

• Snappy: Fast compression and decompression with moderate file sizes. Widely supported by modern data platforms such as BigQuery, Snowflake, and Apache Spark.
• GZip: Broadly compatible, including with tools that do not natively support Snappy. Recommended if your downstream pipeline requires a widely recognized compression standard.
• Z Standard (Zstd): High compression efficiency with fast decompression. Suitable if minimizing file size is a priority and your tools support Zstd.

• Any cloud accounts that you previously configured are available to use for data feeds. You can configure cloud accounts from the Locations manager, in Components > Exports > Location accounts.

• Cloud accounts are associated with your Customer Journey Analytics user account. Other users cannot use or view cloud accounts that you configure unless you make them available to all users in your organization.

• You can edit any locations that you create from the Locations manager in Components > Exports > Locations.

Do either of the following:

• Use an existing account: Select the drop-down menu next to the Account field. Or, begin typing the account name, then select it from the drop-down menu.

  Accounts are available to you only if you configured them or if they are shared with an organization you are a part of.

• Create a new account: Select Add account within the Account drop-down menu. For information about how to configure the account, see Configure cloud export accounts.

Do either of the following:

• Use an existing location: Select the drop-down menu next to the Location field. Or, begin typing the location name, then select it from the drop-down menu.
• Create a new location: Select Add location within the Location drop-down menu. For information about how to configure the location, see Configure cloud export locations.