Use case

Keep ad audiences current from your customer data

Build a segment once in Argon. Sync sends its members to your ad platforms and keeps the list current as people join and leave.

Talk to usSee it step by step

At the Hypothesis stage. Uses 2 Argon modules: customer profiles (Profiles) and reverse ETL (Sync).

Audience

Warm trial users

  1. SegmentViewed pricing twice, not a customer yet
  2. Send to[AD PLATFORM]
  3. Update[SCHEDULE]
  4. LeaveWhen they no longer match

Step by step

How a segment becomes an ad audience

Audiences for ads has 3 steps. It’s at the Hypothesis stage, so details may change.

  1. Segment

    Build the segment

    Combine events and traits with plain rules, like “viewed pricing twice and isn’t a customer yet”. Membership updates as events arrive.

    Runs on Profiles

    Segments / High-intent trialsLive
    WHOdidpricing_viewedat least 2 timesin the last 7 days
    ANDtraitplanistrial
    ANDnot in segmentCustomers
    Membership, last 14 days2,418 people
    Membership updates as events arrive. Used by 3 journeys.

  2. Destination

    Choose where it goes

    Pick the ad platform and account to send to. [WHICH AD PLATFORMS SYNC SUPPORTS, AND WHEN.]

    Runs on Sync, at the Hypothesis stage

  3. Update

    Keep it current

    Sync sends the segment’s members on a schedule. People who join are added, and people who leave are removed.

    Runs on Sync

  4. The audience keeps itself current

    People who stop matching the segment leave the audience at the next update, so you stop paying to reach them.

Modules

What it takes

This use case needs 2 Argon modules. Sync is at the Hypothesis stage.

Needed

To build and send the audience

Optional

To do more with it

Tell us where your audiences should go

Tell us which ad platforms you use and who you want to reach. We’ll tell you what Sync can do today.

Talk to usSee Sync