# Trigger campaigns from customer or decisioning data

> Connect your CDP or decisioning platform to the Visitor API and target triggered campaigns on the data it sends.

How-to guide · Personalisation & AI · Last updated 25 September 2026

URL: https://personalisationhub.com/support-centre/personalisation-and-ai/trigger-campaigns-from-customer-or-decisioning-data/

To trigger campaigns from customer or decisioning data, your data platform sends a visitor's attributes to the platform's Visitor API, and each campaign's targeting rules decide which campaign plays. This article covers the decisions to make, the API credential, the targeting rule, and a test you can run from a phone before any integration work.

## Before you begin

- An HQ Admin account with the Admin role.
- A customer data platform (CDP) or decisioning vendor that provides an API to retrieve data for a store visitor.
- A test store with at least 1 connected display — see [Register a new display or device](https://personalisationhub.com/support-centre/digital-signage/register-a-new-display-or-device/).

## Decide the identifier and the data

1. Choose the identifier your data platform's API needs to look up a visitor. Most brands use a hashed email address or a hashed mobile number.
2. Confirm the platform can capture that identifier in store. Store queueing, QR Control and appointments each capture visitor details as a visitor checks in.
3. List the insights you want in store, for example product holdings, purchase history or purchase intent. The platform uses them to personalise campaigns on displays and shows them to staff when they pick a visitor up from the queue.

## Create the API credential

1. In the left navigation, select **Platform Admin**.
2. Under **Enabled Features**, select **API Authentication**.
3. Select **Add New Platform**, name it (for example `Visitor API`) and save the secret somewhere secure — see [Create API authentication credentials for an integration](https://personalisationhub.com/support-centre/integrations-and-3rd-party-guides/create-api-authentication-credentials-for-an-integration/).

## Add a targeting rule to the campaign

1. In the left navigation, select **Campaigns**, then select the campaign's name.
2. Select the **Targeting** tab.
3. Select **Add New "AND" Condition**.
4. In the first drop-down, choose **Visitor / Customer Data**.
5. In the second drop-down, choose the field, for example **Gender** or a product holding.
6. Choose the operator (for example **equal**) and enter the value the data feed sends, for example `male`.
7. If the campaign must interrupt whatever is playing, set **Override current campaign** to on.
8. Select **Save Changes**.

## Send a test feed from a phone

You can test without any integration by posting a sample feed from a REST client app on a phone.

1. Install a REST API client app on a phone. If your instance restricts access by IP address, add the phone's IP first — see [Restrict platform access by IP address](https://personalisationhub.com/support-centre/platform-installation/step-7-restrict-platform-access-by-ip-address/).
2. Create a `POST` request to `https://<your-platform-domain>/location-api/visitor/feed`.
3. Add the headers `Content-Type: application/json` and `apikey: <the secret you created>`.
4. Set the body to raw JSON using the fields in [Use customer and decisioning data to personalise the store visit](https://personalisationhub.com/support-centre/personalisation-and-ai/use-customer-and-decisioning-data-to-personalise-the-store-visit/), with `uuid` set to the store's **Store Code**, `uuid_type` set to `STORE_CODE`, and `display_id` set to the display's ID from its detail page URL.
5. Send the request.

> **Note:** To stop the campaign, send the same request again with the data values blank.

## Verify it worked

The display named in `display_id` starts playing the campaign whose rule matches the data you sent. Omit `display_id` and every display in the store plays it.

## Connect your data platform

Once the test works, your data platform posts the same feed whenever a visitor is identified. Email [support@personalisationhub.com](mailto:support@personalisationhub.com) if you want help connecting your customer or decisioning data to the platform.

## Next step

[Connect your mobile app or third-party system to the Visitor API](https://personalisationhub.com/support-centre/personalisation-and-ai/connect-your-mobile-app-or-third-party-system-to-the-visitor-api/)

## Related

- [Use customer and decisioning data to personalise the store visit](https://personalisationhub.com/support-centre/personalisation-and-ai/use-customer-and-decisioning-data-to-personalise-the-store-visit/)
- [What are triggered campaigns?](https://personalisationhub.com/support-centre/personalisation-and-ai/what-are-triggered-campaigns/)
- [Localise campaigns by visitors' reason for visit](https://personalisationhub.com/support-centre/launching-campaigns/localise-campaigns-by-visitors-reason-for-visit/)
- [View a visitor's recent interactions and profile data](https://personalisationhub.com/support-centre/queue-management/view-a-visitor-s-recent-interactions-and-profile-data/)