You can import user attributes and events from relational databases such as Oracle Database, MySQL, PostgreSQL, and Microsoft SQL Server into Insider One by preparing the data for a standard import channel.
Your integration job reads or exports the source data, transforms it into the required format, and sends it through the Upsert User Data API, FTP/SFTP, or Amazon S3.
This guide describes API-based and file-based imports, rather than a direct connection from Insider One to your database. For data needed while a journey runs, you can also use Architect's Call an API element to request values from an API endpoint backed by your database.
Before you begin
Ensure you can read or export the required user and event data from your database.
Prepare an integration job that creates API payloads or publishes export files.
Plan your data mapping, including user identifiers, profile attributes, events, and event parameters.
Prepare the credentials and infrastructure required by your chosen import channel.
To configure FTP/SFTP or Amazon S3 source integrations, you need an Administrator or Editor with PII access role. Generating an API key requires an Administrator role.
Choose your import channel
Channel | When to use it | How data reaches Insider One |
|---|---|---|
Ongoing profile and event updates | Your integration job reads database records, creates API payloads, and sends requests to Insider One. | |
Scheduled bulk exports to a file server | Your job publishes CSV or TSV files. Insider One reads them on the configured schedule. | |
Batch exports through AWS | Your job uploads CSV or JSONL files to your S3 bucket. SQS notifications enable automatic imports of new files. |
Prepare your database data
Use the following approach whether your source is Oracle Database, MySQL, PostgreSQL, or Microsoft SQL Server:
Select the user and event records you want to import.
Include the identifiers needed to match records to Insider One user profiles.
Map source fields to Insider One attributes, events, and event parameters.
Format the output for your chosen channel: API payloads, CSV or TSV files for FTP/SFTP, or CSV or JSONL files for Amazon S3.
Test a small sample before starting the recurring import.
The database extraction and transformation steps run in your environment. The channel-specific guides explain how to format and deliver the resulting data to Insider One.
Import channel 1: Upsert User Data API
The Upsert User Data API creates or updates user profiles using attributes and events sent from your backend. If a profile already exists for the identifier you send, the API updates it. Otherwise, it creates a profile.
Use this channel for data such as loyalty attributes, consent preferences, leads, and offline purchase events.
Set it up
Plan your user data and get the plan approved by the Insider One team. Use the Upsert User Data API Integration Wizard to generate an API key and prepare headers and payloads.
Build an integration job that reads your database records and maps them to the API payload.
Place identifier fields under the
identifiersobject. Use one identifier per user object where possible.Run the job at the frequency your use case requires.
Review the API documentation for response handling before running the integration in production.
For payload requirements, limits, and error handling, see Upsert User Data. For guided setup, see the Upsert User Data API Integration Wizard.
Import channel 2: FTP/SFTP
Use FTP/SFTP when your database pipeline produces scheduled file exports. Insider One can read CSV or TSV files from an FTP, FTPS, or SFTP server and map them to user profiles and events.
Set it up
Export the required database records as CSV or TSV files.
Publish the files to your file server.
Navigate to InOne > Components > Integrations > External Integrations in InOne and select FTP/SFTP.
Configure the connection, file settings, identifier mappings, attribute mappings, and event mappings as needed.
Set the import schedule.
FTP transfers data in plain text. FTPS encrypts transfers with TLS, while SFTP runs over SSH. Choose an encrypted protocol for sensitive data.
For connection settings, file requirements, data mapping, and scheduling, see Import Data from FTP/SFTP to InOne.
Import channel 3: Amazon S3
Use Amazon S3 when your database pipeline publishes batch exports to AWS. The integration supports CSV and JSONL files containing user attributes and events.
Set it up
Prepare your database export in the required CSV or JSONL format.
Create an Amazon S3 source integration under Components > Integrations > External Integrations.
Authorize Insider One to read from your bucket and configure an Amazon SQS queue for new-file notifications.
Configure the bucket, path, and data mappings as described in the integration guide.
Publish your export files to the configured location.
For AWS permissions, notification setup, file requirements, and data mapping, see Import Data from Amazon S3.
Look up database-backed data during a journey
If a journey needs a current value from your database, use Architect's Call an API element to request it from an API endpoint that you expose in front of the database. This is a journey-time lookup, not a bulk database import.
Prepare an API endpoint that retrieves the required data from your system.
Configure a Call an API element in your journey.
Configure response variables according to the Call an API data-fetching guide.
Use the returned values in message content, update a user attribute, or branch the journey with Check API Response.
For example, you can retrieve a coupon code or the user's latest NPS score from your database-backed API.
Response variables belong to the journey that fetched them and are deleted when the user leaves it. If you need to save a returned value on the user profile, configure a user attribute update. Use the standard import channels for bulk updates.
For setup, supported response formats, and use cases, see Architect Channel: Fetch Data through Call an API.
For an Oracle-focused walkthrough, see Import Data from Oracle to Insider One.