Skip to main content

What is the latency of data in Swrve?

Latency in Swrve depends on the type of data in question. The table below lists the approximate latency for different reporting data in Swrve.

Data typeRelevancyTotal latency in realtime mode
Segment membershipA/B tests, Campaign audiences, Trend reports, Segments screenData written every 2 seconds
All KPIsTrend reports, KPI Metrics dashboard, A/B testsData written hourly
User cohortsUser Cohorts reportData written hourly
User attributesUser Attributes reportData written hourly
ItemsTrend reports, Top Items report, Item Charts reportData written hourly
Event countsEvents report, Trend reports, Campaign reports, A/B testsData written hourly
FunnelsFunnels report, A/B testsData written hourly
A/B test resultsA/B testsData written every 5-10 minutes (see below)
Campaign metricsCampaigns - summary card and detailed reportsData written every few minutes up to several hours (see below)

A/B test results​

A/B test results are written every 5 to 10 minutes. However, note the following:

  • As conversion A/B tests are based on funnels, the data on which these A/B tests are based is written hourly.
  • As engagement tests depend on event and item sales KPIs, the data on which these A/B tests are based is written hourly.

For more information about Swrve analytics, see Intro to analytics.

Campaign report metrics​

Campaign report metrics are a combination of several KPIs and campaign engagement results. Depending on the campaign channel, frequency, and delivery schedule, campaign report data may be written anywhere from a few minutes up to six or seven hours.

Viewing device event information​

You can access debug event information for a particular device on the QA User Logging screen. To access device events, on the Settings menu, select QA devices and then select Logging for the device in question.