Preset Parameters in Zync

For a custom configuration, there could be additional parameters within the tag URL, the expected values of which relate to the data being collected from the website. However, if there are supplied parameters for which the parsing of a relevant value is not possible, the parameter and accompanying placeholder macro can be removed from the tag URL. If there are no additional parameters supplied within this specific tag bundle, then the marketer has not expressed a wish to collect additional data, therefore no further configuration is required.

When implementing a tag with standard (or custom) parameters, the marketer's tag management team should parse the expected variable value (as specified by the parameter's placeholder macro), from the marketer's CRM platform or TMS upon HTML document render, completely replacing the parameter's placeholder macro.

For example,

The supplied parameter & placeholder macro: &CustID={customerId}
Upon HTML render: &CustID=970033140789446465

In some cases, there may be more than one value to pass in for a parameter. In this case, it is acceptable to use a string delimiter, not including ampersand(&), to separate the values such as a comma or pipe delimiter.

For example,

The supplied parameter & placeholder macro: &productID={productID}
Upon HTML render: &productID=AC123,BD456,EF789

The following are examples of additional parameters that may be included in your tag. Please consult with your Zeta contact for specifically requested parameters when applicable.

Standard Parameters
Parameter	Description
Cache_buster	randomly generated alphanumeric string unique to each render of the tag
CustID	the unique customer ID as generated in the marketer's CRM database, expressed as an alphanumeric string. Must not contain any PII data such as the customer's plain text email address.
OrderID	The unique identifier or primary key of the conversion/transaction/lead event carried out, expressed as an alphanumeric string.
OrderAmount	The shopping cart total of the conversion/transaction event carried out, for example a booking or order, expressed in the format integer-period-decimal.
OrderQty	The quantity of items within the shopping cart at the time of the conversion/transaction event carried out, expressed as an integer.
Currency	The 3 digit ISO 4217 currency code.
StoreID	The identifier of a store, vendor, merchant or dealer, expressed as an alphanumeric string.
CategoryID	The category identifier, expressed as an alphanumeric string.
ProductID	The unique product identifier or SKU, expressed as an alphanumeric string.
cartID	The shopping cart identifier for the purpose of cart recovery, expressed as an alphanumeric string.
cartTotal	The shopping cart total prior to any conversion/transaction event carried out, for example on the shopping cart page, expressed in the format integer-period-decimal.
cartQty	The quantity of items within the shopping cart prior to any conversion/transaction event carried out, for example on the shopping cart page, expressed as an integer.
promoCode	the promotional discount code entered by the customer into the shopping cart, expressed as an alphanumeric string.
e_md5	The MD5 (message-digest algorithm) 128-bit hash value of a customer's email address, this must not be used for any customer geographically within a GDPR region.
e_sha	The SHA-2 (Secure Hash Algorithm 2) 256-bit hash value of a customer's email address, this must not be used for any customer geographically within a GDPR region.
gdpr=${GDPR}	The GDPR status parameter and macro, to be parsed by the marketer's CMP, where a value of 1 indicates that GDPR applies to this customer, and the value of 0 indicates that it does not.
gdpr_consent=${GDPR_CONSENT_469}	The GDPR TC consent placeholder and macro, to be parsed by the marketer's CMP, with the global vendor list identifier (GVL ID) of 469 for Zeta Global

Custom Parameters

Zeta Global provides for up to 20 custom parameters, e.g., custom1, custom2, custom3, etc. which can accommodate any alphanumeric string value. Please work with your Zeta contact in mapping out these additional custom data points.

For Additional Developer Guides please refer to the Zeta API Developer Guide.