Skip to content

Commit 42b46b5

Browse files
authored
Merge branch 'master' into codeowners-update
2 parents 4213c0b + 0b30a41 commit 42b46b5

File tree

2 files changed

+14
-7
lines changed

2 files changed

+14
-7
lines changed

src/connections/destinations/catalog/kitemetrics/index.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,12 @@ pod "Analytics"
3333
pod "Analytics-iAds-Attribution"
3434
```
3535

36-
Segment and Kitemetrics can automatically record the following events: "Application Installed", "Application Opened", "Application Updated", "Install Attributed" and "In-App Purchases". In order to capture those events you need to enable automatic tracking. Ensure you set up [SEGAnalyticsConfiguration](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/) as shown below:
36+
Segment and Kitemetrics can automatically record the following events: "Application Installed", "Application Opened", "Application Updated" and In-App Purchases”. In order to capture those events you need to enable automatic tracking. Ensure you set up [SEGAnalyticsConfiguration](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/) as shown below:
3737

3838
Swift
3939
```swift
4040
let configuration = SEGAnalyticsConfiguration(writeKey: "YOUR_WRITE_KEY")
4141
configuration.trackApplicationLifecycleEvents = true
42-
configuration.trackAttributionData = true
4342
configuration.trackInAppPurchases = true
4443
configuration.middlewares = [SEGADTracker.middleware()]
4544
SEGAnalytics.setup(with: configuration)
@@ -49,7 +48,6 @@ Objective-C
4948
```objc
5049
SEGAnalyticsConfiguration *configuration = [SEGAnalyticsConfiguration configurationWithWriteKey:@"YOUR_WRITE_KEY"];
5150
configuration.trackApplicationLifecycleEvents = YES;
52-
configuration.trackAttributionData = YES;
5351
configuration.trackInAppPurchases = YES;
5452
configuration.middlewares = @[ [SEGADTracker middleware] ];
5553
[SEGAnalytics setupWithConfiguration:configuration];

src/connections/storage/warehouses/selective-sync.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,19 @@
11
---
2-
title: Warehouse Selective sync
2+
title: Warehouse Selective Sync
33
redirect_from: '/connections/warehouses/selective-sync/'
44
---
55

6-
[Warehouse Selective Sync](https://segment.com/docs/connections/warehouses/faq/#can-i-control-what-data-is-sent-to-my-warehouse/) allows you to manage the data that you send to your warehouses. You can use this feature to stop syncing specific events (also known as collections) or properties that aren’t relevant, and could be slowing down your warehouse syncs.
6+
[Warehouse Selective Sync](/docs/connections/warehouses/faq/#can-i-control-what-data-is-sent-to-my-warehouse/) allows you to manage the data that you send to your warehouses. You can use this feature to stop syncing specific events (also known as collections) or properties that aren’t relevant, and could be slowing down your warehouse syncs.
77

88
> info ""
99
> This feature is available to Business Tier customers only.
1010
1111
With Selective Sync, you can customize which collections and properties from a source are sent to each warehouse. Previously, changes made using this feature were applied to all warehouses within a workspace. Now, instead of all changes affecting every warehouse in a workspace, you can use Selective Sync to decide which data should go to each individual warehouse. This allows you to send different data to each warehouse.
1212

13-
This feature only affects [warehouses](/docs/connections/storage/warehouses/), and does not prevent data from going to any other [destinations](/docs/connections/destinations/).
13+
This feature affects [warehouses](/docs/connections/storage/warehouses/), and does not prevent data from going to any other [destinations](/docs/connections/destinations/).
1414

15-
When you use Selective Sync to prevent data from syncing to a specific warehouse, Segment stops sending new data that meets the selection criteria to that warehouse, however it doesn't delete any existing data in the warehouses. If you use Selective Sync to re-enable a source after disabling it, Segment loads all data that arrived since the last sync into the warehouse, but doesn't backfill data that was omitted while the source was not syncing.
15+
> warning ""
16+
> Note: For each warehouse only the first 5,000 collections per source and 5,000 properties per collection are visible in the Selective Sync user interface. Learn more about the limits [here](#selective-sync-user-interface-limits).
1617
1718

1819
## When to use Selective Sync
@@ -43,5 +44,13 @@ To manage data from one specific source to an individual warehouse, go to the Wa
4344

4445
All changes made through Selective Sync only impact an individual warehouse - they do **not** propagate to multiple warehouses at once. To make changes to multiple warehouses, you need to enable/disable data for each individual warehouse.
4546

47+
### Selective Sync User Interface Limits
48+
49+
Regardless of schema size, for each warehouse only the first 5,000 collections per source and 5,000 properties per collection can be managed using the Selective Sync user interface. After you hit any of these limits, all future data is still tracked and sent to your warehouse. New collections created after hitting this limit is not displayed in the Selective Sync table.
50+
51+
You will see a warning in the Selective Sync user interface when the warehouse schema has reached 80% of the limit for collections and/or properties. An error message will appear when you've reached the limit.
52+
53+
Contact [Support](https://app.segment.com/help/contact/) to edit Selective Sync settings for any collections and/or properties which exceed the limit.
54+
4655
> warning ""
4756
> Note: Only Workspace Owners can change Selective Sync settings.

0 commit comments

Comments
 (0)