Skip to main content
Maestro ABM is an account-based marketing (ABM) platform: sales and marketing teams organize the companies they target into accounts and segments, map the contacts of each one, prepare dossiers, and run plays made of touchpoints (emails, calls, gifts, events) while Maestro scores engagement and influence. This connector reads the Maestro Data API and brings your accounts, segments, contacts, dossiers, plays and touchpoints, including custom fields, tags and the indicators Maestro calculates.
The connector only reads data. It never creates, changes or deletes anything in Maestro.

Configuring Maestro ABM as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Maestro ABM option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

The connector signs in with a Maestro Data API key. Only an ADMIN user of your Maestro company can create one, and the full key is shown only once, right after it is created, so copy it at that moment. If you don’t know where to create the key in your Maestro account, ask Maestro’s support for a Data API key. The following configuration is available:
  • API Key: The Maestro Data API key of your company.
The key reads the data of the Maestro company it belongs to. Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: Accounts, Segments and Contacts support Incremental sync: after the first sync, only records created or changed since the previous sync are read. Dossiers, Plays and Touchpoints are always synced as Full table, because their scores and indicators are recalculated by Maestro all the time.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here. Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

What happens when access is missing

  • If the API key is wrong or was revoked, the sync fails and no table is changed. Ask an ADMIN user to create a new key and update it in this source.
  • If Maestro says your company’s subscription or trial has ended, or that the company is deactivated, the sync fails and no table is changed.
  • If Maestro refuses one table to the key, that table is skipped and not updated, the other tables keep syncing, and the sync log names the table.
  • If a table synced as Full table that had rows comes back completely empty, that table’s sync fails instead of emptying it, and the log says so. If you really removed all that data in Maestro, run a Full sync of the source to accept the empty table.

Streams and Fields

Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description.
Archived and inactive records are included, with is_active false (and archived true on plays and touchpoints), so you can filter them in your queries. Nested information (custom fields, linked contacts, dossier details, play learnings, notes) comes as JSON text. Every table also has an extra_fields column with any field Maestro sends that has no column yet.

Fields by stream

Organizations your company follows in Maestro (segments are in their own table). Archived accounts come with is_active false.Table: accounts · Primary key: id · Sync: Incremental (by last_modified_at)
Accounts marked as segments in Maestro, with the same fields as Accounts.Table: segments · Primary key: id · Sync: Incremental (by last_modified_at)
People linked to one or more accounts. Inactive contacts come with is_active false.Table: contacts · Primary key: id · Sync: Incremental (by last_modified_at)
Sales-support material per account, contact or play, with its free notes. Read in full on every sync.Table: dossiers · Primary key: id · Sync: Full table
Commercial action plans with goals, budget, dates and the indicators Maestro calculates. Read in full on every sync.Table: plays · Primary key: id · Sync: Full table
Relationship actions run inside each play, with owners, contacts reached, interactions, scores and notes. Read in full on every sync.Table: touchpoints · Primary key: id · Sync: Full table

Implementation Notes

  • Incremental tables use last_modified_at. Maestro leaves updated_at empty on records that were never changed, so last_modified_at holds updated_at, or created_at when the record was never changed. Maestro does not document whether its “changed since” filter also returns records that were created and never changed, so the connector protects you in two ways: whenever the number of records in a table changes and the filter has not yet been seen returning such records, it reads the whole table in that sync; and every incremental table reads its whole list at least once every 7 days. In the rare case where a record is created while another one is removed between two syncs, the new record can take up to 7 days to appear.
  • Linked lists inside a record (for example the contacts listed inside an account) are refreshed in the incremental tables only when that record itself changes. Schedule an occasional Full sync of the source if you rely on those lists.
  • Accounts turned into segments (or back) appear in both the Accounts and the Segments tables, because Maestro does not report that a record left a list. A Full sync of the source removes the old copy.
  • Records deleted in Maestro stay in the incremental tables (Accounts, Segments, Contacts), because Maestro does not report deletions. A Full sync removes them. The Full table tables drop them on the next sync.
  • Request limit. Maestro limits the number of requests per minute for your whole company, shared with your other integrations. When the limit is reached the sync waits and continues; it only takes longer.
  • Not synced: the API key list and the API usage reports of the Maestro Data API (they need a user login, not an API key).