This article will guide you on how to send audience data to Krux using their Mobile HTTP API via an AudienceStream Webhook Connector.
Before you begin, this article assumes your familiarity with the Webhook action, "Send Custom Request".
This solution combines the following components from iQ and Customer Data Hub:
Add the Krux Control tag from the iQ Tag Management Tag Marketplace. Configure the tag with the Krux Configuration ID provided to you by Krux.
In order to match the user you are sending via the Webhook connector to a Krux user, you need to extract the Krux User ID from the Krux object populated by the Krux Control Tag. The Krux object's naming convention will vary per client. The code to extract the user ID will be similar to
Krux.ns.CLIENT('get', 'user'), where CLIENT is your specific Krux client name. You can either ask your Krux representative for the naming convention of this object or examine the object in Chrome DevTools Console by typing
Krux.ns and examining the resulting object.
Once you obtain your Krux client name, follow these steps to save the Krux User ID to a cookie:
Set the conditions for this extension to only set the variable if the utag_main_krux_id cookie has not yet been set.
Set the conditions to only store this cookie if the krux_id variable is populated and keep the first value set.
Create a Visitor-scoped String Attribute named "Krux ID". Populate this attribute from the utag_main_krux_id cookie.
This section will define the parameters needed to create the Krux connector using the Webhook Send Custom Request Action.
Vendor documentation: Krux Mobile HTTP API
|Mapped Attribute||Krux Parameter||Description|
|<Custom Value>||_kpid||Publisher UUID (provided by Krux)|
|<Custom Value>||_kcp_d||Domain (provided by Krux)|
|<Custom Value>||_kcp_s||Site (provided by Krux)|
|Krux ID||_kuid||Krux ID Visitor Attribute|
|<Custom Value>||_kua_<krux_user attribute_name>||
Custom user attribute set in Krux