> For the complete documentation index, see [llms.txt](https://help.konnektive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.konnektive.com/konnektive-crm/admin-setup/plugins/fraud-services/kount-enterprise.md).

# Kount Enterprise

Konnektive clients can enable the original Kount plugin to utilize Kount’s Enterprise account tier.

After a Kount Enterprise account is generated (Ask Konnektive Rep for application details), you will receive a login to Kount.

The Kount UI provides full reporting on all transactions and rules triggered. Rules can be created to your own discretion and will be used across all Konnektive campaigns where Kount is enabled.\
\
\
To add Kount Enterprise to your Konnektive instance, navigate to Admin → Plugins → Fraud Services to find the Kount plugin.

{% hint style="warning" %}
If you would like to use Kount through Konnektive’s Fraud Manager please follow this [link](/konnektive-crm/admin-setup/plugins/fraud-services/fraud-manager.md).
{% endhint %}

<figure><img src="/files/YOH4DMKB3T3eAL5pA9C0" alt=""><figcaption></figcaption></figure>

\
Enter in the merchantId and ApiKey, acquired from Kount.

<figure><img src="/files/NBMTpD3x402a53QLBKbG" alt=""><figcaption></figcaption></figure>

**UseTestingServer** = sends transactions to Kount’s testing server

**Campaign4Source** = sends the Konnektive campaignId as the SITE parameter to Kount.

{% hint style="info" %}
Site IDs can be used to logically organize or segregate data by Site. Site IDs must defined manually in the Kount backend before they can be used and they must match exactly for the transactions to be screened by Kount\
\
(SITE = website identifier of where the order originated) i.e. “KV-\[campaignID]”
{% endhint %}

<figure><img src="/files/GaNNAQqY76efsYhSIEzZ" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
**Note: For affiliates sending the amountPaid value, check the option for “Fire Pixels on QA Approval,” due to screened orders going to “PENDING” status.**
{% endhint %}

Once the plugin is added, navigate to CRM → Campaigns and edit your campaign. Inside the “Other Options” section of the campaigns General Details you will enable the “Screen with Kount?” option.

<figure><img src="/files/LFFJf0Z3eElJ9pB6PVQh" alt=""><figcaption></figcaption></figure>

\
After this is enabled please BE SURE to place the [Data Device Pixel](/konnektive-crm/admin-setup/plugins/fraud-services/device-data-collector-pixel-ddc-pixel.md) onto your landing pages so Kount can receive more data for screening.

***

Orders placed into Review must be manually evaluated in Konnektive or Kount. If evaluated in Konnektive then Kount is automatically updated. If you prefer to evaluate in Kount then you need to enable notifications on your Kount account.

* Login to Kount
* Go to Fraud Control > Websites
* Click the cog icon to the right of the website and select Edit
* Enter Merchant ENS URL = <https://api.konnektive.com/kount/>


---

# 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://help.konnektive.com/konnektive-crm/admin-setup/plugins/fraud-services/kount-enterprise.md?ask=<question>&goal=<endgoal>
```

`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.
