Insider One provides API, panel, cloud storage, and webhook options that help you transfer supported customer data to your own systems.
Select an export method based on the data you need, the expected volume, and whether your migration requires a point-in-time export or an ongoing data feed. Plan and test your exports before completing your offboarding process.
Review the applicable data retention periods before defining your export timeline. Complete the required exports while your account and the relevant data remain available.
Choose an export method
Export method | What it exports | Format and delivery | Limits and considerations |
|---|---|---|---|
Contact attributes and events for users selected through a saved segment or an events query. Attribute and event data arrive in separate files that you can join using | CSV or Parquet files. Collect the signed download URLs through the status endpoint, a webhook, or both. | Up to 10 export requests per account per UTC day. The quota resets at 00:00 UTC. Requests that return a non-success response do not count toward the daily quota. Signed download URLs remain valid for approximately 24 hours. | |
Requested user attributes and events for users in a Dynamic Segment. | CSV, Parquet, or JSON. Insider One sends the download link to the webhook endpoint specified in the request. | One successful export request per UTC day. The download link remains valid for 24 hours. Use V2 for new export integrations. | |
Users in a saved Dynamic Segment, including their identifiers and selected profile attributes. | CSV file requested from the Dynamic Segments page in the Insider One panel. | You can include up to 20 additional attributes in one export. | |
Contact export | Contacts and the profile fields supported by the selected panel export. | File requested from the applicable Audience or contact view in the Insider One panel. | The available fields and export scope depend on the selected contact view. |
Cloud storage export | Selected event data and supported fields generated after the destination integration is activated. | Scheduled CSV files sent to Amazon S3, Google Cloud Storage, or Microsoft Azure Blob Storage. | You can select an export interval of 1, 2, 4, 6, 12, or 24 hours. A shared limit of five destination integrations applies across the supported cloud storage destinations. These integrations export data generated after activation. |
Selected user attribute changes or events with the fields configured for the stream. | JSON payloads sent to an HTTP endpoint managed by your organization. | The feed starts after activation and covers the attributes, events, and fields selected in the webhook configuration. |
Recommended API: Use Raw User Data Export API V2 for new bulk export integrations. V2 provides asynchronous processing, a higher daily request limit, status polling, and webhook delivery.
Review the linked API or integration guide for authentication requirements, supported fields, output schemas, and destination-specific limits.
Plan your data export
Complete the following steps before starting your migration or offboarding process:
Define the required data: List the profiles, attributes, identifiers, events, consent records, coupon source files, and product-specific information that your organization needs to retain.
Check data retention: Review the data retention periods for the events and records included in your export.
Select the export method: Use a bulk export for a point-in-time transfer. Configure a cloud storage export or Data Stream when your migration requires ongoing updates.
Run a test export: Export a controlled user group or date range and validate the schema, identifiers, timestamps, and record counts.
Plan the full export: Divide large transfers into suitable segments or date ranges based on the selected method and its limits.
Validate the destination: Confirm that your destination can process the files and associate profile data with event data.
Download files promptly: Raw User Data Export API download links remain valid for a limited time. Copy the generated files to your own storage before the links expire.
Export profiles and events
Use Raw User Data Export API V2 to export contact attributes, events, and event parameters at scale.
You can select users through a saved segment or define the user set through an events query. You can request specific attributes or use * to include all attributes registered for your account.
V2 creates separate attribute and event files. Use insider_id to join the exported datasets in your destination.
For a panel-based export, select a saved Dynamic Segment and request a CSV file. The export includes the users in the segment and can include up to 20 additional profile attributes.
Refer to Which API Should I Use? to compare bulk exports with APIs designed to retrieve specific user profiles or manage user data.
Transfer ongoing changes
Use a cloud storage export or Webhook (Data Stream) when your migration plan requires ongoing data delivery before the final transition.
Cloud storage exports
Cloud storage integrations send selected event data to a customer-managed destination at the configured interval. Select the guide for your destination:
Cloud storage exports include data generated after the integration is activated. Use a bulk export when your migration also requires data from an earlier period that remains available within the applicable retention window.
Exported files are windowed by when each event was recorded in Insider One (UCD entry time), not by the event's own timestamp, so exported row counts will not match the panel or Statistics APIs one-to-one.
Webhook (Data Stream)
Data Stream provides event-driven delivery to your endpoint. Configure an Attribute Stream for selected user attribute changes or an Event Stream for selected events.
Follow the Insider One Webhook Configuration guide to select the data, define the payload, configure the endpoint, and review delivery behavior.
Use an ongoing feed together with a bulk export when your migration requires both an initial dataset and changes generated during the transition period.
Prepare consent and preference data
Include the applicable opt-in and consent attributes in your profile export. Examples can include email_optin, sms_optin, whatsapp_optin, and data-processing consent attributes registered for your account.
Profile opt-in attributes and channel suppression states serve different purposes. An opt-in attribute records a user's permission, while a channel suppression state affects whether the channel can send messages to the user.
Review profile permissions and channel subscription states when defining the consent records required by your migration. Refer to Data Governance for the applicable Unsubscribe and Resubscribe APIs.
Consent scope: Confirm which profile consent attributes and channel subscription records your organization needs to retain. Validate each record type separately during the export.
Prepare coupon data
Review the coupon lists used by your campaigns and journeys before offboarding. Retain the original coupon files, coupon generation records, and related source data managed by your organization.
Use the Coupon Lists page to review each list's type, status, usage, creation date, and expiration date. Refer to FAQ about Coupon Management for the current coupon management and export behavior.
Document which campaigns and journeys use each coupon list before preparing the corresponding setup in the destination system.
Prepare journey information
Use the Journey List API to retrieve supported journey metadata. The response includes information such as journey names, statuses, creation and execution dates, tags, starter types, conversion goals, exit criteria, and campaign references.
You can use this metadata to create an external journey catalog, support an audit, or prepare a visual review of your journey setup.
For a transition between supported domains under the same account, use Duplicate Journey to Other Accounts. Review the duplication summary before continuing because the destination account can require additional configuration.
After duplication, open the journey in the destination account and validate the journey flow, channels, content, events, attributes, segments, goals, exit criteria, dynamic content, and coupon dependencies before activation.
Journey preparation: The Journey List API provides supported journey metadata. The panel duplication feature helps you prepare supported journeys in another domain under the same account. Review each duplicated journey visually and complete its destination-specific configuration.
Complete your offboarding
Start your final export before your account access ends. Allow enough time to submit export requests, download the generated files, validate the results, and resolve incomplete requests.
Following termination or expiration of the services, Insider One securely deletes Customer Data within 180 days, subject to the terms and exceptions defined in the applicable agreement and Data Processing Agreement.
Contract terms: Review your applicable agreement and Data Processing Agreement for the deletion commitment that applies to your organization. Complete the required exports before your account access and data availability end.
Store the exported data in a destination that meets your organization's retention, access, privacy, and security requirements.
Offboarding checklist
Confirm the data types and historical periods required by your organization.
Review the applicable data retention periods.
Select the required bulk and ongoing export methods.
Verify API credentials, cloud storage credentials, and receiving endpoints.
Test each export method and document its output schema.
Download generated files before their signed links expire.
Validate profile, event, consent, and product-specific records.
Retain the coupon source files and related records managed by your organization.
Export journey metadata and review journey duplication requirements.
Confirm the termination date and the deletion terms in your applicable agreement.
Complete and validate the final export before account access ends.