We’ve redesigned the Swivel Sync experience to make setup and ongoing configuration simpler, faster, and fully self-service. Previously, users needed to navigate between multiple areas of the application to configure devices, update source settings, or view sync activity. With this release, all Swivel Sync actions are consolidated into a single, unified dashboard.

The Swivel Sync dashboard gives you a clear view of the most important activity to monitor throughout your day. Each widget highlights key information about your device, sources, and sync activity so you can quickly identify where attention is needed.

The Device Health widget displays the current status of your Swivel Sync device and alerts you when action is required (for example, when the device goes offline). If the device is offline, updates cannot sync to your connected policies and accounts.

The Sources widget shows which login sources are linked or unlinked.
Keeping sources linked ensures that all associated policies and accounts continue to update properly. If a source becomes unlinked, those policies will not sync until the source is reconnected.

Sync Activity provides the most relevant sync attempt across all syncable policies within a rolling last 7-day period.

This breakdown gives you a clear picture of which policies have successfully updated, which may require follow-up, and which still need to be synced for the day.

Your Sync Activity numbers move over time — and that’s expected. This section explains how the syncing engine fills those numbers, why the counts rise and fall from day to day, and how to tell the difference between normal fluctuation and a count that actually needs attention. For what each individual metric means, see the Sync Activity section.

Each linked login source builds its own queue of all the policies and accounts it has access to. The queue is ordered by priority so the work that matters most is attempted first, and the source works through it continuously while linked.

Within a source’s queue, products are ordered like this:

If you've synced everything and noticed your "not synced" number still moving from one day to the next, that's expected — it's the system working as intended.

A changing count is normal and usually isn't a sign of a problem. The number that actually warrants attention is Not Found.

Every metric in Sync Activity — Not Yet Synced, Not Found, Success, and Total Syncable — is measured over the most recent 7 days, not since the beginning of time. A policy counts as a Success as long as it had at least one successful sync attempt during that window.

As each day passes, the window moves forward with it. Once a policy’s most recent successful attempt slips outside the last 7 days, that policy rolls back into Not Yet Synced until a source picks it up again. Because the window is always sliding forward, the counts move with it — even on a day when you haven’t touched anything.

This is the most common reason the count jumps up unexpectedly. When you sync a large batch of policies on a single day, all of those successes share roughly the same “expiration date” in the rolling window. About 7 days later they age out together. Any that a source hasn’t successfully synced again in the meantime will move back into Not Yet Synced at around the same time — so the number can climb again even though nothing has gone wrong.

The remedy is simply continued, consistent syncing. As your sources stay linked and keep working their queues, those policies get attempted again and return to Success. This is also why running a manual sync on a group of policies one day can be followed, about a week later, by a brief rise in the Not Yet Synced count.

How much of a source’s queue can be completed within any 7-day window depends on three things:

Carriers with shorter link sessions — or sources that only get linked once every day or two — are the most likely to not reach every policy within 7 days, so their counts fluctuate the most. For those carriers this is expected behavior.

There isn’t a fixed “done” state — and that’s by design. Swivel Sync is built to keep your policy data current continuously, so the work is ongoing rather than a task you finish once, and the count never has to land on zero. Instead of waiting for Not Yet Synced to reach zero, read the dashboard this way:

If your Sync Activity is returning lower success counts than you expect, the cause is usually one of two things:

After a login source is first created and linked, Swivel Sync works through the queue of syncable policies in the background — success counts will rise as those sync attempts complete.

A source can only sync while it’s linked. If one of your sources drops or doesn’t get linked daily, the policies it covers won’t make progress through the queue, and your overall success counts will reflect that. Check the Sources widget on the Dashboard to confirm everything you expect to be linked actually is.

The Institutions & Sources tab provides the ability to manage and configure all connected institutions and login sources needed to sync and update your policies and accounts.

The Device tab provides the ability to configure and connect your assigned Swivel Sync device to your specific Swivel account.