getConsentFromVendor

getConsentFromVendor Function

The getConsentFromVendor function returns the current consent state for a specific vendor within the context of the currently processed tracking package.

⚠️ This function does not reflect the full, persisted user consent. It only reflects the temporary consent information associated with the tracking event currently being handled.

---

Purpose

Use this function to:

• Determine whether a specific vendor (tool) currently has consent in the active tracking package

• Dynamically adapt tracking logic based on temporary consent states

• React to consent changes in real-time (e.g., allow or block data persistence)

---

Function Definition

Property	Description
Function Name	this.getConsentFromVendor
Type	function
Available In	Server-Side Variables
Returns	boolean or string ("ncm")

---

Return Values

Value	Meaning
true	Consent granted for the vendor
false	Consent declined
"ncm"	Tool is running in Essential Mode

---

Parameters

Parameter	Description	Type	Required	Example
vendor-id	Internal ID of the vendor/tool (as used in JTM)	string		"googleanalytics"

---

Example Usage

async function() {
  let x = this.getConsentFromVendor("googleanalytics");
  return x;
}

This example checks the current consent status for the vendor googleanalytics and returns true, false, or "ncm" based on the tracking package.

---

Use Cases

• Execute vendor-specific logic only if consent is granted

• Avoid writing cookies or data when consent is "false" or "ncm"

• Enrich server-side data conditionally based on vendor consent

---

Important Notes

• This function references the current tracking context, not the user's complete or historical consent status.

• If you need to understand consent transitions, refer to this.package.consent.

• Vendor IDs must match the internal names used in your JENTIS Tag Manager configuration.

---

Summary

this.getConsentFromVendor is a quick and context-aware way to determine if consent is currently given for a specific vendor in the active tracking event. It supports dynamic decision-making in server-side variables and ensures that vendor-specific logic only runs under compliant conditions.