{
    "kind": "term",
    "name": "Tealium for Pharma",
    "count": 7,
    "items": [

    
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/server-side-connectors/pulsepoint-npi-list-connector/",
            "title": "PulsePoint NPI List Connector Setup Guide",
            "body": "<p>This integration connects you to Life by PulsePoint. Life is a DSP focused on healthcare advertising and lets you plan, activate, and analyze digital healthcare ad campaigns aimed at HCPs across endemic and non-endemic publishers. Our PulsePoint NPI List Connector provides you direct access and complete control to Life’s NPI List, creating a seamless integration to our <a href=\"/industries/tealium-for-pharma/\">Tealium for Pharma CDP</a>.</p>\n<h2 id=\"api-information\">API Information</h2>\n<p>This connector uses the following vendor API:</p>\n<ul>\n<li>API Name: PulsePoint API</li>\n<li>API Version: v1</li>\n<li>API Endpoint: <code>https://lifeapi.pulsepoint.com/RestApi/v1/npi/npi-list/</code></li>\n</ul>\n<h2 id=\"connector-actions\">Connector Actions</h2>\n<table>\n<thead>\n<tr>\n<th>Action Name</th>\n<th style=\"text-align:center\">AudienceStream</th>\n<th style=\"text-align:center\">EventStream</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Create NPI List</td>\n<td style=\"text-align:center\">✓</td>\n<td style=\"text-align:center\">✗</td>\n</tr>\n<tr>\n<td>Add NPIs to a List</td>\n<td style=\"text-align:center\">✓</td>\n<td style=\"text-align:center\">✗</td>\n</tr>\n<tr>\n<td>Delete NPIs from a List</td>\n<td style=\"text-align:center\">✓</td>\n<td style=\"text-align:center\">✗</td>\n</tr>\n</tbody>\n</table>\n<h2 id=\"configure-settings\">Configure Settings</h2>\n<p>Navigate to the Connector Marketplace and add a new  connector. For general instructions on how to add a connector, see <a href=\"/server-side/connectors/about/\">About Connectors</a>.</p>\n<p>After adding the connector, configure the following settings:</p>\n<ul>\n<li><strong>Client ID</strong><br>\n(Required) ID for the account in PulsePoint.</li>\n<li><strong>Client Secret</strong><br>\n(Required) Secret for the account in PulsePoint, provided by a PulsePoint representative.</li>\n<li><strong>Username</strong><br>\n(Required) PulsePoint Life username for the client.</li>\n<li><strong>Password</strong><br>\n(Required) PulsePoint Life password for the client’s username.</li>\n<li><strong>Account ID</strong><br>\n(Required) Account ID associated with the client and that holds all the NPI lists.</li>\n</ul>\n<h2 id=\"actions\">Actions</h2>\n<p>Enter a name for the action and select the action type from the drop-down menu.</p>\n<p>The following section describes how to set up parameters and options for each action.</p>\n<h3 id=\"create-npi-list\">Create NPI List</h3>\n<h4 id=\"parameters\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Name</td>\n<td>(Required) Name of the advertiser that is linked to the NPI list.</td>\n</tr>\n<tr>\n<td>Advertisers</td>\n<td>(Required) NPI list name.</td>\n</tr>\n<tr>\n<td>NPI</td>\n<td>(Required) List of NPIs to include in the NPI list.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"add-npis-to-a-list\">Add NPIs to a List</h3>\n<h4 id=\"parameters-1\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>List ID</td>\n<td>(Required) List number that the requested NPIs belong to.</td>\n</tr>\n<tr>\n<td>NPI</td>\n<td>(Required) List of NPIs to include in the NPI list.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"delete-npis-from-a-list\">Delete NPIs from a List</h3>\n<h4 id=\"parameters-2\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>List ID</td>\n<td>(Required) List number that the requested NPIs belong to.</td>\n</tr>\n<tr>\n<td>NPI</td>\n<td>(Required) List of NPIs to delete in the NPI list.</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    , 
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/client-side-tags/pulsepoint-hcp365-tag/",
            "title": "PulsePoint HCP365 Pixel Tag Setup Guide",
            "body": "<p>HCP365, the first self-serve product under the Signal platform, uncovers who, how, and when your HCP audience organically engages with branded digital touch points at the NPI-level. The HCP365 Pixel will send page-level information into your PulsePoint system.</p>\n<h2 id=\"tag-tips\">Tag Tips</h2>\n<ul>\n<li>Use mappings to override Standard parameters.</li>\n</ul>\n<h2 id=\"tag-configuration\">Tag Configuration</h2>\n<p>Go to the tag marketplace to add a new tag. For more information about how to add a tag, see <a href=\"/iq-tag-management/tags/manage/\">Manage tags</a>.</p>\n<p>When adding the tag, configure the following settings:</p>\n<ul>\n<li><strong>PulsePoint Container Pixel</strong>: PulsePoint container pixel that is unique to each client</li>\n<li><strong>Token</strong>: PulsePoint internal identifier for a brand (for example, Merck advertiser has multiple brands so multiple tokens)</li>\n</ul>\n<h2 id=\"load-rules\">Load Rules</h2>\n<p>Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the <a href=\"/iq-tag-management/load-rules/about/\">Load Rules</a> documentation.</p>\n<h2 id=\"data-mappings\">Data Mappings</h2>\n<p>Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see <a href=\"/iq-tag-management/data-mappings/manage/\">data mappings</a>.</p>\n<p>The available categories are:</p>\n<h3 id=\"standard\">Standard</h3>\n<table>\n<thead>\n<tr>\n<th>Variable</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>PulsePoint container pixel (<code>p</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Token (<code>token</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Base Url (<code>base_url</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>CCPA Opt-Out (<code>us_privacy</code>) (Required)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>URL of the page the tag was fired (<code>url</code>) (Required)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Referrer of the page (<code>rr</code>) (Required)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Additional parameters for passing additional information to the pixel (<code>param1</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Additional parameters for passing additional information to the pixel (<code>param2</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Additional parameters for passing additional information to the pixel (<code>param3</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Additional parameters for passing additional information to the pixel (<code>param4</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Additional parameters for passing additional information to the pixel (<code>param5</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Form details if tag is fired on form submission (<code>frmtext</code>)</td>\n<td><code>String</code></td>\n</tr>\n<tr>\n<td>Link text of the link being clicked or document name of the document being downloaded (<code>clktext</code>)</td>\n<td><code>String</code></td>\n</tr>\n</tbody>\n</table>\n"
        }  

    , 
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/server-side-connectors/dmd-connector/",
            "title": "DMD Connector Setup Guide",
            "body": "<p>DMD, an IQVIA Business, is the only provider of healthcare data that is first-party sourced, 100% opted-in, and privacy and regulatory compliant. This DMD Email Connector allows users to send campaign emails to HCP/HCOs based off of CDP actions.</p>\n<h2 id=\"batch-limits\">Batch Limits</h2>\n<p>This connector uses batched requests to support high-volume data transfers to the vendor. For more information, see <a href=\"/server-side/connectors/batched-actions/\">Batched Actions</a>. Requests are queued until one of the following thresholds is met or the profile is published:</p>\n<ul>\n<li>Max number of requests: 100</li>\n<li>Max time since oldest request: 15 minutes</li>\n<li>Max size of requests: 1 MB</li>\n</ul>\n<h2 id=\"connector-actions\">Connector Actions</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Action Name</strong></th>\n<th><strong>AudienceStream</strong></th>\n<th><strong>EventStream</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Trigger Custom Event</td>\n<td>✓</td>\n<td>✗</td>\n</tr>\n<tr>\n<td>Trigger Email Message</td>\n<td>✓</td>\n<td>✗</td>\n</tr>\n</tbody>\n</table>\n<h2 id=\"configure-settings\">Configure Settings</h2>\n<p>Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the <a href=\"/server-side/connectors/manage/\">About Connectors</a> article.</p>\n<p>After adding the connector, configure the following settings:</p>\n<ul>\n<li><strong>API Username</strong><br>\nUsername for the Oracle Responsys account.</li>\n<li><strong>API Password</strong><br>\nPassword for the specified user.</li>\n<li><strong>Login Endpoint</strong><br>\nSelect the login endpoint for the authentication.</li>\n</ul>\n<p>Click <strong>Done</strong> when you are finished configuring the connector.</p>\n<h2 id=\"action-settings--parameters-and-options\">Action Settings — Parameters and Options</h2>\n<p>Click <strong>Continue</strong> to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu.</p>\n<p>The following section describes how to set up parameters and options for each action.</p>\n<h3 id=\"action--trigger-custom-event\">Action — Trigger Custom Event</h3>\n<h4 id=\"parameters\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Event Name</td>\n<td>(Required) Custom Event Name.</td>\n</tr>\n<tr>\n<td>Folder Name</td>\n<td>(Required) Folder Name.</td>\n</tr>\n<tr>\n<td>Object Name</td>\n<td>(Required) Profile List Name.</td>\n</tr>\n<tr>\n<td>Email Format</td>\n<td>(Required) Email Format, either <code>TEXT_FORMAT</code> or <code>HTML_FORMAT</code>.</td>\n</tr>\n<tr>\n<td>Customer ID</td>\n<td>Customer ID.</td>\n</tr>\n<tr>\n<td>Mobile Number</td>\n<td>Mobile number, can be <code>NULL</code>.</td>\n</tr>\n<tr>\n<td>Recipient ID</td>\n<td>Recipient&rsquo;s RIID, value can be <code>NULL</code>.</td>\n</tr>\n<tr>\n<td>Email Address</td>\n<td>Recipient&rsquo;s plain text email address.</td>\n</tr>\n<tr>\n<td>Email Address (already SHA256 hashed)</td>\n<td>Recipient&rsquo;s SHA256-hashed Email address.</td>\n</tr>\n<tr>\n<td>Email Address (apply SHA256 hash)</td>\n<td>Recipient&rsquo;s email address, which will receive a SHA256 hash.</td>\n</tr>\n<tr>\n<td>Email Address (already MD5 hashed)</td>\n<td>Recipient&rsquo;s MD5-hashed Email address.</td>\n</tr>\n<tr>\n<td>Email Address (apply MD5 hash)</td>\n<td>Recipient&rsquo;s email address, which will receive an MD5 hash.</td>\n</tr>\n<tr>\n<td>Number Data Mapping</td>\n<td></td>\n</tr>\n<tr>\n<td>Date Data Mapping</td>\n<td></td>\n</tr>\n<tr>\n<td>String Data Mapping</td>\n<td></td>\n</tr>\n<tr>\n<td>Optional Data</td>\n<td>Optional data containing name-value pairs.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"action--trigger-email-message\">Action — Trigger Email Message</h3>\n<h4 id=\"parameters-1\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Campaign Name</td>\n<td>(Required) Name of the Campaign.</td>\n</tr>\n<tr>\n<td>Email Format</td>\n<td>(Required) Email Format.</td>\n</tr>\n<tr>\n<td>Customer ID</td>\n<td>Customer ID</td>\n</tr>\n<tr>\n<td>Mobile Number</td>\n<td>Mobile number,  can be <code>NULL</code>.</td>\n</tr>\n<tr>\n<td>Recipient ID</td>\n<td>Recipient&rsquo;s RIID, value can be <code>NULL</code>.</td>\n</tr>\n<tr>\n<td>Email Address</td>\n<td>Recipient&rsquo;s plain text email address.</td>\n</tr>\n<tr>\n<td>Email Address (already SHA256 hashed)</td>\n<td>Recipient&rsquo;s SHA256-hashed Email address.</td>\n</tr>\n<tr>\n<td>Email Address (apply SHA256 hash)</td>\n<td>Recipient&rsquo;s email address, which will receive a SHA256 hash.</td>\n</tr>\n<tr>\n<td>Email Address (already MD5 hashed)</td>\n<td>Recipient&rsquo;s MD5-hashed Email address.</td>\n</tr>\n<tr>\n<td>Email Address (apply MD5 hash)</td>\n<td>Recipient&rsquo;s email address, which will receive an MD5 hash.</td>\n</tr>\n<tr>\n<td>Campaign Folder Name</td>\n<td>(Optional) Campaign Folder Name.</td>\n</tr>\n<tr>\n<td>Object Name</td>\n<td>(Optional) Profile List Name.</td>\n</tr>\n<tr>\n<td>Optional Data</td>\n<td>Optional data containing name-value pairs.</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    , 
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/server-side-connectors/veeva-crm-connector/",
            "title": "Veeva CRM Connector Setup Guide",
            "body": "<h2 id=\"connector-actions\">Connector Actions</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Action Name</strong></th>\n<th><strong>AudienceStream</strong></th>\n<th><strong>EventStream</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Insert into Custom Object</td>\n<td>✓</td>\n<td>✗</td>\n</tr>\n<tr>\n<td>Update Custom Object</td>\n<td>✓</td>\n<td>✗</td>\n</tr>\n</tbody>\n</table>\n<h2 id=\"configure-settings\">Configure Settings</h2>\n<p>Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the <a href=\"/server-side/connectors/manage/\">About Connectors</a> article.</p>\n<p>After adding the connector, configure the following settings:</p>\n<ul>\n<li><strong>Endpoint URL</strong><br>\n(Required) Provide the endpoint URL. Default URL is <code>https://login.salesforce.com/services/oauth2/authorize</code></li>\n<li><strong>Establish</strong> <strong>Connection</strong><br>\nClick <strong>Establish Connection</strong> to connect to your Salesforce account.</li>\n</ul>\n<p>Click <strong>Done</strong> when you are finished configuring the connector.</p>\n<h2 id=\"action-settings--parameters-and-options\">Action Settings — Parameters and Options</h2>\n<p>Click <strong>Continue</strong> to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu.</p>\n<p>The following section describes how to set up parameters and options for each action.</p>\n<h3 id=\"action--insert-into-custom-object\">Action — Insert into Custom Object</h3>\n<h4 id=\"parameters\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Custom Object Name</td>\n<td>Name of custom object.</td>\n</tr>\n<tr>\n<td>Insert Data Map</td>\n<td>Insert data map configured in Salesforce.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"action--update-custom-object\">Action — Update Custom Object</h3>\n<h4 id=\"parameters-1\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Custom Object Name</td>\n<td>Name of custom object.</td>\n</tr>\n<tr>\n<td>Lookup Data Map</td>\n<td>Select attribute to look up custom object by.</td>\n</tr>\n<tr>\n<td>Update Data Map</td>\n<td>Update data map configured in Salesforce.</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    , 
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/client-side-tags/aim-xr-website-tag/",
            "title": "AIM XR Website Tag Setup Guide (formerly DMD)",
            "body": "<p>DMD, an IQVIA Business, is a healthcare identity company dedicated to connecting marketers to key healthcare audiences for impactful engagement. Their Audience Identity Manager Extended Reach (AIM XR) provides identity resolution for Healthcare Professionals (HCPs). This tag will load DMD’s AIM XR library and will scan for a DMD tagged device. Upon identification, <code>AIM.ondetect()</code> will execute whatever is located within the function.</p>\n<h2 id=\"tag-tips\">Tag tips</h2>\n<ul>\n<li>Use mappings to override standard config values.</li>\n</ul>\n<h2 id=\"tag-configuration\">Tag configuration</h2>\n<p>When adding the tag, configure the following settings:</p>\n<ul>\n<li><strong>Version</strong>: Select the version of the tag to use.</li>\n<li><strong>Data Layer Name</strong>: By default, the data layer initiated and referenced by the global site tag is named <code>aimDataLayer</code>. Rename the data layer only if your project requires a separate name.</li>\n<li><strong>API KEY</strong>: The AIM XR API key used in the <code>AIM.init</code> function.</li>\n<li><strong>Trigger Event AIM Signal</strong>: Signal data is being sent to Tealium Collect on server-side.</li>\n<li><strong>Session Information Event</strong>: Request session information (<code>id</code>, <code>timestamp</code>).</li>\n<li><strong>Include POI Identity Type</strong>: Enable this option to include POI identity type. The default value is <code>No</code>.</li>\n<li><strong>Include TST Identity Type</strong>: Enable this option to include TST identity type. The default value is <code>No</code>.</li>\n<li><strong>Include UNK Identity Type</strong>: Enable this option to include UNK identity type. The default value is <code>No</code>.</li>\n<li><strong>Send HCP data to</strong>: Specify the unique identifiers (UIDs) of the tags you want to selectively target for sending High-Value Customer (HCP) data through <code>utag.link</code> (separated by commas). By default, it uses all tags.</li>\n<li><strong>Tag must only fire on the first page view</strong>: By setting the parameter to <code>Yes</code>, <code>utag.link</code> will exclusively activate during the initial page view of the website. If the parameter is set to <code>No</code>, <code>utag.link</code> will fire on all pages.</li>\n</ul>\n<h2 id=\"load-rules\">Load rules</h2>\n<p>Load the tag on all pages or set conditions for when your tag will load. For more information, see <a href=\"/iq-tag-management/load-rules/about/\">About load rules</a>.</p>\n<h2 id=\"data-mappings\">Data mappings</h2>\n<p>Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For more information, see <a href=\"/iq-tag-management/data-mappings/about/\">About data mappings</a>.</p>\n<p>The available categories are:</p>\n<h3 id=\"configuration\">Configuration</h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Variable</th>\n<th style=\"text-align:left\">Type/Values</th>\n<th style=\"text-align:left\">Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><code>apiKey</code></td>\n<td style=\"text-align:left\">String</td>\n<td style=\"text-align:left\">API key.</td>\n</tr>\n<tr>\n<td style=\"text-align:left\"><code>triggerEvent</code></td>\n<td style=\"text-align:left\">Boolean</td>\n<td style=\"text-align:left\">Trigger Event AIM signal.</td>\n</tr>\n<tr>\n<td style=\"text-align:left\"><code>sessionInformation</code></td>\n<td style=\"text-align:left\">Boolean</td>\n<td style=\"text-align:left\">Session information.</td>\n</tr>\n<tr>\n<td style=\"text-align:left\"><code>poiSelected</code></td>\n<td style=\"text-align:left\">Boolean</td>\n<td style=\"text-align:left\">Include POI identity type.</td>\n</tr>\n<tr>\n<td style=\"text-align:left\"><code>tstSelected</code></td>\n<td style=\"text-align:left\">Boolean</td>\n<td style=\"text-align:left\">Include TST identity type.</td>\n</tr>\n<tr>\n<td style=\"text-align:left\"><code>unkSelected</code></td>\n<td style=\"text-align:left\">Boolean</td>\n<td style=\"text-align:left\">Include UNK identity type.</td>\n</tr>\n<tr>\n<td style=\"text-align:left\"><code>selectedTagsToSend</code></td>\n<td style=\"text-align:left\">String</td>\n<td style=\"text-align:left\">Send HCP data to.</td>\n</tr>\n<tr>\n<td style=\"text-align:left\"><code>firstPageOnly</code></td>\n<td style=\"text-align:left\">Boolean</td>\n<td style=\"text-align:left\">Tag must only fire on the first page view.</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    , 
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/server-side-connectors/doceree-connector/",
            "title": "Doceree Connector Setup Guide",
            "body": "<h2 id=\"connector-actions\">Connector Actions</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Action Name</strong></th>\n<th><strong>AudienceStream</strong></th>\n<th><strong>EventStream</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Add User NPI</td>\n<td>✓</td>\n<td>✗</td>\n</tr>\n<tr>\n<td>Remove User NPI</td>\n<td>✓</td>\n<td>✗</td>\n</tr>\n</tbody>\n</table>\n<h2 id=\"configure-settings\">Configure Settings</h2>\n<p>Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see <a href=\"/server-side/connectors/about/\">About Connectors</a>.</p>\n<p>After adding the connector, configure the following settings:</p>\n<ul>\n<li><strong>Username</strong><br>\n(Required) Username for your Doceree account.</li>\n<li><strong>Password</strong><br>\n(Required) Password for your Doceree account.</li>\n<li><strong>Environment</strong><br>\n(Required) Select the environment you are using at Doceree. Use <strong>Production</strong> unless your Tealium and/or Doceree representative tells you to use <strong>Demo</strong>.</li>\n</ul>\n<p>To add an audience list:</p>\n<ol>\n<li>Click <strong>Add Audience List</strong>.</li>\n<li>Enter the Doceree account name associated with the audience.</li>\n<li>Enter the audience name to create.</li>\n<li>Click <strong>Add</strong>.</li>\n</ol>\n<p>Click <strong>Done</strong> when you are finished configuring the connector.</p>\n<h2 id=\"action-settings--parameters-and-options\">Action Settings — Parameters and Options</h2>\n<p>Click <strong>Continue</strong> to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu.</p>\n<p>The following section describes how to set up parameters and options for each action.</p>\n<h3 id=\"action--add-user-npi\">Action — Add User NPI</h3>\n<h4 id=\"batch-limits\">Batch Limits</h4>\n<p>This action uses batched requests to support high-volume data transfers to the vendor. For more information, see <a href=\"/server-side/connectors/batched-actions/\">Batched Actions</a>. Requests are queued until one of the following thresholds is met or the profile is published:</p>\n<ul>\n<li>Max number of requests: 1000</li>\n<li>Max time since oldest request: 10 minutes</li>\n<li>Max size of requests: 1 MB</li>\n</ul>\n<h4 id=\"parameters\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Account</td>\n<td>The Doceree account associated with this audience.</td>\n</tr>\n<tr>\n<td>Audience ID</td>\n<td>The audience that you want to add the user to.</td>\n</tr>\n<tr>\n<td>NPI</td>\n<td>The unique identifier (NPI) for the user.</td>\n</tr>\n</tbody>\n</table>\n<h3 id=\"action--remove-user-npi\">Action — Remove User NPI</h3>\n<h4 id=\"parameters-1\">Parameters</h4>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Account</td>\n<td>The Doceree account associated with this audience.</td>\n</tr>\n<tr>\n<td>Audience ID</td>\n<td>The audience that you want to remove the user from.</td>\n</tr>\n<tr>\n<td>NPI</td>\n<td>The unique identifier (NPI) for the user.</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    , 
        {
            "weight": "0",
            "url": "https://docs-preview.tealium.com/server-side/data-sources/webhooks/pulsepoint-hcp365/",
            "title": "PulsePoint HCP365 incoming webhook setup guide",
            "body": "<p>The PulsePoint HCP365 pixel is used to resolve the identity of a Healthcare Provider (HCP) visiting a pharmaceutical website. The purpose of the PulsePoint HCP 365 data source is to bring in the resolved identity of the HCP along with other data elements related to the HCP.</p>\n<h2 id=\"prerequisites\">Prerequisites</h2>\n<ul>\n<li>PulsePoint HCP365 account</li>\n<li>Tealium for Pharma</li>\n</ul>\n<h2 id=\"how-it-works\">How it works</h2>\n<p>PulsePoint HCP365 offers webhook functionality that can be configured to send outgoing requests to an endpoint that you specify. These requests inform Tealium about activity in your PulsePoint account. When you add the PulsePoint data source within Tealium, a unique endpoint will be generated that you can then use within PulsePoint HCP365 to configure the PulsePoint webhook.</p>\n<h2 id=\"pulsepoint-data-source\">PulsePoint data source</h2>\n<p>To configure the PulsePoint data source, perform the following steps:</p>\n<ol>\n<li>Navigate to <strong>Sources</strong>.</li>\n<li>In the sidebar, select <strong>Sources &gt; Data Sources</strong>.</li>\n<li>Click <strong>+Add Data Source</strong>.</li>\n<li>On the <strong>Select a Platform</strong> screen, select <strong>Pharma</strong> under <strong>Categories</strong>, and then select <strong>PulsePoint HCP365</strong>.</li>\n<li>In the <strong>Name</strong> field under <strong>Summary</strong>, enter a name and click <strong>Continue</strong>.</li>\n<li>Click <strong>Continue</strong>.</li>\n<li>Select the <code>pulsepoint_hcp_identity</code> event specification under the <strong>Pharma</strong> category and click <strong>Continue</strong>: <figure><a class=\"slb\" href=\"/images/server-side/data-sources/webhooks/pulsepoint1.png\"><img src=\"https://docs.tealium.com/images/server-side/data-sources/webhooks/pulsepoint1.png\"\n         alt=\"PulsePoint HCP365 event specifications\"\n         title=\"PulsePoint HCP365 event specifications\"/>\n    </a>\n</figure></li>\n<li>(Optional) To download installation instructions, including the data source key, base code, and event tracking code, click <strong>Download as PDF</strong>.</li>\n<li>Click <strong>Save &amp; Continue</strong>.\nA summary of the data source appears.</li>\n<li>Click <strong>Close</strong>.</li>\n</ol>\n<p>For more information, see <a href=\"/server-side/data-sources/create-data-source/\">Create a data source</a>.</p>\n<p>The PulsePoint data source generates a unique URL to use as the HTTP GET OR POST URL in your PulsePoint configuration. The generated URL uses the following format:</p>\n<pre tabindex=\"0\"><code>https://collect.tealiumiq.com/integration/event/ACCOUNT/PROFILE/DATA_SOURCE_KEY\n</code></pre><p>After you create the PulsePoint HCP365 data source, note the following values: <strong>Tealium Account Name</strong>, <strong>Tealium Profile Name</strong>, and the <strong>Data Source Key</strong>. You will need these when configuring the webhook within PulsePoint HCP365.</p>\n<h2 id=\"pulsepoint-setup\">PulsePoint setup</h2>\n<p>After you configure your data source endpoint, configure the webhook in your PulsePoint account.</p>\n<ol>\n<li>Log in to your PulsePoint HCP365 Application.</li>\n<li>Navigate to <strong>Webhook Support</strong>.</li>\n<li>Select <code>GET</code> or <code>POST</code> as the <strong>Request Method</strong>.</li>\n<li>In the <strong>URL</strong> field, enter the endpoint URL that was generated when creating the data source in Tealium.</li>\n<li>In the <strong>Body</strong> field, the event parameters must be included in each request to connect to your Tealium instance and the specific data source. See the <a href=\"#event-attributes\">Event attributes</a> section for a list of event parameters..</li>\n</ol>\n<h2 id=\"event-attributes\">Event attributes</h2>\n<p>The following parameters must be included in each connection request:</p>\n<ul>\n<li><code>tealium_account</code> - Your <strong>Tealium Account Name</strong>.</li>\n<li><code>tealium_profile</code> - Your <strong>Tealium Profile Name</strong>.</li>\n<li><code>tealium_datasource</code> - Your <strong>Data Source Key</strong>.</li>\n</ul>\n<p>The following attributes are specific to PulsePoint and can be sent through the webhook. Ensure that each attribute includes the <code>pulsepoint_</code> prefix as shown in the table below. Refer to your PulsePoint documentation or contact the PulsePoint Support Team if you need help with the HCP365 data elements.</p>\n<table>\n<thead>\n<tr>\n<th>Event Attribute</th>\n<th>Type</th>\n<th>Definition</th>\n<th>Example</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td><code>pulsepoint_npi</code></td>\n<td>String</td>\n<td>National Provider Identifier (NPI) of the individual.</td>\n<td><code>12345</code></td>\n</tr>\n<tr>\n<td><code>pulsepoint_url</code></td>\n<td>String</td>\n<td>Page URL where an event occurred.</td>\n<td><code>https://www.brandhcp.com/psoriatic-arthritis/3-year-data/</code></td>\n</tr>\n<tr>\n<td><code>pulsepoint_channel</code></td>\n<td>String</td>\n<td>Channel Indicator (<code>1</code> - Site, <code>2</code> - Search).</td>\n<td><code>1</code></td>\n</tr>\n<tr>\n<td><code>pulsepoint_token</code></td>\n<td>String</td>\n<td>Unique identifier for pixel and/or placement.</td>\n<td><code>J7CYWG18ZB3F</code></td>\n</tr>\n<tr>\n<td><code>pulsepoint_param1</code></td>\n<td>String</td>\n<td>Optional parameter that can be used to describe the event.</td>\n<td>key action</td>\n</tr>\n<tr>\n<td><code>pulsepoint_param2</code></td>\n<td>String</td>\n<td>Optional parameter that can be used to describe the event.</td>\n<td>key action</td>\n</tr>\n<tr>\n<td><code>pulsepoint_param3</code></td>\n<td>String</td>\n<td>Optional parameter that can be used to describe the event.</td>\n<td>key action</td>\n</tr>\n<tr>\n<td><code>pulsepoint_param4</code></td>\n<td>String</td>\n<td>Optional parameter that can be used to describe the event.</td>\n<td>key action</td>\n</tr>\n<tr>\n<td><code>pulsepoint_param5</code></td>\n<td>String</td>\n<td>Optional parameter that can be used to describe the event.</td>\n<td>key action</td>\n</tr>\n</tbody>\n</table>\n"
        }  

    ]
}