Integration troubleshooting

Most integration issues fall into one of three buckets: expired authorization, missing permissions, or a mismatch between what you think is being synced and what the provider actually exposes.

Start with the simplest checks

Before deeper debugging, confirm:

1. the integration still shows as connected
2. the correct account is connected
3. the target audience, list, or segment still exists
4. provider permissions have not changed

If any of those fail, reconnect first before testing anything else.

Mailchimp reconnect flow

Mailchimp problems often appear after token expiry, scope changes, or list reconfiguration.

Check:

• the correct Mailchimp account is connected
• the audience still exists
• the account still grants read and write access

If in doubt, disconnect and reconnect from the integrations page, then run a fresh import.

HubSpot reconnect flow

HubSpot issues usually come from changed app scopes, list access, or contact property permissions.

Check:

• the connected HubSpot account is the intended production account
• the list or workflow you expect is still available
• contacts still expose the fields you rely on

Reconnect if any of those assumptions changed.

Common sync mismatch pattern

If the provider looks connected but counts are wrong:

• compare the expected source segment with the imported list
• check whether filters changed on the provider side
• verify whether the sync is incremental or full

Teams often debug the verifier when the real issue is a source list mismatch upstream.

What to capture before opening support

Include:

• provider name
• connected account email or workspace
• the list, audience, or segment name
• what changed recently
• the exact mismatch you see

That is enough for support to decide whether the issue is auth, source data, or SendSure sync behavior.