Send audiences to OpenAI Audiences

OpenAI Audiences syncs an Amperity audience to an OpenAI custom audience, so you can target, exclude, or bid-adjust those customers in your OpenAI ad campaigns. Members are matched to OpenAI users on a single hashed identifier — an email address or a phone number — that you choose when you configure the destination. The connector uses the OpenAI Advertiser API.

Beta

The OpenAI Audiences connector is currently in beta. Contact your Amperity representative to learn more.

Note

This destination uses the OpenAI Advertiser API .

Important

OpenAI Audiences updates membership incrementally. Each run sends only the members who joined or left the audience since the last run: new members are added first, then members who left are removed. Members already in the audience are left in place and reported as unchanged. Amperity tracks these membership changes itself, so it never resends the full audience.

Caution

A single identifier is sent per member — the Match identifier you configure applies to every member of the audience. Because that identifier is also how Amperity tracks membership, it cannot be changed without recreating the audience, and match rates are typically lower than a connector that sends several identifiers per person. OpenAI counts a user matched on either email or phone as one member, but only one identifier column can be sent.

Note

Membership is matched in the background. A successful orchestration means OpenAI accepted the members, not that they matched a user or that the audience is usable for targeting yet. OpenAI reports matched-audience sizes only as privacy-preserving ranges and never returns per-member results, so a run cannot confirm that any specific member matched — confirm the audience size in OpenAI Ads Manager.

Caution

Amperity resolves the List name to an audience on the account, creating one if it does not exist, and reuses it on later runs. OpenAI audiences cannot be deleted, and archiving is permanent: an archived audience cannot be restored, targeted, or written to. If the configured audience was archived, enter a new List name and Amperity creates a fresh audience.

Note

An OpenAI custom audience needs roughly 25,000 matched users before it can be used for inclusion targeting or bid adjustment. Below that size it can still be used for exclusion, which has no minimum matched size.

Note

OpenAI custom audiences are not supported for campaigns that target the European Economic Area (EEA) or Switzerland. Confirm your campaigns target other regions before syncing.

Note

If OpenAI rejects a membership batch, Amperity reports that batch’s members as failed rows and stops the run without sending the remaining batches. Re-running is safe: Amperity resubmits each batch so an interrupted change resumes rather than being applied twice.

The steps required to configure campaigns to send audiences to OpenAI Audiences.

Note

Ask your DataGrid Operator or your Amperity representative for help configuring OpenAI Audiences as a destination to which you can send campaigns for customer activation.

Caution

This destination is available for sending campaign audiences to OpenAI Audiences after it is configured by a Datagrid Operator or your Amperity representative.

If this destination cannot be selected from the campaigns editor or activations canvas ask your Datagrid Operator or Amperity representative to configure a destination for sending campaign audiences to OpenAI Audiences.

Build a segment

Use the Segment Editor to build any audience using a series of drop-downs and picklists.

As you define the attribute profile for an audience be sure to refresh segment insights to view audience size and to see the value it brings to your business.

When the segment is ready, activate it, and then use it use it in a campaign to send to your preferred destinations for customer activation.

About segments that use the sub-audience editor

You can use any attribute that is in your customer 360 database to define your audience.

When sending the list of customers who belong to this audience to OpenAI Audiences as part of a campaign you must choose specific attributes to send.

OpenAI Audiences supports the following attributes: audiences.

Important

Validate the audience with OpenAI Audiences by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by OpenAI Audiences. Send the sample audience to OpenAI Audiences and verify the sample audience is correct in OpenAI Audiences. Make adjustments if necessary. Only send full audiences after validation is complete.

Add to a campaign

Use the campaign editor to configure Amperity to send data to OpenAI Audiences. Add a segment, define exclusions and sub-audiences, and then define each audience sent to OpenAI Audiences.

	Open the Campaign Editor. This is available from the Campaigns page. Click the Create campaign button in the top right corner of the page.
	Assign OpenAI Audiences as a destination for at least one treatment group. Note You may need to edit the attributes for the sub-audience to ensure Amperity is sending the right data to OpenAI Audiences.
	Click Edit attributes to review the attributes that Amperity sends to OpenAI Audiences. a single hashed email or phone identifier Amperity pre-selects the list of attributes sent to OpenAI Audiences. The Edit attributes page for OpenAI Audiences is similar to: Note The Merged Customers table is the default table for sending data to OpenAI Audiences, even though segments are often built against the Customer 360 table. This is by design. The Merged Customers table is the underlying table for customer profile data and is the source for all customer profile data that exists within the Customer 360 table.

Configure default attributes

Each unique destination configured to send treatment group audiences to OpenAI Audiences has a set of default attributes.

Configure default attributes by clicking the Default attributes link next to the Create campaign button on the Campaigns page.

The source table defaults to the Merged Customers table for most attributes. This is configurable.

OpenAI Audiences sends a single identifier per member — the one that matches the Match identifier configured on the destination. Map the default attribute for the campaign to the column that matches that setting.

Source attribute	Required?	Destination attribute
email / phone / email_sha256 / phone_number_sha256	Yes	The one column that matches the configured Match identifier. Amperity hashes raw email and phone values with SHA-256 before sending; the email_sha256 and phone_number_sha256 columns are sent as supplied. Plaintext identifiers never leave Amperity.