Changelog

Not happy with where your data is headed? Now you can do something about it. Stitch is happy to announce that customers can now switch between destination types in their Stitch account.

If you’ve been waiting to get Stitch hooked up to Snowflake, wait no longer! We’re happy to announce that as of today, Snowflake has entered open beta and is available for any customer to use.

Been waiting for Stitch to support Snowflake? Good news - Snowflake as a destination has just entered closed beta, and testing has already begun! If you’re interested in getting on the list, add your email address here and we’ll let you know as we add more testers.

Stitch has added 3 new integrations to help you expand your analyses. Sync your time tracking data from Harvest, your Urban Airship lists and segments and Taboola campaign performance to your data warehouse today. These integrations are all built using the Singer open source spec, allowing you to contribute and collaborate on their future improvements.

Time marches on, as do versions. Today, we’re happy to announce support for the latest version of Mongo, version 3.4. Additionally, Stitch now supports connecting securely to Mongo instances using SSL.

We’re excited to report that Stitch supports the recently announced PostgreSQL flavor of the the Google CloudSQL service. It’s available as both an input integration AND a data warehouse destination - a dual threat!

Stitch now has built-in support for Singer Taps, the data extraction component of the the just launched simple, composable, open source ETL Singer project. This exciting new standard will make getting data out of any source and into Stitch (or elsewhere) simpler and more straightforward.

To learn more about Singer, check out the launch blog post.

By supporting this standard, Stitch now supports these integrations:

• Hubspot
• Marketo
• Shippo
• Close.io
• Referral SaaSquatch
• Freshdesk
• Braintree
• GitLab
• Wootric
• Outbrain

Are you using Branch for deep linking in your mobile app? Now you can replicate event data from your Branch account to your warehouse and analyze app installs and engagement. Learn more.

Today we are excited to announce the launch of Stitch Webhooks; a configurable incoming webhook integration that replicates data from hundreds of webhook APIs directly to Stitch. Additionally, we’ve added 15 new integrations to Stitch, powered by webhooks, as great examples of what you can sync across different types of applications: AfterShip, Contentful, Customer.io, Delighted, Drip, Iterable, Mailjet, Mandrill, Particle.io, SendGrid, Sendwithus, SparkPost, FormKeep, Vero, and Zapier.

Ever wondered where your data was after Stitch pulled it from the source but hadn’t arrived in your data warehouse yet? When the next sync will start? How many rows you’ve loaded today? This information (and more) is now available - just click on any individual integration to experience this… experience.

With the new year fast approaching, the Stitch engineers wanted to slip in a last update or two to the product before the ball drops. Today, customers can now see and replicate views for database integrations - just pick a primary key and replication method. Enjoy!

Occasionally, Stitch encounters data that it can’t load into a data warehouse for a variety of reasons - dates that fall out of range, table names that are too long, etc. Stitch now persists these rejected records into a special table (_sdc_rejected) for each integration, and includes the reason for the rejection and as much of the data as it can fit.

When things go wrong, as they occasionally do, Stitch already sends an email notification about this issue. Now, those notifications are available inside the Stitch interface as well. Just click on the “Notifications” tab at the top of the page to see your active notifications.

If Redshift is not the right data warehouse for you, then we’ve got you covered. Our BigQuery and Postgres data warehouse integrations are now in open beta - and you can set them up in Stitch today! Both are now available during destination selection in the onboarding process.

Not sure how far back Stitch reaches into a SaaS integration? Need more historical data for your analysis? Made a change and need to go get all the data again? Now you can do it - Stitch users can now configure during setup how far back a SaaS integration will replicate, and can review, reset, and re-sync from that date at anytime. Check it out under Integration Settings.

Hot off the heels of support for resetting the replication keys for an entire database integration, Stitch now offers the ability to do it on a per table basis. Head down to the “Table Settings” for an individual table and you’ll see the new button.

Longing to get your data into Postgres instead of Amazon Redshift? Good news, everyone - Postgres as a destination for Stitch is now in closed beta! Sign up today if you are interested in the Postgres beta and we’ll add you to the waiting list.

Up until now, Stitch supported VARCHAR, NVARCHAR, and LONGVARCHAR. Today we’ve added support for the crazy uncle of the VARCHAR family, LONGNVARCHAR! Just a note - if you have existing database integrations that have this datatype, you’ll need to go in and specifically track it. Any new integrations will automatically track it.

Interested in Redshift but don’t want the hassle of maintaining an Amazon Web Services account? Exciting news - Stitch has partnered with Panoply.io to bring their managed data warehouse solution to our users - including a free tier with up to 10 million rows per month!

Salesforce objects with a lot of fields can lead to unnecessarily wide tables when all you care about are a few of the fields. Starting today you can select which fields to sync from your Salesforce objects, giving you more control to keep your warehouse clean and simple.

The Stitch Close.io integration is now available in beta for all customers to use. The new integration will sync all of your leads and activities to your warehouse, allowing you to analyze your Sales cycle and always be closing.

Excited about Google BigQuery? We’ve got some big news for you. Our Google BigQuery destination is now in closed beta! Sign up if you’re interested in joining the beta to start sending your data to Google BigQuery.

Lots of integration related news today. We’ve opened up the public beta for our new Google Analytics integration. The new GA integration allows you to create custom datasets using GA’s metrics and dimensions. Also, our Segment, Recurly, Trello, Pardot, and Intercom integrations have come out of beta and are ready for some ETL’ing. Now get out there and start moving some data.

The NetSuite integration now includes a table called netsuite_deleted which contains a row for every deleted record that supports deletes. Accounting for deleted records is especially important if you’re performing any sort of aggregate function - for example, totaling invoices or balancing your books. Learn more about utilizing the NetSuite deletion log in our docs.

The Zendesk integration now includes a zendesk_group_memberships table containing information about the groups your Zendesk agents are members of. Fields in this table include the group membership ID (id), URL, name, deletion flag, created_at and updated_at dates.

Need to completely re-sync all incrementally replicated tables in a DB integration? Now you can(!) via the Integration Settings page on any MySQL, Postgres, SQL Server or Mongo integration. Take care though - the re-synced rows count towards your monthly caps.

Don’t like what you named your integration? You can now fix that. Integration names can be edited within the settings for each respective integration. This does not change the name of the schema in your data warehouse.

We added a changelog to stitchdata.com to make it even easier to learn about Stitch product updates. Very meta.

All Postgres fields of type JSONB and ARRAY may now be synced from integrations page. These fields will be converted to strings in Redshift.

Now 50% Redshiftier, along with these improvements: faster loading for high volume data streams, transactional upserts, and NO MORE VIEWS - data is materialized into tables directly in the target schema, and these tables are never dropped.