Skip to content

Commit 43dfe4d

Browse files
ugpeterstayseesong
andauthored
Update src/connections/sources/catalog/cloud-apps/unlocking-attribution/index.md
Co-authored-by: stayseesong <[email protected]>
1 parent 629f929 commit 43dfe4d

File tree

1 file changed

+1
-1
lines changed
  • src/connections/sources/catalog/cloud-apps/unlocking-attribution

1 file changed

+1
-1
lines changed

src/connections/sources/catalog/cloud-apps/unlocking-attribution/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The Unlocking Attribution source is built with a sync component, which means tha
3838

3939
Segment's sync component uses an upsert API, so the data in your warehouse loaded using sync reflects the latest state of the corresponding resource in Unlocking Attribution. For example, if `conversions.value` goes from `0` to `212` between syncs, on its next sync that conversion's value will be `212`.
4040

41-
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment daily. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.
41+
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources sync with Segment daily. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.
4242

4343

4444
## Collections

0 commit comments

Comments
 (0)