FAQs: Account Connector

  • Updated

Click the links below to learn the answers to frequently asked questions about Account Connector. 

What is Account Connector? 

Using Account Connector, you can connect your Demandbase account data with other third-party integrations. Account Connector will support Adobe Analytics, Google Analytics, Drift, Optimizely, Uberflip, and other custom integrations. Learn more about setting up Adobe Analytics and Google Analytics integrations here.

To access the Account Connector page, click the Settings cogwheel icon in the left panel and Navigate to Demandbase-Wide Settings > Account Connector. To view the steps for using Account Connector, click this link.

Are there limits to the number of integrations you can create?

There is no limit on the number integrations you can create. 

What data can you push out on the API?

Account data only.

Are there limitations on the number of variables you can select for the response?

200

Who has access to Account Connector?

The Administrator Role only.

How is Account Connector different than Data Stream?

Account Connector (API) relies on website traffic to fire, while Data Stream does not. Data Stream has all historical data (e.g. intent) and activities, while Account Connector only has access to Account fields. Data Stream also includes ad campaign data, while Account Connector does not, Data Stream is updated nightly.

Why is the data different between Demandbase Platform and Google/Adobe Analytics?

Currently, Demandbase leverages two data models, the Domain data model and the Company data model. We developed the Domain data model as a new way to define companies. The Domain data model rolls up all the various records we collect about a company at the website domain level. This solved many problems with our legacy method (SID-based) Company data model, and was therefore adopted as the data model for new features such as the Platform and Site Analytics.

However, our integrations with Google and Adobe Analytics still use the Company data model, and there can be slight differences in company names and firmographics between the Company data model and the Domain data model. We could not immediately update these integrations with the Domain data model as it could negatively affect downstream systems such as personalization or reporting. We are nearing the process of inviting clients to begin this migration, but are unfortunately not initiating migrations yet.

Until then, there may be differences between the Platform and Google and Adobe Analytics. If you are interested in migrating over to the Domain data model, please reach out to your CSM.

Was this article helpful?

0 out of 0 found this helpful