AB Tasty
Sync audience membership into AB Tasty Web Personalization segments for A/B testing and personalization campaign targeting. Zeotap pushes visitor IDs and optional attribute values through AB Tasty’s Universal Data Connector (UDC), and the resulting segments become selectable when targeting experiments and personalization campaigns in the AB Tasty UI.
AB Tasty Feature Experimentation (Flagship) is not supported by this destination — Flagship evaluates segment membership from decision-time visitor context rather than from persisted audience data, so there is no server-side audience-push flow to integrate with.
Prerequisites
- An AB Tasty Web Personalization tenant (not Feature Experimentation).
- The Universal Data Connector enabled on your account. UDC is provisioned by AB Tasty Support — open a ticket to request it for your account.
- An OAuth2 client ID and client secret with access to the public API.
- The
partner_nameidentifier AB Tasty assigns when they enable UDC for you. - Your AB Tasty Account ID.
Authentication
AB Tasty uses OAuth 2.0 (Client Credentials).
- In AB Tasty, navigate to Integrations → Public API Access and create a new API client.
- Grant the client permission to call the Universal Data Connector.
- Copy the Client ID and Client Secret.
- Paste them into Zeotap when creating the destination.
Zeotap exchanges the credentials for a short-lived access token on every sync and caches it for its documented ~12-hour lifetime.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Account ID | Text | Yes | Your AB Tasty account identifier. Found in AB Tasty Settings → Account information. |
| Partner Name | Text | Yes | The UDC partner identifier AB Tasty provisions for your account. Obtained from AB Tasty support when UDC is enabled. |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Segment Name | Text | Yes | The audience label written to AB Tasty. This name appears in the AB Tasty UI and is selectable when targeting experiments or personalization campaigns. |
| Expiration (days) | Number | No | How long newly added visitors remain in the segment. Leave blank to use AB Tasty’s default retention of 30 days. Applied to Add rows only; Remove and mirror-departed rows are expired immediately. |
Supported Operations
Sync Modes
| Mode | Supported |
|---|---|
| Insert | — |
| Upsert | — |
| Update | — |
| Mirror | — |
AB Tasty is an audience-only destination — record-level CRUD is not part of the API surface.
Audience Sync Modes
| Mode | Supported |
|---|---|
| Add | Yes |
| Remove | Yes |
| Mirror | Yes |
Features
- Field Mapping: Yes
- Schema Introspection: No
Field Mapping
| Destination Field | Type | Required | Description |
|---|---|---|---|
visitor_id | String | Yes | The unique visitor identifier AB Tasty uses for segment targeting. If unmapped, Zeotap falls back to the model’s primary key. |
value | String | No | Optional per-row attribute value written alongside the segment membership. Use when your campaign targeting rules need a discriminator beyond simple membership. |
How It Works
Zeotap serializes each batch into a CSV body with four columns — visitor_id, segment, value, expiration — and posts it to AB Tasty’s Universal Data Connector endpoint for your account and partner name.
The expiration column is derived from the sync mode so you never have to model it yourself:
- Add rows use the configured Expiration (days) TTL, or AB Tasty’s 30-day default when the field is blank.
- Remove rows use
-1, which AB Tasty interprets as an immediate expiry. - Mirror rows inspect the per-row change type: newly added rows use the TTL; rows that fell out of the audience use
-1.
The segment column on every row is populated with the configured Segment Name. Enabling the “Use connected audience/model name” toggle on the sync auto-fills this value from the connected audience.
Rate Limits / Quotas
Each upload request accepts up to 100,000 rows or 20 MB, whichever is lower. Zeotap splits large batches into chunks respecting both limits. Uploads for a single destination are processed sequentially; AB Tasty queues per-integration work server-side, so serialized uploads avoid out-of-order add/remove ordering issues.
Troubleshooting
Test destination fails with “invalid client credentials”
Re-check the Client ID and Client Secret. Regenerate the client in AB Tasty if it has been revoked, and confirm it has permission to call the public API.
First sync fails with a 404
This usually means the configured Partner Name is not provisioned for your account. UDC has no way to verify the partner name ahead of time, so the test step cannot catch this. Contact AB Tasty support to confirm UDC is enabled and that the partner name matches the identifier they issued.
Visitors sent but not appearing in AB Tasty campaigns
Confirm the Segment Name on the sync matches the audience label your campaign is targeting inside AB Tasty. AB Tasty accepts the data regardless of whether a campaign references the segment — it’s the campaign setup that connects the two.
Missing visitor_id
Every row must resolve a visitor ID. Zeotap uses the visitor_id field mapping first, then falls back to the model’s primary key. Rows that resolve neither are skipped and counted as failures.