Connect Data





Specific connection settings

Please see the Integrations left nav category in this wiki to discover key insights about a specific integration partner listed under the Connect Data marketplace.

Staying organized is smart, but keeping your data cleaned and organized is even smarter.

The Connect Data section gives your team the power to integrate numerous technologies in one place.

Where and how to connect data

1) Select the Connect Data button from the left-side navigation menu.

2) Select from the Data Sources | Extentions | or Destinations tabs. Each tab holds it's own category of integrations. You might find some integrations appear in multiple tabs but with different settings available once they are opened. This is because the platform attempts to split functionalities up by how data moves for your organization. For example, you might want to use Hubspot to constantly import data as it appears, but you also might want to use it as an destination where you can push marketing audiences into Hubspot lists. Most customers onboarding start by integrating their point of sale under Data sources. Extentions are usually data enhancers like "Take all of my contacts and find their latitude and longitude" or "Use a name to gender database to assign genders to unknown contacts".

Extention fees

Please note that some extentions have a usage fee associated with them. Pricing is listed within the description text on the integration listing.



3) Click the Connect button next to integrations you want to enable and you will then be presented with settings specific to that data source/ extention/ destination.

Example settings modal:

Document image

Common integration settings

  • All integrations require you consent that contacts imported using your connection will be compliant customers for your respective use cases. We will import as much data as possible from your integrations. Once imported, de-duped, and cleansed, you will be able to segment your data down to fit your needs using the Audience builder.
  • Most integrations that import customer records have a setting for "Send an SMS double optin request if a contact with a phone number is synced from this source after X date" setting. Leave this blank if you DO NOT want to send phones sourced from this integration a double optin request to join your SMS program. You must follow applicable privacy and marketing regulations based on your industry and use case. In some juristictions, asking for a phone number during a checkout at the point of sale is considered a verbal consent, while in others it's not. Only enable the double optin date if your customers already consented to joining or receiving your double-optin message. This feature is a great way to go back in time and say "I only want to send double optins to customers as long as they are seen checking out on my point of sale after x date." This date can be far in the past. If you do set the date in the past, the system will mass blast all applicable contacts since that date that need a double optin text message sent to them. Then from that moment forward, it will send them as we see new phone numbers from the respective data source.
  • Most integrations have the option to "FREEZE" on the last snapshot of data imported from the integration ("Most likely every 4 hours a snapshot occurs"). This is useful when migrated technology vendors. For example, if you move from POS "A" to POS "B", you would likely first turn on your "B" integration and then open up the settings for "A" to turn on the FREEZE checkbox. You would retain all Alpine IQ cleansed data from A but continue to leverage it on your new POS.
  • Sync contacts is a keystone functionality of the Alpine platform. If available on the integration, Alpine IQ will attempt to also reverse sync contact information back to the data source. Meaning if we see 3 semi-duplicate customers in your POS, we will merge all of those duplicates in your Alpine IQ database along with other duplicates that might be found via a another integration. This creates a complete customer record containing all engagement, purchase, and lifecycle history. Which then in turn powers relevant analytics, audience segmentation, message drips and more! If sync contacts is turned on, we will take the most complete record from our merging technology and then push it back into the POS and other integrations you have connected with sync contacts turned on.

Sync contacts only within state(s). NEW!

Enabling this will make Alpine only sync contacts that belong to the given credential's region. This is an advanced setting used mostly by multi-state operators.

If enabled, all credentials inputted need to fill out the "Regions" input with 2-character state abbreviations. For example, if you have 3 sets of Treez credentials, you could save "TX" in one, "CA" in the second, "FL" in the third. You then enable "Sync Contacts" + "Sync to State". Upon doing so, we'll only sync customers located in TX to the TX credentials, CA customers to the CA credentials etc.

We derive a customers "home state" in this order of priority:

  1. favorite store's state
  2. state for the last store u completed a sale at
  3. state saved as ur home address
  4. state derived from your phone's area code

If Sync contacts is enabled and sync to state is not, syncing will work as normal, i.e: Global syncs to every hub

Contacts crossing state lines

Contacts that leave their normal state and are seen shopping within another key will be synced to that other state/ keys regions at that time. This allows your org to maintain a clean database of customers across complex multi-POS setups.