Understand Salesforce and Interaction Studio Integrations

• Interaction Studio collects user and event data. 
• Data is transformed to CSV file and sent to Salesforce CDP through a shared file store.
• Salesforce CDP ingests data through an Interaction Studio starter bundle.

• Salesforce CDP activation jobs send segment membership, selected attributes, and calculated insights to Interaction Studio. 
• Data is written to CSV file and sent to Interaction Studio through a shared file store. 
• A Salesforce CDP ETL job ingests and imports data as user attributes and manual segments.

Import from Marketing Cloud:

• Use the Interaction Studio SFTP as the file location
• Marketing Cloud data extensions (DE) are extracted using Interaction Studio SFTP as destination in Automation Studio
• Interaction Studio polls SFTP for new files every 15 minutes for ingestion (files in Interaction Studio standard formatting specifications)

Export to Marketing Cloud:

• Export from any Interaction Studio segment
• Process uses Segment Exporter Gear
• Exports to Interaction Studio SFTP location
• Export types: manual (full or delta), nightly (delta)

• Build an Open Time email campaign in Interaction Studio to power 1:1 offer/content/product recommendations at open time within a Marketing Cloud email
• Copy and paste the HTML code output of the Open Time email campaign into a dynamic content block within Marketing Cloud for a reusable machine learning-driven component

• Pass Interaction Studio segments into Marketing Cloud using Automation Studio so you can leverage the data for retargeting across paid or social channels through Advertising Studio

Data in from Audience Studio:

• Client-side sync
• Feed

Data out to Audience Studio:

• File-based

• Capture and store additional Audience Studio attributes as custom attributes on the user profile to inform Interaction Studio segmentation and experience targeting
• Pass Interaction Studio segment membership to the page to help inform retargeting efforts
• Pass Interaction Studio segments using SFTP to Audience Studio for re-targeting purposes.

• After you add an Interaction Studio Activity to a Journey Builder Journey, you can use it to personalize the experience your customers have with your website or mobile app based on recent journey interactions.
• Journey Builder passes actions, identifiers, and attributes you configure back to Interaction Studio for identity merging, segmentation and targeting, and personalization.
• See also: Send a User to Journey Builder Upon Segment Join

Functionality enabled through Interaction Studio Web SDK:

• Understand anonymous and named customer behavior and web conversions
• Collect product, content, and other catalog information in real-time
• Render personalized experiences in real-time

Data in from Pardot:

• Feed

Data out to Pardot: 

• File-based
• Copy/Paste of Open Time email HTML

• Nightly or one-off file transfer
• Open-time email is real-time

• Segment Push - leverage the Interaction Studio segment exporter gear to push segments out through Interaction Studio's SFTP so you can pull them into Pardot for enhanced targeting
• User & Campaign Data Ingestion - Leverage the Interaction Studio ETL to store users, user attributes, and campaign events, such as sends, opens, and clicks. Interaction Studio has standard file formatting specifications available for these types of feeds
• Open-time Email - Build an open-time email campaign in Interaction Studio to power Pardot email with 1:1 offers or content/product recommendations at open time

• There is no direct connector between Interaction Studio and either Tableau or Datorama
• All data captured/stored within Interaction Studio can be made available in a pre-formatted data warehouse schema as files you can then import into Tableau or Datorama
• Tableau allows for richer analysis and custom visualizations of Interaction Studio's rich integrated data, while Datorama supports enhanced roll-up analysis and deeper media spend analytics

Feed

• Take any predictive scores configured in Einstein Analytics, output them using Interaction Studio's standard file formatting specifications, then upload to Interaction Studio to store as custom attributes on the user profile
• Uploads can either be one-off or posted to Interaction Studio’s SFTP for ingestion on a recurring cadence

• There is no direct connector between Interaction Studio and Einstein Analytics
• All data captured or stored within Interaction Studio can be made available in a pre-formatted data warehouse schema either as files for you to upload and leverage inside Einstein Analytics
• Bringing data into Einstein Analytics would be managed by you as the customer