You can import user attributes and events from your WordPress site, such as registered users, form submissions, and order data if you run a store on WordPress, into Insider One through standard import channels. Use the Upsert User Data API for ongoing profile and event updates, FTP/SFTP for scheduled file imports, or Amazon S3 for automated file imports through Amazon Web Services (AWS).
This guide explains how to prepare WordPress data for these channels and configure the Insider One side of the integration. Your team or integration provider builds and operates the process that extracts data from WordPress, maps it to the required format, and delivers it to the selected channel.
This guide describes an integration through Insider One's standard APIs and file import channels. It does not describe an Insider One WordPress plugin, a native WordPress connector, or a direct connection to your WordPress database.
Adding the Insider Tag to your WordPress site to collect on-site behavior is a separate setup. For that, see Insider Tag Integration and Google Tag Manager.
Essentials before integration
Before you begin, make sure you meet the following prerequisites:
You have access to retrieve or export the required data from WordPress through a method your WordPress setup supports. The available data depends on your site and the plugins it uses.
Your team or integration provider can prepare API payloads or publish export files to the selected destination.
You have identified the user identifiers, profile attributes, and events you want to send. For WordPress data, the identifier is typically the user's email address.
You have defined how WordPress source fields map to Insider One identifiers, attributes, events, and event parameters.
To configure FTP/SFTP or Amazon S3 source integrations in InOne, you have an Administrator or an Editor with a PII access role (PII: personally identifiable information). To generate an API key for the Upsert User Data API, you have an Administrator role.
Prepare API payloads for the Upsert User Data API, CSV or TSV files for FTP/SFTP, or CSV or JSONL files for Amazon S3. Transform WordPress records into the format the selected import channel requires before you send them to Insider One.
Choose your import channel
Channel | When to use it | How it works |
|---|---|---|
Ongoing updates to user profiles and events, for example, when a user registers or submits a form | Your integration job retrieves WordPress data, maps it to API payloads, and sends requests to Insider One. | |
Scheduled bulk file imports | Your integration job publishes CSV or TSV files to your file server. InOne reads the files on the configured schedule. | |
Batch imports when your data pipeline uses AWS | Your integration job uploads CSV or JSONL files to your S3 bucket. Insider One imports new files through the configured notification flow. |
Import channel 1: Upsert User Data API
The Upsert User Data API sends user attributes and events to Insider One. If a profile exists for the identifier you send, the API updates it. If no matching profile exists, the API creates one.
Use this channel to map WordPress user data to user attributes and site activity to user events. Depending on your data plan, you can send a registered user's profile fields as attributes, represent a form submission as an event, or represent a completed order as an event.
Set it up
Plan the user data you will send and get the plan approved by the Insider One team. Then use the Upsert User Data API Integration Wizard to generate an API key, configure headers, and prepare payloads.
Build an integration job that retrieves the required WordPress records through your chosen extraction method.
Transform the records into the required API payload. Place user identifiers under the identifiers object, and use one identifier per user object where possible.
Test the mapping with a small sample and review the API responses.
Run the integration job at the frequency your use case requires.
For payload parameters, limits, and error handling, see Upsert User Data API. For guided setup, see the Upsert User Data API Integration Wizard.
Import channel 2: FTP/SFTP
The FTP/SFTP integration allows InOne to read comma-separated values (CSV) or tab-separated values (TSV) files from your file server on a schedule and import their data into user profiles and events. InOne supports FTP, FTPS, and SFTP.
Your integration process is responsible for extracting WordPress data and publishing the formatted files. The Insider One integration reads those files from the configured server, not directly from WordPress.
Set it up
Extract the required WordPress data and transform it into CSV or TSV files that meet the import requirements.
Publish the files to your FTP, FTPS, or SFTP server.
In InOne, navigate to Components > Integrations > External Integrations, select FTP/SFTP, and enter your server connection details.
Configure the file settings and map user identifiers, attributes, and events.
Set the import schedule to match when your integration process makes the files available.
For protocol selection, credentials, file requirements, and data mapping, see Import Data from FTP/SFTP to InOne.
Import channel 3: Amazon S3
If your data pipeline uses AWS, you can publish WordPress data to an Amazon S3 bucket you own. The Insider One Amazon S3 integration supports CSV and JSON Lines (JSONL) files containing user attributes and events, including purchase data.
Your integration process prepares and uploads the files. Insider One reads the resulting files from S3 rather than retrieving records directly from WordPress.
Set it up
Extract the required WordPress data and transform it into CSV or JSONL files that meet the import requirements.
In InOne, navigate to Components > Integrations > External Integrations and create an Amazon S3 source integration.
Authorize Insider One to read from your bucket and configure the required bucket, path, and data mappings.
Configure an Amazon Simple Queue Service (SQS) queue for new-file notifications, as described in the integration guide.
Publish export files to the configured location so that new-file notifications can trigger imports.
For AWS authorization, notification setup, file requirements, and data mapping, see Import Data from Amazon S3.
Related resources
Insider Tag Integration and Google Tag Manager, to add the Insider Tag to your website.
Integration Hub, to browse the platforms you can connect to Insider One as a source or a destination in the InOne panel.