Talon.One
Overview
The Talon.One source syncs customer sessions, events, campaigns, customers, stores, coupons, and referrals from one application into your destination. Nested attributes and other structured fields are retained as JSON.
The connector uses the Talon.One Management API.
Source setup
Ask your Talon.One administrator for:
- Your deployment prefix, including its region when applicable.
- The numeric Application ID you want to sync.
- A Management API key authorized to export customer sessions and read each selected stream for that application.
In Extract, add a Talon.One source and enter:
| Field | Description | Example |
|---|---|---|
| Subdomain | The deployment prefix, without https:// or .talon.one. Regional prefixes are supported. | company.us-west2 |
| Application ID | The application authorized by your Management API key. | 5 |
| Management API Key | Your key, entered either alone or with its ManagementKey-v1 prefix. | Use your own key. |
For example, company.us-west2 connects to https://company.us-west2.talon.one.
During login, Extract validates access to the selected application's customer-session export:
GET /v1/applications/{application_id}/export_customer_sessions
Application-scoped keys are supported. The key does not need permission to list all applications through /v1/applications.
Extract supplies the Authorization: ManagementKey-v1 <key> header automatically. You do not need to configure request headers.
Connection setup
Create a connection from your Talon.One source to a destination, select the streams you need, and configure the sync schedule and destination settings.
The Application ID belongs to the source account. To sync another application with a different scoped key, create another Talon.One source with that application's ID and key.
Data streams
| Stream | Primary key | Default sync mode |
|---|---|---|
customer_sessions | applicationid, id | Incremental on updated |
campaigns | application_id, id | Incremental on updated |
stores | application_id, id | Incremental on updated |
events | application_id, id | Incremental on created |
customers | application_id, id | Full Refresh |
coupons | applicationid, id | Full Refresh |
referrals | applicationid, id | Full Refresh |
Additional streams are disabled by default. Select only streams your key has permission to read. Login checks Customer Sessions access; each selected stream is checked when it syncs.
The Customer Sessions export retains Talon.One's CSV column names, including integrationid, profileid, profileintegrationid, and store_integration_id.
JSON list endpoints use snake_case field names, such as integration_id and profile_id.
Nested columns such as attributes and cartitems are parsed as JSON. Custom session fields remain inside attributes; they are not separate top-level columns. Use your destination's JSON query tools to access those fields.
Sync behavior
- The first run backfills all sessions available through the export endpoint.
- Later runs retrieve updated sessions, with a one-second overlap to include changes at the timestamp boundary.
- The cursor advances only after the entire export succeeds. A failed export is retried from the previous saved cursor.
- Events use creation-time bounds and a one-second overlap. Their nested
effectsvalues are included. - Campaigns and stores scan all pages on each run and emit rows within the update-time bounds, because those APIs do not support an update-time filter. Campaign updates to external entities, such as coupon usage, do not change the campaign's
updatedfield; use Full Refresh to reread these values. - Customers, coupons, and referrals reread all available records on every run, because their APIs do not expose a reliable update timestamp.
- Full Refresh rereads all available records in the selected stream on every run.
Use a destination mode that updates existing records using the primary key. Repeated session updates and the boundary overlap can return the same session in multiple runs.
Limitations
- Archived sessions cannot be exported.
- Deleted sessions are not returned as deletion records, so this source does not remove them from your destination automatically.
- The connector uses read-only endpoints and does not create, update, or delete Talon.One objects.
- Account-wide streams such as loyalty programs and audiences are not included.
- Paginated APIs do not provide a snapshot across pages; concurrent changes can appear on a subsequent run.
Troubleshooting
Login returns 401 or 403
Verify that the key is a Management API key, that the Application ID matches the key's scope, and that the key can export customer sessions for that application. A key that can export one application might not be allowed to list all applications; listing permission is not required by this connector.
The deployment prefix is rejected
Enter only the prefix, such as company.us-west2. Omit https://, the .talon.one suffix, ports, and URL paths.