Ctrlk
PlatformsPricingResources
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Send Feature Experimentation Event to Heap

Heap is a Product Analytics company that provides analytics infrastructure and helps its clients focus on discovering insights and taking action, rather than writing tracking code.

The Heap Analytics integration allows you to send the Feature Experimentation (FE&R) campaign data to your Heap Analytics project.

Visitor ID requirement

To make this integration work, you must use a valid user ID from Heap when calling the Decision API.

To do:

• Create the connector before sending hits • Ensure Heap has a known user_id to associate events with the correct profile • Retrieve Heap’s existing user ID using: heap.getUserId() • It is strongly recommended to use Heap’s auto-generated ID • If you prefer to use your own custom ID, register it with: heap.identify("your_custom_user_id") • Call the Decision API with this same visitor ID; otherwise, the hit won’t be sent to the third party

How to set up the integration

1

On Heap dashboard

  1. Go to your Heap dashboard and click: Account > Manage > Projects

  2. A right-side panel lists all linked environments (for example, production and development).

  3. Copy the Environment ID of the environment you want to connect to AB Tasty.

2

On AB Tasty

  1. Open the Integration Hub under the Feature Experimentation Tab.

  2. Select Heap > Create

  3. Fill in the required details:

    • Instance name – a descriptive label for the integration.

    • App ID – paste the Heap environment ID you copied earlier.

  4. Create the connector

3

Visitor ID Requirement

  1. The connector must be created before sending hits.

  2. Heap requires a known user_id to associate events with the correct user profile.

  3. Retrieve the existing user ID via:

    heap.getUserId()

  4. It’s strongly recommended to use Heap’s own generated ID. If you choose to create your own, register it using:

    heap.identify("your_custom_user_id")

    This ensures Heap can match the user’s identity across events.

Decision API must be called with this visitorID, otherwise, the hit won’t be sent into the third party

Troubleshooting

You can verify the hit in real time in Heap by navigating to Data → Live data feed, where your flagship The event should appear alongside other user actions.

PreviousHeap - Feature Experimentation IntegrationNextImport Heap Audience to Feature Experimentation

Last updated

Was this helpful?