The initial data sync between Summit and your CRM will typically complete in under 24 hours, but can take up to 48 hours for very large datasets.

Subsequent data syncing for individual contact records will typically complete in 5 minutes, but can take up to 20 minutes in some cases. Why the delay?

In Summit, individual runs are bundled under a concept called sessions. A session is a group of the parameter values a visitor enters while interacting with a particular app over the course of about 5 minutes. A session auto-closes after 5 minutes of inactivity. Only closed sessions will sync into your CRM. That introduces the first 5-minute delay.

The purpose of this delay and grouping methodology is to paint a clearer picture of which input values are most accurate. A session displays (a) the most common value entered over the course of that 5-minute session, (b) the min/max values, (c) first/last, etc. and we've found that the most common value entered within a session has the highest likelihood of being accurate. Without the session-level grouping, identifying the "right" value would prove much more challenging (Note: Grouping data by session also allows us to compare visitor input values across sessions).

Now, if the visitor's email address can be associated with an existing contact record in your CRM, the session data will likely appear in about 5 minutes. However, if the visitor's email address is not found as an existing contact record in your CRM, it will take an additional 15 minutes to create the contact and display the session data. The purpose of this delay is to take into consideration the scenario in which a new contact record for that same email is being created by another flow associated with your CRM (e.g. newsletter subscribe, trial signup, contact form submission, etc.) and not yet showing up in our integration (Note: this is a delay on the CRM side). Therefore, to avoid any data duplication, we introduce this 15-minute delay.

Return to: API & Integrations Support