Why are my contacts not syncing? Why is my sync not working? Why am I seeing Duplicates?
These are questions you might have if you see anything unusual happen with your contacts or sync(s) and you're wondering 'why?' Our troubleshooting tips below can provide an answer to questions about commonly encountered issues and might help you fix them.
1. Do your contacts have an email address? Is Avoid Duplicates enabled?
The algorithm of PieSync is based on the allocation of an existing email address. Contacts will only be synced if an email address is included. With some applications this setting is mandatory, with others you're able to determine yourself. When mandatory, you can always contact us, we just want to make sure you are aware of possible implications before doing so.
2. Are your contacts part of the rules (IF/THEN) you have configured?
Through PieSync you can and you should tweak the sync so that not only contacts get synced, but you also respect the segmentation, tags, groups, categories, custom attributes, subscription status, ... of the apps that the contacts live in. In a PieSync rule, you can choose to add a filter, and add actions to syncs.
It’s crucial to know the distinction between adding additional filters (IF) within a rule (AND) or creating a completely new rule per filter (IF).
For each filter you add within a rule, you establish an extra requirement. A contact will only be synced when it fulfils ALL of the requirements. In the example below, a contact needs to have the status "Subscribed" and "Cleaned" and "Pending" in order for it to be synced.
Creating separate rules for each filter allows you to sync contacts that are in ANY of the filters (IF) you choose rather than having to be present in ALL before it will sync.
3. Does PieSync still have access to your app-accounts? (Access Revoked/Authentication Failed)?
Due to long inactivity, changes in your login details or changes in the API restrictions, it might happen that PieSync loses access to your applications. If this is the case, you'll see this in your dashboard, please contact firstname.lastname@example.org. We'll send you a link to re-authorise asap!
4. Do your contacts meet the app-requirements?
Whether or not a contact is being kept in sync between two applications can also be dependent on the requirements of the applications itself.
The example below shows a contact in Capsule CRM which can only be created after providing a first or last name. Therefore, a contact will not be synced if this requirement is not met. Another example, for instance: a contact in HubSpot be created with only an email address. In a connection with Capsule, this contact will not be synced to Capsule until the first or last name is added there first.
5. Am I trying to sync CONTACT information?
At this point, we only sync contact information.
Depending on the apps you have connected, you might be looking for data that you believe to be part of the contacts in that app. However, it might actually be part of a different entity we don't sync (just) yet. In the example below, we only sync people.
6. Is there a third party or native integration in parallel with PieSync active?
Before activating PieSync, you want to make sure there is no other native or third-party integration running in parallel. Some applications come with their own integrations. Other/parallel integration(s) will also have access to your data and the ability to manipulate which could cause large numbers of duplicates & loops. That's why we ask you to use PieSync and nothing else to keep your data in sync between two apps.
7. Did you make an adjustment to a field that is mapped?
It's important to check the default field mappings between a connection. If you update a contact field in application A and you notice it's not syncing to application B, this field might not be part of the default mappings. In some cases, this can be solved by adding a custom field mapping.