Send audiences to ad platforms or share customer data with your warehouse, cloud storage, or other systems. Choose a route based on what you need to send and when the destination needs it: on a schedule, when an event or journey step occurs, or on request.
This article covers:
Choose an outbound route
Route | What it sends | Timing | Typical use | Guide |
|---|---|---|---|---|
Remarketing Segments (Ad Audiences) for Google Ads, Meta, and TikTok | The users in a Dynamic Segment, matched by hashed email address and phone number. Google Ads and Meta also accept optional attributes. | Once a day at 00:00 in your InOne panel's time zone: users who entered the segment are added, and users who exited are removed. The ad platform can take up to 48 hours to show changes. | Remarketing, suppression, and lookalike seed audiences | |
Remarketing Segments (Ad Audiences) for ChatGPT Ads | The users in a Dynamic Segment, matched by hashed email address and phone number only. No other identifiers or attributes are sent. | On a regular schedule, not in real time: users who entered the segment are added, and users who left it are removed. The new audience size can take time to appear in ChatGPT Ads Manager. If the segment becomes empty, Insider One skips the update and ChatGPT Ads keeps the current audience members. | Remarketing and suppression. An audience needs at least 25,000 matched users for targeting; smaller audiences can be used for exclusion only. Not available for accounts in the European Economic Area (EEA) or Switzerland. | |
Architect ad elements: Google Ads Customer Match and Facebook Custom Audiences | Adds the user to, or removes the user from, the audience you select | When the user reaches the element in a journey. Meta can take 24 to 48 hours to process the update. Google typically takes 6 to 12 hours and can take up to 48 hours. | Audience changes tied to a journey step, such as a purchase | Architect Channel: Google Ads Customer Match, Architect Channel: Facebook Custom Audiences |
Dynamic Segment export to a comma-separated values (CSV) file | The users in a saved Dynamic Segment with their identifiers, plus up to 20 additional attributes you choose | On request, from the Dynamic Segments listing page | One-off lists for tools that accept file uploads | |
Raw Export API | Separate attribute and event files in CSV or Parquet for users selected by a saved segment or an events query. Join the files on insider_id. | On request. V2 allows 10 export requests per account per UTC day. Poll the status endpoint or use a webhook to get download links when the export is ready. | Bulk exports to data warehouses and business intelligence tools. Use V2 for new integrations. | |
Webhook (Data Stream) | Attribute Stream: changes to the attributes you select. Event Stream: the events you select, with their parameters and added attributes. Both send JavaScript Object Notation (JSON) payloads to your endpoint. | When Insider One collects a selected event or detects a change in a monitored attribute. You can throttle requests per endpoint. | Keep a customer relationship management (CRM) system up to date, or start workflows in other systems | |
Cloud storage exports | Selected event data, with the parameters and attributes you choose, as CSV files in Amazon Simple Storage Service (Amazon S3), Google Cloud Storage, or Azure Blob Storage | Every 1, 2, 4, 6, 12, or 24 hours | Analysis in your own storage, or loading into Google BigQuery through Google Cloud Storage | Export Data to Amazon S3, Export Data to Google Cloud Storage, Export Data from Insider One to Azure Blob Storage |
Data warehouse exports | Selected events with their parameters and attributes, shared with Snowflake or Databricks, or written to Amazon S3 for loading into Amazon Redshift | Snowflake and Databricks sync at the sync period you set, up to 24 hours. Check for data after the first sync that contains events. For Amazon Redshift, your pipeline loads the files from Amazon S3 on its own schedule. | Combining campaign engagement with your other business data | Export Data to Snowflake from Insider One, Export Data from Insider One to Databricks, Export Data from Insider One to Amazon Redshift |
Call an API in Architect | A request to your endpoint. Its body can include user attributes and event parameters. The Body Builder supports JSON and form-encoded bodies up to 100 kilobytes (KB). | When the user reaches the element in a journey | Updating a CRM, loyalty, or backend system after a journey step | |
Get User Profiles API | Selected attributes and events for one user, found by an identifier | When your system requests it | Profile lookups from a call center tool or another system | |
Meta Conversions API for Click to WhatsApp ads | Purchase events with currency, value, and the hashed phone number | Automatically, after Insider One records the purchase | Measuring return on ad spend in Meta Ads Manager |
Call an API sends one request for each user who reaches the element. For bulk exports, use the Raw Export API V2.
Each account can have up to five cloud storage exports in total across Amazon S3, Google Cloud Storage, and Azure Blob Storage. Snowflake, Databricks, and SFTP Export share one destination slot per account, so only one of them can be set up at a time, including draft and paused integrations. If the Destination option is disabled, hover over it to see which integration holds the slot. To free the slot, archive that integration.
Use synced segments as lookalike seed audiences
Lookalike audiences help you reach new customers who resemble your best ones. Sync a high-value Dynamic Segment, such as frequent purchasers or loyal customers, as an Ad Audience. Then, in the ad platform, select the synced audience as the source of a lookalike audience, where the platform supports it. The ad platform builds the lookalike audience.
The seed follows its segment: the daily sync adds customers who join it and removes customers who leave it. You can also build a seed audience in a journey with the Architect ad elements.
Apply ad consent when you sync audiences
The consent confirmation, Dynamic Segment filters, and Architect reachability checks serve different purposes:
When you create a Google Ads, Meta, or TikTok Ad Audience, you confirm consent for ads and personalization in the Consent section of the drawer. You can update this confirmation later from the segment's Ad Audiences tab.
An Ad Audience syncs the users who match its Dynamic Segment. To sync only users who gave the consent your advertising requires, add that consent, such as an attribute that records advertising consent, to the segment's conditions.
In journeys, the Google Ads and Facebook Custom Audiences elements pass only reachable users. Reachability depends on the identifier you select in Architect Settings: the user needs an email address or a correctly formatted phone number, as applicable, and their General Data Protection Regulation (GDPR) opt-in must not be false. Passing this check doesn't guarantee a match in the ad platform or replace your advertising consent rules. See Architect Journey: Reachability on Channels.
Keep consent attributes current on each profile, for example by sending changes from your consent management platform (CMP) with the Upsert User Data API. See Sync Consent Between Your CMP and Insider One.
Example: Suppress existing customers in acquisition ads
Use a suppression audience to exclude existing customers from campaigns aimed at new customers. This example uses Google Ads, Meta, or TikTok. For ChatGPT Ads, follow the separate setup guide.
Navigate to Audience > Segments > Dynamic Segments, click Create, and build a segment of your existing customers, for example, users who purchased in the last 12 months.
On the Dynamic Segments listing page, click the Create Ad Audience icon in the segment's Actions column.
Enter an Ad Audience Name, select the Ad Platform, and choose your ad account.
Optionally, set a Sync Expiration Date. Without a date, the audience syncs for 1 year unless you stop it.
For Google Ads, Meta, and TikTok, confirm consent for ads and personalization. Click Create.
In the ad platform, exclude the new audience from your acquisition campaigns.
Insider One creates the audience in the ad platform with the name you entered, and users join it at the next daily sync. From then on, new customers are added once a day, and customers who leave the segment are removed.
To send an update when a shopper reaches a journey step after purchase, use the On Event starter for the purchase event and set the Facebook Custom Audiences or Google Ads element to add users. The ad platform still needs time to process the update. See Architect Journey Starter: On Event and Architect Channel: Using Facebook Custom Audiences.
Send audiences to other platforms
Google Ads, Meta, TikTok, and ChatGPT Ads have built-in audience sync. For a destination without built-in audience sync, choose a route based on what it accepts: a Dynamic Segment export for a one-off list, the Raw Export API V2 for a bulk export, or a webhook or Call an API in Architect for ongoing updates. Your own integration handles delivery, matching, and any audience membership changes the destination needs. Scope this work with the Insider One team before you commit to a launch date. See Integrations and Connector Directory and Retail Media Activation.
Read ad results in the ad platform
Insider One manages who is in your ad audiences. You read ad delivery results, such as impressions, clicks, and spend, in the ad platform's own reporting. For the Architect ad elements, Insider One reports how many users arrived at the element, were reachable, and were dropped.
To connect ad traffic to website visits, add Urchin Tracking Module (UTM) parameters to the destination links of your ads. Use those tags to identify campaign traffic in your web analytics tool. You can also use Page Rules to show OnSite campaigns to visitors whose landing page URL contains the tags.
Retrieve past events
Scheduled exports and webhooks are for ongoing delivery and send data generated after you activate them. For events from before activation, or for gaps an export did not replay, use Export Raw User Data V2 and specify the event time range. You can only retrieve events that are still within their retention period. See Data Retention.