Overview
In this article, we describe the steps to configure DataBridge to start using the eMarketeer Connector to update eMarketeer and SuperOffice user consent.
To exchange consent between eMarketeer and SuperOffice with DataBridge is quite simple but needs some steps to follow. Once setup, consent is exchanged automatically in the background between eMarketeer and SuperOffice.
Intended Audience
This article is intended for persons who are the administrators for DataBridge.
Configure the eMarketeer Consent Connector
Log in to the customer portal as an admin. more info
Create a new profile, give the profile a name e.g. ImportToSO, and in the location field chose eMarketeerConsent. The destination field will be filled automatically with your SuperOffice system.
When done click the NEXT button and you will be guided to the Configure Profile page.
- Configure Profile
On this page you can connect your SuperOffice instance and insert your eMarketeer API key. Read Requirements and checklist for eMarketeer Connector for SuperOffice to get the API key from eMarketeer.
This The inserted API Key is now specific to the eMarketeer consent API (see step 2) and cannot be shared with any other entities or connectors of eMarketeer.
When done click the NEXT button and you will be guided to the Configure Source page.
- Configure Source
There are two consent purposes defined in eMarketeer "Store and process" and "Marketing sendouts"
Both Consent purposes need to be synced between SuperOffice and eMarketeer. But, both purposes can’t be synced within one Databridge profile, separate profiles are needed for each Consent purpose.
Select one Consent purpose e.g. "Marketing sendouts" and create after finishing this profile a second profile for the other Consent purpose "Store and process".
The Consent properties are exactly the same across both purposes and fields can be selected from the “Fields” input field.
The next option is to say whether the import needs to support an incremental export in order to fetch the periodical data from eMarketeer.
When this option is enabled, only a export is done for the data that was created or modified after the last export. When it is the very first export it will always include all data.
Even if this option is not enabled, the DateTime will be tracked for every run. Resulting in that when a user enables "Incremental export" at some time, the last run’s DateTime will be used to fetch the changes since that time.