Skip to content

Commit ee8a02a

Browse files
authored
Update index.md
Update language around historical backfill to include how to ensure the backfill is running.
1 parent 7866df6 commit ee8a02a

File tree

1 file changed

+1
-1
lines changed
  • src/unify/profiles-sync/profiles-sync-setup

1 file changed

+1
-1
lines changed

src/unify/profiles-sync/profiles-sync-setup/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ If you choose to re-enable a table or property to sync again, only new data gene
117117

118118
#### Using historical backfill
119119

120-
Profiles Sync sends profiles to your warehouse on an hourly basis, beginning after you complete setup. You can use backfill, however, to sync historical profiles to your warehouse, as well.
120+
Profiles Sync sends profiles to your warehouse on an hourly basis once setup is complete. Setup is considered complete after the initial automated backfill has finished, which will sync all profile data. To initiate the backfill, the Profiles Sync pipeline requires live data flowing into your workspace. If live data isn’t available, you can send test data to the workspace to start the backfill sooner. You can also use backfill to sync historical profiles to your warehouse.
121121

122122
> info ""
123123
> You can only use historical backfill for tables that you enable with [Selective Sync](#using-selective-sync) during setup. Segment does not backfill tables that you disable with Selective Sync.

0 commit comments

Comments
 (0)