PieSync Fundamentals Answers
Contrasts PieSync and Zapier as iPaas solutions and walks you through the PieSync functionality.
There are 30 questions.
It should take 30 minutes to complete.
You must answer 23 questions correctly to pass.
You must wait 12 hours between attempts.
You have 3 hours to finish the exam.
Fill in the blank: In the App Marketplace, you can find _______.
swag such as t-shirts, coffee mugs, and backpacks
Tools for your business, such as PieSync, that can be accessed with a account
Landing page templates and other modules to help build out content for your website
In which scenarios should you use PieSync? (Choose all that apply.)
Enabling salespeople to have caller ID and an always up-to-date phone book
Allowing sales staff to consult QuickBooks invoices directly within
Syncing Calendly meetings with meetings
Migrating Zendesk tickets into Service Hub
Having a two-way synchronization of contacts data with a Mailchimp audience
How many different apps can you connect using PieSync?
Around 10, including , with 10 new apps being released every year
All of Zapier’s apps are automatically supported
Over 200 apps, with new apps being released every week
Around 200 officially, but actually unlimited apps if you consider PieSync’s open API
Fill in the blank: PieSync cannot be used for _________________.
syncing customer data only one-way
automatically promoting the lifecycle stage for contacts according to how they behave in another app
importing contacts data from a platform different from
de-duplicating data within one single platform
You want to achieve the following automation: When a deal progresses to a certain stage, you need an invoice drafted up in your invoicing app. Which of the following statements is true?
This is a textbook use case for a trigger-action automation tool such as Zapier. PieSync will not be of much help here.
This is a textbook PieSync use case. Set up a sync between and your invoicing app and this is what you’ll get.
This will most probably require custom development. Welp, there goes this year’s budget.
You could use PieSync Health to see: (Choose all that apply.)
The syncing status of a connection.
Which contacts are syncing and which aren’t, including an error message to figure out why.
Your PieSync and ubSpot billing status.
How many new contacts you can still sync this month.
Which of the following statements are true? (Choose all that apply.)
PieSync is a declarative method of integrating — you tell it what you want to achieve and PieSync will figure out what to do.
PieSync is a procedural method of integrating — you set up the different steps of the integration.
Zapier is a declarative method of integrating — you tell it what you want to achieve and Zapier will figure out what to do.
Zapier is a procedural method of integrating — you set up the different steps of the integration.
How does PieSync match identical contacts across two different apps?
Contacts are considered identical based on first and last name.
PieSync checks whether the IP addresses attached to these contacts are the same.
PieSync matches contacts on the basis of email address exclusively.
Other than contacts, PieSync can also sync companies. How does PieSync match identical companies across two different apps?
Companies are considered identical based on their VAT or tax identification number.
PieSync checks whether the IP addresses attached to these companies are the same.
PieSync matches companies based on their company name or email (if any).
How often does PieSync refresh syncs?
You can choose in the settings
Automatically at least every 5 minutes
Automatically every minute
At the end of the day
Scenario: Yesterday I set up a sync. PieSync Health is alerting me that around 250 of contacts could not be synced to my other app because the contacts don’t have a “Last Name (required field).” How could this be fixed? (Choose all that apply.)
Export a CSV out of PieSync and repair the names in a spreadsheet editor.
Fill out last names in . PieSync will automatically pick this up and resume syncing the contacts that now have a proper last name.
Have PieSync automatically define a placeholder last name for contacts with a missing last name.
Have a support agent fix this for you.
There is no solution for this.
PieSync Health informs you that your sync is “rate limited.” No data is syncing. What should you do in this situation?
PieSync will automatically resume syncing as soon as the rate limit is over.
Upgrade to a different PieSync plan with higher limits.
Hit “Force Sync”.
Delete your connection and start over from scratch.
What steps are recommended before starting up a sync? (Choose all that apply.)
No need to be careful. Just start the sync, and check the outcome. You can always revert to an earlier state of your database.
Review the connection rules and field mappings.
Make sure the data that you need synced is clean and rid of duplicates.
“Default field mappings” are customer properties that PieSync found in common for the two apps you need synced, and has linked automatically. What could be an example of a default field mapping’s property? (Choose all that apply.)
Mailchimp subscription status
What will happen when you disable the “Avoid Duplicates” checkbox?
PieSync will no longer use the email address to identify unique contacts.
Contacts that lack an email address will now also be included.
Contacts that PieSync flagged as duplicates can now also be synced.
All of the above.
Which of the following statements is false?
By ignoring any contact that does not have an email address, the creation of duplicates is avoided.
Connection Rules will help you define which contacts are kept in sync and which ones are not.
The sync direction will ultimately decide which app wins in case of conflicts.
Excluding a contact in one rule will not automatically exclude them in other rules.
Which of the following statements is true?
You will always be able to get a two-way sync no matter which apps you are connecting.
PieSync can create and update contacts, but it will never delete contacts.
Changing the email address of a contact in sync, will cause the creation of a new contact.
If you exclude a contact in one rule, it will automatically also be excluded in any other rule.
Why does PieSync sometimes ask you to select a contact type?
Each connection can only sync one contact type.
It needs to know which contacts to exclude.
To have you verify the risk you are taking by syncing.
True or false: PieSync will always keep your contacts in sync, even if it’s a one-directional connection.
Contacts will always be kept in sync regardless of the sync direction or integration.
Not when syncing lead generators like Eventbrite or Facebook Lead Ads, then PieSync will just push those contacts like Zapier.
PieSync syncs with the following object(s): (Choose all that apply.)
Which of the following fields will always be part of a default field mapping between any two PieSync compatible apps?
First name, last name, and email
When is syncing a better option over importing? (Choose all that apply.)
You have a CSV properly formatted and you know you only need to import this data once.
You have contacts data sitting in two PieSync-compatible apps and need it to be synched up.
You want to create leads in your CRM for every subscriber that interacts with your content.
True or False: PieSync syncs historical data.
Contacts that already exist in the databases can also be synced.
PieSync only starts syncing new data from the moment you set up the sync.
Scenario: While syncing your Outlook address books and CRM, you discover that your personal notes in Outlook also sync into the CRM. You could make this a one-way sync from into Outlook, but you actually need your data to sync from Outlook into as well.What could you do to avoid a potentially bad situation?
Set up connection rules to avoid contacts with notes to sync.
Disable the notes field in the field mappings.
Activate the special Outlook-NN (no notes) connector instead.
Contact the PieSync team to custom code a solution for you.
What should you do before you start syncing with PieSync? (Choose all that apply.)
Make sure that you have a good understanding of what your contact data looks like
Clean up your contacts; delete or merge duplicates
Take a backup of your contacts as precaution
Run a test sync on a limited subset of your contacts
No need to prepare. If something goes wrong I can have PieSync restore my contacts
PieSync connection rules allow you to: (Choose all that apply.)
Change the color of your dashboard
Limit which contacts should be kept in sync
Define which team members have access to PieSync’s configuration screen
Assign contacts to sync to the respective contact owners in
Set up Slack alerts for when syncing fails
In the following sync rule configuration, the desired outcome is to have contacts labeled “CRM” synced with . What would you fix to make this setup work?
This is a perfectly sound rule setup and nothing would need to be changed.
The second rule needs to be deactivated. It does not come with a filter and would sync all contacts regardless of their label.
Each rule still needs to have an action to define whether contacts can be created or only updated.
When is it useful to click “Force sync” on the PieSync Health screen?
It is useful to click this button every seven to eight days to purge PieSync’s sync cache.
When you’re actively making changes to your contacts and you don’t want to wait for PieSync’s next sync cycle.
The “Force sync” button doesn’t do anything. It’s in fact a placebo button and its sole intent is to give the user a false sense of control over the sync.
Consider the scenario and screenshot of an active sync between and Google Contacts. A new contact for lead John Doe was recently created in . It’s been 25 minutes and the contact still isn’t showing in Google Contacts. Why isn’t this new contact syncing into Google?
The second rule to allow contacts to sync into Google has been deactivated.
The contact will only sync after 30 minutes. Patience is a virtue!
The sync still needs to be manually triggered for John Doe to sync over.
Review the screenshot of the configured field mappings for a sync between and Mailchimp. How can you start segmenting the Mailchimp audience based on company size (number of employees)?
Everything is OK in PieSync. The segmentation on company size needs to be set up in Mailchimp directly.
The field mapping is not yet complete. The company size property still needs to be mapped to a custom field in Mailchimp.
It’s not possible to set up this type of segmentation through PieSync.
Review this screenshot. The following sync rule has three actions attached to it. What is the maximum amount of actions one could add?
There’s no limit to the number of actions you can add in a sync rule.
If the number of filters is N, then the number of actions can be N+1 at most.
A maximum of three actions can be added to each rule.
This depends on which pricing plan the user is on.
What could never be a possible field mapping between any two PieSync compatible apps?
Sync up “First name” to “Last name”, two-way
Sync up a yes/no field to a text field, one-way.
Sync up a numerical field to a text field, one-way
Sync up a date field to a date/time field, two-way
In the setting illustrated below, I have selected the second setting, CRM. Choose the statement that most correctly describes the outcome of this configuration.
When I change someone’s first name in Google Contacts, the first name in should not change. Only changes that I make in should be synced to Google Contacts.
Someone’s first name could be spelled differently in both apps before I set up a two-way sync. This setting confirms it’s okay to have first name overwrite Google Contact’s first name.
The drop-down shown here is a filter in a sync rule. It contains a long list of properties through which you can scope your sync to sync just a subset of data. What kind of properties will make up this list?
Only the default properties for contacts — custom properties can be found elsewhere
properties for contacts, along with data linked to Service Hub tickets
All default and custom properties for contacts and companies
Review the screenshot. The sync has been modified from its default two-way sync to a one-way sync instead. When would you need just a one-way sync instead of a two-way sync?
PieSync is cheaper when it only runs as a one-way sync.
You don’t want to make any inadvertent changes to data.
This is the only way to prevent your Google private contacts from syncing into .
I’m in the process of setting up field mappings to sync the lifecycle stage directly into Mailchimp’s “Tags” field. I want “Subscriber” or “Customer” to sync respectively as tags in Mailchimp. However, from this screenshot, you can see this is not possible. “Tags” is greyed out. Why would this not be possible?
Tags have to be created beforehand in Mailchimp through its user interface, so a direct field mapping won’t work here.
Since does not work with tags, a field mapping to Mailchimp tags will not work either.
The PieSync license in which this screenshot is captured probably doesn’t allow for this type of mapping.
Review the screenshot of this connection overview of two active syncs. The newly created contacts in either or Outlook are not syncing across. What could be causing the sync issue?
Contacts can only sync to either Google or Outlook, not both at the same time.
The sync with Outlook is paused — resume this sync and the contacts will sync again.
The maximum number of contacts that can be synced has been reached.
Review this scenario and screenshot: Oh no! A colleague who did not complete a training on PieSync logged into PieSync and changed the default sync rules, turning it into this atrocity instead. Why is this not making any sense?
We don’t have any contacts named John nor Mary in our contacts database.
It does not take into account that “John” can sometimes be spelled “Jon” without an “h.”
Setting up these rules are overkill, and in fact, limit the sync to contacts named only John or Mary.
You want to keep and Intercom in sync, but you don’t want new Intercom contacts to ever be created in . How can you tell PieSync to keep existing Intercom contacts in sync with?
By adding an action to the second and third rule that says ‘only perform updates’.
By adding a filter to the second and third rule that says ‘in CRM’.
By either deleting or disabling the second connection rule.
It’s not possible, PieSync will always sync historical contacts.
Review this screenshot. What could be wrong about this sync rule?
The operator should not state “equals.” It should instead state “contains.”
The rule logic is wrong — a contact can never be a lead and a customer at the same time. These should be split up into two separate sync rules.
Instead of “AND” an “OR” operator should have been selected.
More certification answers:
- Size109 KB
- Length12 pages