OAuth for APIs, Cloud Storage for file transfer
Last updated
Last updated
Data is written and read via Cloud Storage (S3, Azure Blob Storage, etc).
OAuth 2.0 credentials are used to connect to the Marketing Cloud APIs and run import/export tasks.
For outbound syncs, if any import errors are reported then the async import summary API is used to retrieve record level errors.
Omnata is agnostic as to the specific configuration of the cloud storage, as it never directly interacts with it. The only requirement is that the Marketing Cloud file location works, and that the objects can be read by Snowflake using an external stage.
Enter the Marketing Cloud Setup area:
2. Navigate to the "Installed Packages" section under "Apps", click "New", enter "Omnata" as the app name, and click "Save":
3. Click the "Add Component" button, and choose "API Integration":
4. Choose "Server-to-Server":
5. Enable the following scopes:
AUTOMATION
Automations: Read, Write, Execute (for outbound syncing of data extensions)
CONTACTS
Audiences: Read, Write (for inbound and outbound syncing of audiences respectively)
List and Subscribers: Read, Write (for inbound and outbound syncing of lists/subscribers respectively)
JOURNEYS: Read (for inbound syncing of journey events)
DATA
Data Extensions: Read, Write (for inbound and outbound syncing of data extensions respectively)
File Locations: Read (for managing import and export tasks)
6. Note the Client ID, Client Secret, and Authentication Base URI for the Omnata App Connection:
Configure a file location in Marketing Cloud which can read and write to the underlying cloud storage infrastructure, and note the External key.
Configure an external stage in Snowflake which points to the same underlying cloud storage infrastructure, and share it with the OMNATA_SALESFORCE_MARKETING_CLOUD_PLUGIN native application
Use both of these during connection configuration
Tracking Events: Read (for inbound syncing of tracking extracts)
