Skip to content

Area: User guide

How segment syncs work

A segment sync connects one Releva segment to one audience on an ad platform. Releva calculates the segment, sends its profiles to the platform, and sends them again on a schedule so the audience follows your customers’ behaviour. You manage syncs under Data Platform › Sync Segments.

Releva has two ways to work with ad platforms, and their names are close.

Segment with scope Google or Facebook Segment sync
Where Data Platform › Segments, Scope set to Google or Facebook Data Platform › Sync Segments
What it is A rule set (for example URL rules for web page visitors) that the ad platform evaluates itself A Releva behavior segment whose profiles Releva uploads to the platform
Who builds the list Google or Facebook, from the rules Releva, from your tracked events and orders
Typical use Retarget visitors of certain pages Target or exclude customers Releva knows, such as repeat buyers or churn risks

Only segments with the scope behavior can be synced. The segment picker on the sync form hides the other scopes. For how to build a Google or Facebook segment, read How segments work.

Google. Releva creates an audience in your Google Analytics 4 property and fills it with the segment’s profiles. The audience appears in Google Analytics as Releva audience for segment sync: <id>, with the description “In Releva segmentId <segment id>”. A profile stays in the audience for 30 days after Releva last sent it. Each scheduled sync sends the profiles still in the segment again, so profiles that leave the segment drop out of the Google audience after 30 days. You need a Google account connected under Settings › Google with a GA4 property.

Facebook. Releva creates a custom audience in your Meta ad account named <sync name> - <id> (custom file audience method) and uploads the segment’s profiles. You need a Facebook account connected and enabled under Settings › Facebook & Whatsapp, an ad account (the one in your settings, or a different one chosen on the sync with Sync to another Facebook Ad account), and both the Custom Audience and Value Based Custom Audience terms of service accepted in Business Manager. The sync form warns you if the terms are not accepted and keeps Create disabled until they are.

The <id> in both names is a unique identifier Releva assigns to the sync when it is created. The card on the Sync Segments page shows it after the first successful sync, together with the platform’s audience id.

A Facebook sync can also ask Meta to build a lookalike audience from the synced one. Tick Enable lookalike audience creation and choose a Lookalike Type:

  • Reach: a larger number of profiles which are somewhat similar to your source audience.
  • Similarity: a smaller number of profiles that are very similar to your source audience.
  • Custom ratio: the top 1%-20% of people most similar to your source audience, set with the Ratio % slider (default 3). Lower percentages give higher precision with smaller reach.

Meta is only asked for the lookalike once at least 100 profiles were synced. Below that, Releva skips the lookalike without an error and tries again on the next scheduled run. The lookalike is named Lookalike (<type>) - <sync name> - <id> (custom file audience method).

Choose the lookalike and its type when you create the sync: Lookalike Type is locked on an existing sync, so adding a lookalike later fails. To add one, delete the sync and create it again. Once a sync has a lookalike audience you cannot turn it off on the sync; delete the sync instead.

A sync runs in the background. The card shows Syncing… in place of the On/Off switch while it runs.

Trigger What happens
You create a sync A first sync is queued immediately. The sync starts On.
Scheduled run Once a day at midnight UTC by default. Every sync that is On in the shop is run. The schedule is the cron expression in Audience Sync Schedule under Settings › Facebook & Whatsapp.
Sync Now next to Audience Sync Schedule Queues a sync for every Facebook sync that is On. Google syncs are not included.
You turn a sync Off Nothing is sent. A Facebook audience keeps the profiles it already has. In a Google audience, profiles drop out 30 days after they were last sent.
You turn a sync On again No immediate sync. The next scheduled run updates the audience.

A sync that is Off is skipped even if a run was queued for it.

Prerequisites are checked at run time, not when you save the form. If the Google or Facebook account is missing, the ad account is not set, or the Facebook terms are not accepted, the run is logged on Releva’s side and the audience is not created or updated. The Sync Segments page shows no error for a skipped run: the card simply returns to the switch. If an audience does not appear on the platform, check the prerequisites above first.

  • Deleting a Facebook sync also deletes the custom audience in your ad account, if one was created.
  • Deleting a Google sync leaves the GA4 audience in place.
  • Turning a sync off never deletes anything on the platform.