Using Frakture for Integrations

Ashley Hansen

When we’re out and about, we often hear. “Oh yeah, Frakture! I’ve heard of you, you do integrations and have bots!” Yes, both are true.

Frakture does integrations, but they are a bit different than traditional system to system (also called point to point) integrations you’re probably familiar with. Let me explain.

All of the data captured through Frakture’s integrations flow through a centralized database (data warehouse) and are coordinated through a common set of data fields (also known as a data schema). This means all the data collected from each system is captured in one location using the same data fields throughout.

We’ve talked to many clients over the years who have built very custom system to system integrations only to have one of a few things happen:

  • Not all of the data from one system fits nicely into the other system.
  • One of the systems releases an upgrade and the integration breaks.
  • You move systems and the integration is no longer needed.
  • A process changes, requiring the integration to be upgraded, but there isn’t any budget to fix it.

To simplify, scale and reduce the price, Frakture operates with a standard set of fields and processes.

What does Frakture integrate?

In short, Frakture integrates a standard set of fields for people, transactions and messages.

1. People Fields:

First, Last, Address 1, Address 2, City, State, Postal Code, Country, Email, Phone, ID, Email opt-in status, SMS opt-in status.

2. Segments — a.k.a Groups of people:

Most platforms have some way of representing a list of individuals.  For example, membership levels, advocacy actions, donors, etc.  Frakture can synchronize limited (~100) segments, and their people.  Very useful for summary data, or strategic segments of people used for targeting across different platforms.

3. Transaction Fields

People fields listed above (e.g. person id, email, name), Amount,  Transaction Date, Source codes, and campaign information.

4. Other Data Available from Frakture Data (typically for reporting and not integrations):
  • Message Performance: ‘Messages’ are any published content, regardless of channel.  Statistics depend vary heavily on the channel and platform used (email, Facebook, etc). Typically includes: Sent, views, opens, clicks, unique openers, unique clickers. When available: Reported conversions, transactions, transaction amounts.
  • Message Fields: Name, subject, sender, publish date, campaign, html content, text content, links, source code(s).
  • **Attribution: Frakture will also gather information useful for attribution such as source codes, source code definitions, lookup tables, etc.


But I want to integrate ‘insert thing’, but it’s not listed above! Can I?

Yes, probably. In general, we can add custom fields on the above items for some modest hourly charges. For example, we could push a segment of people from Eventbrite into Luminate indicating the people attended an event. But, we wouldn’t push over the exact event they attended, number of guests they brought to the event, etc.


Advantages of Using Frakture for Integrations:

  • No more custom code built in-house, that’s dependent on one developer or consultant to work.
  • It future proofs your operations at no additional cost. Frakture is responsible for upgrading the connections to the systems you use. We call the connections Bots. If one system upgrades, Frakture updates that Bot to keep your integration working.
  • It makes it easy to test a new best of breed tool to improve your workflow. Are you looking to add a Marketing Automation tool? How about starting an SMS program? Or testing a new payment gateway such as Apple Pay or Amazon Payments to see if that increases donations?
  • Cost effective — rather than re-building custom integrations each time, our Bots are designed to be fast to deploy and fast to maintain

Want to take us for a spin?

Contact us for a demo today and learn how Frakture can help your organization to get more done with robots