Merge pull request #221 from segmentio/repo-sync

repo sync

Author: bot-docsteam

src/_includes/content/destination-footer.md

@@ -15,7 +15,9 @@ You can send computed traits and audiences generated using [Segment Personas](/d
 For user-property destinations, an [identify](/docs/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Personas sets that value to `false`.
 
 When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
-
+{% unless show-sync-disclaimer == true %}
+{% include content/sync-frequency-note.md %}
+{% endunless %}
 {% endunless %}
 
 {% endif %}

src/_includes/content/sync-frequency-note.md

@@ -0,0 +1,3 @@
+<div class="premonition info"><div class="fa fa-info-circle"></div><div class="content"><p class="header">Real-time to batch destination sync frequency</p><p> Note that real-time audience syncs to {{page.title| replace: "Destination", " "}} might take two to three hours.</p>
+
+</div></div>

src/connections/destinations/catalog/marketo-static-lists/index.md

@@ -48,6 +48,7 @@ Every time you create an audience in Personas and connect it to Marketo Static L
 2. Adds any users to that list who both fit the audience definition and have an email address.
 3. If a user has multiple email addresses on their identity graph, each email address becomes a unique entry on the list.
 4. After the audience is configured, Segment checks which users still fit the audience definition, and adds or removes users from the audience, once every hour.
+{% include content/sync-frequency-note.md %}
 
 ## Configuring Marketo Static Lists
 

src/connections/destinations/catalog/personas-display-video-360/index.md

@@ -175,7 +175,7 @@ Segment requires the [DoubleClick Floodlight](/docs/connections/destinations/cat
 To configure DoubleClick Floodlight:
 
 > warning ""
-> **Prerequisite**: Createa a [Javascript Website](/docs/connections/sources/catalog/libraries/website/javascript/) source in your Segment workspace if one does not exist. Ensure that this source is configured to track visitors to your website. For more information about configuring Javascript sources, see the [Analytics.js Quickstart guide](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/).
+> **Prerequisite**: Create a [Javascript Website](/docs/connections/sources/catalog/libraries/website/javascript/) source in your Segment workspace if one does not exist. Ensure that this source is configured to track visitors to your website. For more information about configuring Javascript sources, see the [Analytics.js Quickstart guide](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/).
 
 1. In your workspace, visit the **Catalog** and search for the **DoubleClick Floodlight** destination.
 2. Connect your Javascript Website source to the DoubleClick Floodlight destination, and configure the following settings:
@@ -228,6 +228,7 @@ On Step 3: Review & Create, **deselect** the Historical Backfill option to ensur
 After you complete the set up process, allow up to 24 hours for Google to create the new audience list. Once the list is created, Segment can begin to sync users to that list. Google may require additional time to process the initial audience additions. The entire first sync to DV360 may require 24-48 hours to complete. As a result, the first few audience syncs after you create the audience may fail.
 
 Extra information from the API (settings, connection modes, etc.) are automatically pulled in here.
+{% include content/sync-frequency-note.md %}
 
 ## FAQ
 ### What is Segment’s relationship with Google DV360 and is the data that Segment sends considered to be First or Third party?

src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md

@@ -84,7 +84,7 @@ Facebook offers the Facebook Pixel, which allows you to retarget these types of
 1. Creates a Facebook Custom Audience (of type Customer List) with a name that matches the Personas Audience.
 2. Adds any users that fit the audience definition, based on the matching identifiers that Facebook supports (hashed). Facebook uses these identifiers to match users to Facebook users in their ads system.
 3. Once the audience is configured, Segment checks which users still fit the audience definition based on the same identifiers, and adds or remove users from the audience, every hour.
-
+{% include content/sync-frequency-note.md %}
 > success "Tip:"
 > You can use the Audience History feature in Facebook to see this change over time.
 

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

@@ -1,5 +1,6 @@
 ---
 title: Oracle Responsys Destination
+show-sync-disclaimer: true
 ---
 
 ## Getting Started

src/personas/product-limits.md

@@ -42,7 +42,7 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
 | Compute Concurrency     | 5 concurrent audiences                            | Segment computes five new audiences or computed traits at a time. Once the limit is reached, Segment queues additional audience computations until one of the five audiences finishes computing.       |
 | Compute Throughput      | 10000 computations per second                     | Computations include any Track or Identify call that triggers an audience or computed trait re-computation. Once the limit is reached, Segment may slow audience processing.                           |
 | Events Lookback History | **Essentials**: 1 year <br><br> **Advanced**: 3 years | The period of time for which Segment stores audience and computed traits computation events.  This limit depends on your Personas service. Contact your account team to upgrade your Personas service. |
-
+| Real-time to batch destination sync frequency | 2-3 hours   | The frequency with which Segment syncs real-time audiences to batch destinations.  |
 
 ## SQL Traits