Audience Sync

Audience Sync builds audiences from the conversions Convultra has recorded and pushes them to your ad platforms as first-party match lists. A rule such as “purchase in the last 90 days, value over $150” fills itself, refreshes on a schedule, and drops people who stop matching. No CSV exports and no manual uploads.

It is included on Growth (5 audiences), Scale (unlimited) and Agency plans (5 per client). Starter does not include it.

Where audiences can go

One audience can sync to several destinations at once. Each destination is its own list on the platform, created by Convultra the first time it syncs.

Requirements

• A connected Google Ads or OpenAI Ads integration on the project. See Connecting Google Ads.
• Conversions that carry an email or phone number. The WordPress plugin, the SDK’s enhance() method and payload auto-detection all supply this. See Enhanced conversions.
• Google Ads connected before Audience Sync shipped? The New audience modal will show Reconnect to enable audience sync next to that account. Google needs one extra permission (the Data Manager scope) that older connections do not hold. Spend sync and conversion forwarding keep working while you do this.

Create an audience

1. Open Audiences in the dashboard and click New audience.
2. Name it. The name is also used for the list on the platform, so make it recognizable in Google Ads or OpenAI Ads.
3. Set the rule. Choose a conversion type (purchase, lead, signup, subscription, download, contact, schedule) or identified themselves for anyone who has been matched to an email or phone regardless of what they did. Pick a window from 1 to 540 days. Optionally add a minimum total value, which applies to the person’s combined value inside the window, not to a single order.
4. Check the estimate. The builder shows how many people match today and how many joined over the last seven days, so you can see whether the rule is too tight before you save it.
5. Pick destinations. Tick each connected account the audience should sync to. For OpenAI Ads, also choose the intended use: inclusion (targeting), exclusion (suppression) or bid multiplier.
6. Choose the cadence. Any cadence from every 15 minutes to daily, per audience. Growth plans sync daily, Scale plans hourly or faster.
7. Save. The first sync creates the list on the platform and uploads the current members. Later syncs send only the changes.

Sync modes

Mirror (default, and the only mode on OpenAI Ads). The platform list always matches the rule. When someone falls outside the window, or you edit the rule, the next sync removes them. This is the mode to use for exclusions and for any list where freshness matters.

Add-only (Google Ads only). Members are added but Convultra never sends removals. Google expires them itself after the membership lifespan, which Convultra sets to the rule window. Use it when you want Google’s own expiry behavior or when a list is shared with uploads from elsewhere.

Changing the rule or the mode triggers a full refresh on the next sync: the list is cleared and rebuilt.

OpenAI Ads specifics

• Size minimums. OpenAI needs at least 25,000 matched users before a list can be used for targeting or bid adjustments. There is no minimum for exclusion, so a small audience still works as a suppression list from day one.
• Sizes are ranges. OpenAI reports list size as a band (under 25,000, 25,000 to 100,000 and so on) rather than an exact count, and the count is not available until the list has processed. Convultra shows the same band.
• Matched, not uploaded. The threshold counts users OpenAI could match, not identifiers you sent. Uploading 30,000 emails does not guarantee 25,000 matches.
• Audiences use the same Ads API key as spend sync. No extra credential is needed.

What is sent

Only SHA-256 hashes of email and phone. Identifiers are hashed as soon as a conversion enters the audience pipeline, so the audience store, the sync jobs and the dashboard never hold a raw address. Members are never listed in the dashboard or exposed through the API; you see counts, rule summaries and sync history.

If you remove a conversion, the person leaves any audience it qualified them for on the next evaluation, and a mirrored destination receives a real removal.

Monitoring

Each audience shows its member count, destinations, last sync and next sync. Sync history lists every job with its operation (add, remove, full refresh), status and the platform’s response. Sync now forces an immediate run.

A destination in an error state usually means the platform rejected the credentials or the list. Reconnect the integration and sync again. Paused destinations keep their members but stop receiving changes.

Limits

Any cadence from every 15 minutes to daily, per audience. Growth plans sync daily, Scale plans hourly or faster.