# Import Audience data from any 3rd-party solution (Custom pull)

This feature is in the early adoption phase. To benefit from it, please get in touch with your CSM.

#### Introduction

This guide outlines the steps to send your audience data to AB Tasty, making it available in the Segment Builder for use in your upcoming experiments (A/B tests, personalisations, patches).

{% hint style="warning" %}
**Note:** This feature is currently exclusive to Experience Optimisation Platform clients.
{% endhint %}

#### Overview

The **Custom Pull Connector** is a new method built on top of our **Universal Data Collector (UDC)**.\
It allows you to import audiences from your preferred tools, making them easily accessible for segment creation within AB Tasty.

### Integration Process <a href="#h_01jjrtb2vy7349r6agyw32hwzw" id="h_01jjrtb2vy7349r6agyw32hwzw"></a>

{% embed url="<https://fast.wistia.net/embed/iframe/nwt2wtwewy?seo=true&web_component=true>" %}

{% hint style="info" %}
Please follow the new link to our [Universal Data Connector technical documentation](https://app.gitbook.com/s/dG0EHdNiO40UVA7Bz9mR/data-apis/universal-data-connector)
{% endhint %}

The process consists of three steps:

{% stepper %}
{% step %}

#### **Create a Custom PULL Connector on APP2**

{% hint style="warning" %}
The `partner_name` used when creating the connector must **exactly match** the `partner_name` used in the POST request to UDC (step2)\
This ensures proper matching between your imported data and the connector.
{% endhint %}

**This step is made on the AB Tasty application**

1. Access your **AB Tasty Account > Integrations > Integrations Hub**
2. On the pull section, locate the **Custom Pull Card**

   <figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2FasydzOVn2vPGCjSDM320%2FCapture%20d%E2%80%99e%CC%81cran%202025-06-11%20a%CC%80%2012.03.16.png?alt=media&#x26;token=f9d9356b-5195-4812-80d7-418b6d0dc9bf" alt="" width="563"><figcaption><p>Custom Pull Card is highlighted when you don't have any</p></figcaption></figure>
3. Create your custom pull connector:
4. **Connector Name**\
   This name will help you identify your audience source within the Segment Builder.
5. **Partner Name**\
   Used to identify the origin of your data.\
   It must match the partner name when sending data to AB Tasty through UDC.
6. **Storage Location for Visitor\_ID**\
   Select where the visitor ID is stored. Our connector will use this to retrieve the ID and match it in UDC:
   * **Local Storage** – The connector will look for a specific entry in the browser’s Local Storage.
   * **Cookie** – The connector will look for a specific cookie.
   * **AB Tasty Method** – Use `ABTasty.setCustomPullVisitorId('id')`

     to set the visitor ID manually.
   * **BYOID** – If Bring Your Own ID (BYOID) is implemented, the connector will use the configured method to retrieve the ID.
7. **Key**\
   Enter the name of the key to retrieve the visitor ID, based on the selected storage method above.\ <br>

   <figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Flefj8aQomZfRM3Ywxbno%2Fimage.png?alt=media&#x26;token=e0106a8a-6706-43d7-90a0-fb40553bcb27" alt="" width="375"><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Send Data to UDC

**This Step is made on your end & AB Tasty application**

Retrieve your **account API Key** on AB Tasty

* Access your **AB Tasty account > Integrations > API key**
* Generate or copy the API key (will be used on the method for UDC)\
  **On your end - Using the API key, send audience data to UDC**\
  \
  Following the [UDC documentation](https://app.gitbook.com/s/dG0EHdNiO40UVA7Bz9mR/data-apis/universal-data-connector), choose how & what audience you want to send to AB Tasty\
  \
  **Curl example** (with the correct CSV file format & your API Key)

```markup
curl --location 'https://api-data-connector.abtasty.com/segments/partner_name' \
--header 'X-API-KEY: Your AB TASTY API KEY' \
--header 'Content-Type: text/csv' \
--data 'visitor_id;value;segment;expiration
my_visitor_id;my_value;my_fake_segment;'
```

**Example CSV file content**

```
visitor_id;value;segment;expiration
19102009415591439;SEGMENT_1_VALUE_1;SEGMENT_1;1609136172230
j73xvgwb5yz9re9f;SEGMENT_1_VALUE_2;SEGMENT_1;1609136172230
19051217151193693;SEGMENT_2_VALUE_1;SEGMENT_2;1609136172230
```

{% hint style="success" %}
**Visitor reconciliation**

When a visitor lands on your website and the AB Tasty tag is allowed to execute, our connector will search for the configured `visitor_id` storage method and check the corresponding data on the UDC.

If a match is found, an event will be sent to our collect endpoint, making the audience available for targeting.
{% endhint %}
{% endstep %}

{% step %}

#### **Create a Segment to Launch a Test**

Once the visitor reconciliation worked, you’ll be able to use the imported data on the AB Tasty Segment Builder.

{% hint style="info" %}
All audiences imported via the Custom Pull Connector will be listed under the **Custom Audiences** section. **AB tasty>Library>Segments>Create Segment.** for more info about segment creation [**visit How to create a Segment page**](https://docs.abtasty.com/web-experimentation-and-personalization/targeting-step/how-to-create-a-segment-who-section)**.**
{% endhint %}

<figure><img src="https://2350286830-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6Yw9IRJ6KbbucQPwZUCZ%2Fuploads%2Fa8ftFhF013XLVA2XYqnf%2FCapture%20d%E2%80%99e%CC%81cran%202025-06-11%20a%CC%80%2014.42.12.png?alt=media&#x26;token=5c82f21b-65a7-4285-8e22-f358a7acb16b" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.abtasty.com/integrations/custom-integrations/import-audience-data-from-any-3rd-party-solution-custom-pull.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.