Drift

Last synced 1 week ago by Jonas

GETTING STARTED GUIDE: How to set up a new connection?
ALL FEATURES EXPLAINED: All our features/functionality explained in detail - no app-specifics.

Drift is a conversation-driven marketing and sales platform that connects your business with the best leads in real-time. Like a virtual assistant for your website, Drift lets you turn any conversation into a conversion.

Below you'll find detailed information, specifically for Drift integrations:

Supported Drift Integrations

Authorizing Drift

To authorize Drift, you simply log in to Drift and provide access to PieSync inside Drift.

If you already authorized Drift account(s) in the past or in any other PieSync integration, you'll be able to skip the first part of the authorization and choose from your CONNECTED ACCOUNTS.

Setting up your sync

Rules: [IF] Supported Conditions/Filters
This sync will only sync newly identified contacts. More on that below.
  • Has Tag
  • CQL Score
  • Lead Stage
  • Field Values (INCLUDING CUSTOM FIELDS)
  • Already existing in the app you sync with
Rules: [THEN] Supported Actions
  • Add / Remove Tag
  • Update CQL Source
  • Update Lead Stage
  • Updating field values (INCLUDING CUSTOM FIELDS)
Default Field Mapping

Depending on the other app you're syncing with, you'll see a number of standard Drift fields being mapped by default. For instance, in a connection with Google Contacts, the default field mapping looks like this:

PieSync syncs the default name field(s) that come with the apps. Sometimes they have a different structure in both apps you connect. E.g. first and last names are separate in app A and joint in a single field in app B. In the background, PieSync joins first and last names together from app A to B and separates them again from app B to A. Our algorithm is smart about which part it updates in app B.
Customizable Field Mapping

You can & should custom map your Drift Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible, and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping here.

Some things to note

Normally, PieSync does a full 2-way sync, which includes your historical data. For our Drift connector, we can only give you a near 2-way sync now. Read on below for more info.

Setting up a connection to Drift works in the same way as setting up any other PieSync connection. Setting up rules, defining contact mappings, monitoring the sync, it works just as expected.

What will the Drift sync do / not do?

For any sync, PieSync performs an (1) initial sync, and then PieSync keeps your contacts in (2) continuous sync.

However, because of Drift's different API architecture, there are a couple of elements in sync behavior that are different from what you typically get with PieSync. As long as this different behavior is here, we're giving our Drift connector the beta label.

(1) Initial sync
What you can expect during the initial sync:
  • 👍🏻 Contacts that exist in your ‘other’ app but not yet in Drift will be created in Drift & successfully mapped
  • 👍🏻 Contacts that exist in both your ‘other’ app and in Drift will get matched (based on their email address) and updated in Drift.
What will not work during the initial sync
  • 😬 Contacts that exist in Drift prior to starting the sync will not be created in the ‘other’ app
  • 😬 The setting of the toggle ‘When a conflicting change is detected’ will be ignored as the ‘other’ app will always win and overwrite the data in Drift. No updates will happen to the contact in the ‘other’ app at all.
  • 💩 Contact updates in Drift will be erroneously shown as ‘creations’ in our activity timeline, which can be confusing to the end users, as it should be displayed as ‘updates’ instead. This happens because our sync platform is not aware of the contact existing in Drift.
(2) Continuous syncing
What can you expect once the sync is running?
  • 👍🏻 Contacts created/identified through a Drift conversation get created in the ‘other’ app & successfully mapped
  • 👍🏻 Contacts (which are in sync) that get updated in Drift will get synced to the ‘other’ app successfully
  • 👍🏻 Contacts (which are in sync) that get updated in the ‘other’ app will get synced to Drift successfully

🚀 In other words, contacts are kept in a 2 way sync for any updates happening in Drift, or in ‘other’ app according to the rules & mappings

For contacts created in the ‘other’ app, the same logic applies as for the initial sync:

  • 👍🏻 If the contact does not yet exist in Drift, it will be correctly created and synced
  • 👍🏻 If the contact does exist in Drift, we will match it and update it in Drift
What will not work for ongoing syncs?
  • 😬 For contacts created in the ‘other’ app, the same logic applies as for the initial sync: if the contact already exists in Drift, then the field merging will not be correct and we will show it as a creation in Drift to the end user (instead of an update)
  • 😬 Contacts manually created through the Drift UI (‘add new contact’) will not sync

Thanks to the feedback we have already received, we created a list of popular apps that we’re going to work on very soon. By  voting them up in our pipeline, YOU decide which connectors we’ll release first. If you don’t see your app on the list or need any further help, drop us a line - support@piesync.com.  Don't forget to r ead our blog for the latest in productivity, apps, and technology!


How did we do?


Powered by HelpDocs