Segments
Automatic visitor segments, computed from events, usable in surveys, promos, trigger rules and ad audiences.
Every site's people are classified automatically from the last 90 days of events. Nothing to configure: the segments appear under Segments in the dashboard, on each visitor, and can be targeted by surveys, promos and trigger rules.
The segments
| Group | Segment | Rule |
|---|---|---|
| Lifecycle | New | First seen in the last 7 days. |
| Returning | Known for more than 7 days and seen in the last 30. | |
| Dormant | Not seen for 30 days or more. | |
| Value | First-time buyer | Exactly one purchase. |
| Repeat buyer | Two or more purchases. | |
| High value | Top 20% of the site's buyers by spend. | |
| Intent | Cart abandoner | Added to cart in the last 7 days, over an hour ago, and did not buy since. |
| Checkout abandoner | Started checkout under the same conditions. | |
| Identity | Identified / Anonymous | Resolved to a person by email or phone, or not yet. |
| Traffic | Paid / Organic / Direct | How the person first arrived: an ad click id or paid utm_medium; search, social, referral or email; or nothing at all. |
| Dimensions | country:BD, device:mobile | The person's most frequent country and device type. |
A purchase, cart or checkout is whatever your event definitions
map to those conversions, so a store whose checkout event is begin_order is classified
correctly. Segments are per site and per person: a shopper's two devices count once, and
being a repeat buyer of one store says nothing about another.
How fresh they are
Segments are recomputed every fifteen minutes for sites with new events and once a night for every site. Refresh now on the Segments page recomputes on the spot (once a minute per site).
Targeting
A survey or promo can be aimed at one or more segments; a visitor in any of them qualifies, and a visitor in none is not even sent it. Trigger rules see the visitor's segments too:
if (ctx.visitor.has("cart_abandoner")) ctx.onExitIntent(ctx.show);ctx.visitor.segments is the full list. The tag learns them at boot from
GET /v1/engage?did=…, which answers with visitor.segments.
Ad audiences
On the Segments page, any segment can be kept in sync at an ad platform as an audience (Pro plan and above):
- Meta Custom Audience — needs the Meta destination connected and the ad account id
that will own the audience (
act_…). Members are sent as SHA-256 hashes of email, phone, name, city, state, zip and country, the same hashes the Conversions API uses. - Google Customer Match — needs the Google Ads destination connected. Members are sent as hashed email and phone through an offline user-data job.
The audience is created at the platform on the first sync. Every hour (and on Sync now) PixelFox sends only the people who joined the segment since the last sync and removes the ones who left. Only identified people are included, since an audience needs a contact key. A platform refusal is shown on the audience with its reason; the next sync retries the same difference.