Skip to content

Commit bb62ebc

Browse files
authored
Merge pull request #2803 from Adobe-Enterprise-Docs/cja-df-update-luke
updates
2 parents 9f23f35 + 840107d commit bb62ebc

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

help/components/exports/cja-data-feeds/df-comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Data feeds in both Customer Journey Analytics and Adobe Analytics allow you to e
3535
| **Data processing**<br/>Data is processed at different stages, depending on which product you are using. | Data is processed at **report time**, and therefore many reporting features can be used to change historical data, such as stitching, derived fields, and segmentation. | Data is processed at **collection time**, and therefore reporting features such as processing rules and VISTA rules do not affect historical data. |
3636
| **Delivery frequency**<br/>Determines how often the data feed is sent and the window of time included in the feed. | **Daily** (midnight to midnight in the data view's time zone) or **Hourly**. | **Daily** (midnight to midnight in the report suite's time zone) or **Hourly**. 15-minute feeds are possible but not available by default. |
3737
| **Late-arriving hits**<br/>Hits whose timestamps belong to a previous delivery frequency window but arrive after that window already elapsed. <p>For example, late-arriving hits could come from a mobile app that buffers events while offline and sends them when it reconnects.</p> | The **Processing delay** setting controls how long the system waits after the frequency window closes before triggering the export, allotting extra time for delayed data to arrive. | Late-arriving hits can be **included or excluded** via the **Late-arriving hits** configuration option. <p>The **Lookback window** setting controls how far back the system reaches to include delayed data.</p> |
38-
| **Out-of-order hits**<br/>Hits whose timestamps don't match the order in which they were received. | Because Customer Journey Analytics accepts both streaming and batch data, there is no guarantee that events for a given person will arrive in timestamp order. Customer Journey Analytics reorders data by timestamp per person at report time. <p>The **Processing delay** setting helps reduce out-of-order events in data feed output by giving more time for batch data to arrive before the export. Event ordering in the delivery is not guaranteed.</p><p>**Important**: The ultimate consumer of your data feed data must be able to handle timestamps that are out of order, per person, because hit ordering in the data feed delivery is not guaranteed.</p> | Adobe Analytics requires that data arrive in order per visitor at collection time, but hit ordering in the data feed delivery is not guaranteed.</p> |
38+
| **Out-of-order hits**<br/>Hits whose timestamps don't match the order in which they were received. | Because Customer Journey Analytics accepts both streaming and batch data, there is no guarantee that events for a given person will arrive in timestamp order. Although Customer Journey Analytics reorders by timestamp per person, it can only export the data that has arrived. This means that late arriving hits might be exported after hits with a later timestamp.<p>The **Processing delay** setting helps reduce out-of-order events in data feed output by giving more time for batch data to arrive before the export. Event ordering in the delivery is not guaranteed.</p><p>**Important**: The ultimate consumer of your data feed data must be able to handle timestamps that are out of order, per person, because hit ordering in the data feed delivery is not guaranteed.</p> | Adobe Analytics requires that data arrive in order per visitor at collection time, but hit ordering in the data feed delivery is not guaranteed.</p> |
3939
| **Backfill window**<br/>Exports historical data between two past dates. | Limited to the connection's rolling data window. | Limited to the report suite data retention limit: **25 months** by default. |
4040
| **Segmentation** | Segments can be applied to data feeds via the data view segment, a feed-specific segment, or both. | Segments cannot be applied. |
4141
| **Stitching** | Supported. Enables cross-device identity resolution, linking events across devices to a single person. | Not supported. Stitched data cannot be exported via Adobe Analytics data feeds. |

0 commit comments

Comments
 (0)