Import Data from Oracle to Insider One

You can import data from Oracle products, such as Oracle Database, Oracle CRM, or an Oracle data warehouse, into Insider One through Insider One's standard import channels: the Upsert User Data API for continuous profile and event updates, and the FTP/SFTP integration for scheduled bulk file imports. If your data pipeline already runs on Amazon Web Services (AWS), the Amazon S3 integration is a further option for automated file imports. This guide helps you choose the right channel for your data and walks you through the setup for each.

Essentials before integration

Before you begin, ensure the following prerequisites are met:

• To set up the FTP/SFTP or Amazon S3 source integrations in the InOne panel, you need an Administrator or an Editor with PII access role. To generate an API key for the Upsert User Data API, you need an Administrator role.

• Ensure you can export or query the user and event data you want to sync from your Oracle system; as files (.csv or .tsv for FTP/SFTP; .csv or .jsonl for Amazon S3), or as API payloads for the Upsert User Data API.

• Decide which data you will send: user identifiers, profile attributes, and events.

Choose your import channel

Import channel 1: Upsert User Data API

The Upsert User Data API sends user attributes and events to Insider One. Upsert means insert or update: if a profile already exists for the identifier you send, the API updates it; if none exists, the API creates one. This makes it the main way to bring data from systems outside the web and mobile SDKs, such as your Oracle CRM or operational databases, into the same profile Insider One uses for segmentation and personalization.

Typical Oracle use cases

• Offline and historical events — import purchases and other events recorded in your Oracle systems.

• Leads from external platforms — push leads captured in your CRM so you can follow up through Insider One channels.

• Segments prepared outside Insider One — add users to a static segment you built in your data warehouse.

• CRM and loyalty attributes — keep profile fields such as loyalty tier or language in sync with your source systems.

• Consent and channel opt-ins — pass GDPR opt-in and channel permissions from your consent or preference center.

Set it up

1. Plan your user data and get the plan approved by the Insider One team, then use the Upsert User Data API Integration Wizard to generate your API key (only users with an Administrator role can generate API keys), configure headers, and create API payloads based on your planned user data.

2. Build the job on your side that reads from your Oracle tables and maps each record to the API payload. Place identifiers under the identifiers object, and use one identifier per user object where possible.

3. Schedule the job at the frequency your use case needs.

Refer to Upsert User Data for payload parameters, limits, and error handling, and the Upsert User Data API Integration Wizard for step-by-step setup.

Import channel 2: FTP/SFTP

The FTP/SFTP integration allows InOne to automatically pull CSV or TSV files from your file server and sync the data into user profiles and behavioral events. Once configured, the integration runs on a schedule, so no manual uploads or API integration is required. FTP (plain text), FTPS (encrypted with Transport Layer Security, or TLS), and SFTP (running over Secure Shell, or SSH) are supported.

Set it up

1. Publish scheduled exports from your Oracle system as .csv or .tsv files to your FTP, FTPS, or SFTP server.

2. In the InOne panel, navigate to Components > Integrations > External Integrations, select FTP/SFTP, and enter your server connection details.

3. Map your identifiers, attributes, and events, and set the sync schedule.

Refer to Import Data from FTP/SFTP to InOne for the full walkthrough, including protocol selection, credentials, and data mapping.

Import channel 3: Amazon S3

If your data pipeline already runs on AWS, the Amazon S3 integration lets you efficiently import large volumes of data directly from an S3 bucket you own. S3 import supports .jsonl and .csv files with attribute, event, and purchase data.

Set it up

1. Export the tables you want to sync from your Oracle data warehouse as .csv or .jsonl files, and upload them to an S3 bucket you own.

2. In the InOne panel, navigate to Components > Integrations > External Integrations, create an Amazon S3 source integration, and authorize Insider One to read from your bucket.

3. Set up an Amazon SQS (Simple Queue Service) queue for new-file notifications so that new exports landing in the bucket are imported automatically.

Refer to Import Data from Amazon S3 for the full walkthrough, including AWS Identity and Access Management (IAM) authorization, file requirements, and data mapping.

Alternative: Import Through Your Data Warehouse

If your Oracle data already flows into a cloud data warehouse, you can connect that warehouse to Insider One directly. Snowflake, Amazon Redshift, Databricks, and Google BigQuery each have their own import guides:

• Import Data from Snowflake

• Import Data from Amazon Redshift to Insider One

• Import Data from Databricks to Insider One

• Send Google BigQuery Data to Insider One

Use Oracle Data in Real Time During Journeys

Besides importing, you can also use Oracle-held data at the moment a journey runs. With the Architect Call an API element, a journey can send a request to an API endpoint you expose in front of your Oracle data and retrieve values as response variables. You can use these variables in message content across the Email, Web Push, App Push, WhatsApp, and SMS channels, update a user attribute with them, and branch the journey with the Check API Response element.

This fits data that changes frequently and is temporary, or that regulations allow you to store only briefly; for example, retrieving a coupon code kept in your own systems, or fetching a customer's latest NPS (Net Promoter Score) and routing promoters and detractors down different paths. Response variables live only inside the journey that fetched them and are deleted as soon as the user leaves the journey.

Refer to Architect Channel: Fetch Data through Call an API for setup, response formats, and the full use-case list.