> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/integrations/custom-integrations/custom-integration-connector-with-a-rd-party-tool-push-data.md).
# Configure your own way to send data to your favorite tools (Custom Push)
The Custom Integration Connector enables you to integrate with any 3rd party tool that is not natively provided by AB Tasty, such as an analytics tool.\\
### Definition
The purpose of a Custom Integration Connector is to share campaign and variation information from AB Tasty to your analytics tool. This way, you will be able to read the results of your campaign directly in the analytics tool you chose.
### How to configure a new Custom integration push data use case
{% embed url="" %}
In the AB Tasty application left navigation, click on [Integration Hub](/integrations/integrations-general-information.md).
Then, on the section "Push", on hover on the card "**Want to create a Push connector?**", click on "**Create Push connector**".
It opens the following screen:
1\. Give a name to your connector - for example the name of your third-party tool
2\. Declare your javaScript code
To add a new Custom Integration push data use case, you need to write JavaScript code that is executed by the ABTasty tag every time a visitor is exposed to a variation.\
**Writing this code requires basic knowledge of JavaScript and requires knowing which API is provided by the analytics service you want to integrate.**\
This code is linked to some built-in variables that will be replaced by the AB Tasty tag at runtime. These variables include:
* {{campaignId}}: the ID of the campaign
* {{campaignName}}: the name of the campaign
* {{variationId}}: the ID of the variation (or 0 for the Original version)
* {{variationName}}: the name of the variation
If a visitor is exposed to two campaigns on the same page, the code will be executed twice.For example, let’s say you write this code in your Custom Integration:\\
```
console.log('Custom Integration code\n')
console.log('Campaign Name : %s\n', {{campaignName}})
console.log('Campaign Id : %s\n', {{campaignId}})
console.log('Variation Name : %s\n', {{variationName}})
console.log('Variation Id : %s\n', {{variationId}})
```
If you browse the page with two active campaigns using this integration, this is what you will see in your developer console:
**After saving your Custom Integration Connector, it will be displayed in the list of available Integrations on the *****Web Analytics page***** of the Settings as well as in the Advanced *****options step***** of the campaign creation flow.**
**Good to know 💡**\
If you modify the code or delete a Custom Integration Connector, the changes will apply to all campaigns on which the Integration is active, including campaigns currently using it. If you want your changes to apply immediately, refresh your tag after editing or deleting a Custom Integration.
### Example
Here is an example of custom integration with a fictional service called “Action360 Analytic”:
\
Your custom integration will now be displayed in the list of available integrations:
\
It will also be displayed in the list of available Integrations in the *Advanced options step* of the campaign creation flow:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.abtasty.com/integrations/custom-integrations/custom-integration-connector-with-a-rd-party-tool-push-data.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.