Tracking tag | Developer Center

Parameters

This page describes the parameters available for the tracking tag.

Global snippet
Event snippet
Notes on parameter setting
Deduplication of event tracking

Global snippet

init process

Parameter Name		Required*	Type	Default Value	Settings	Comments
type		Yes	string	-	Enter "init". *Fixed value
tagId		Yes	string	-	Tag ID.
config			-	-	Store each of the following parameters:
	email		string	None	Email address.
	phoneNumber		string	None	Phone number. Enter in the format with the country code.
	useCookie		boolean	false	Specify true if you want to store the identifier in a cookie, and specify false if not.	If you omit the item, it defaults to false.
	useLocalStorage		boolean	false	Specify true if you want to store the identifier in local storage, and specify false if not.	If you omit the item, it defaults to false.
	cookieDomain		string	None	Domain for storing cookies.
	autoLinkDomains		string[]	None	This is the domain for using the cross-domain tracking feature (tracking across different domains).

Page view process

Parameter Name		Required*	Type	Default Value	Settings	Comments
type		Yes	string	-	Enter "event". *Fixed value
eventType		Yes	string	-	Enter "page_view". *Fixed value
tagId		Yes	string	-	Tag ID.
config			-	-	Store each of the following parameters:
	label		string	None	This is a custom label set as a filter when creating an audience list.
	isTest		boolean	false	Flag indicating whether it is a test. true: Exclude from tracking as a test. false: Include in tracking.

Event snippet

Parameter Name		Required*	Type	Default Value	Settings	Comments
type		Yes	string	-	Enter "event". *Fixed value
eventType		Yes	string	-	Event type. For details, refer to "Trackable events"
tagId		Yes	string	-	Tag ID.
config			-	-	Store each of the following parameters:
	snippetId		string	None	ID of the event snippet generated in the conversion setting.
	transactionId		string	None	A unique ID for duplicate detection in conversion tracking. You can set it freely according to the advertiser's needs (Example: payment numbers). For deduplication, refer to "Deduplication of event tracking."
	value		number	None	The monetary value of the event.	If you specify a value, entering the currency is required.
	currency		string	None	The currency unit for the item associated with the event. You can specify only "JPY."	Enter in the 3-character ISO 4217 format.
	label		string	None	This is a custom label set as a filter when creating an audience list.
	isTest		boolean	false	Flag indicating whether it is a test. true: Exclude from tracking as a test. false: Include in tracking.
	items		Item[]	-	You can specify up to 10 in array format.	Example settings: items: [ { itemId: 'i1', categoryId: '', price: '', quantity: '' }, { itemId: 'i2', categoryId: '', price: '', quantity: '' } ]
	itemId		string	None	Item ID.	・Up to 100 characters ・You can use alphanumeric characters (uppercase/lowercase), hyphens (-), and underscores (_)
	categoryId		string	None	Item category ID.	・Up to 50 characters ・You can use alphanumeric characters (uppercase/lowercase), hyphens (-), and underscores (_)
	price		number	None	Item price.	・Up to 10-digit numbers ・You can't set decimal numbers.
	quantity		number	None	Item quantity.	・An integer up to 10 digits ・You can't set decimal numbers.

Notes on parameter setting

If the value entered for a required field is invalid, the request won't be sent to LY Corporation.
If the value entered for an optional field is invalid, a default value will be sent. If there is no default value, that field won't be sent.
Invalid values will appear as an error in the console.

Deduplication of conversion tracking

The tracking tag uses the following values as unique keys to eliminate duplicate tracking:

Account ID
transaction_id

The validity duration for the unique keys is 7 days. Even if you use the same "Account ID" and "transaction_id," they are not subject to deduplication after 7 days from when the conversion is counted.
If the same "Account ID" and "transaction_id" are sent from both the conversion API and the Tracking tag, they are considered duplicates.
Because "transaction_id" is an optional field, if it is not set, "Account ID" and "event_time" are used as unique keys for deduplication. In this case, conversions with the same "Account ID" and "event_time" are deduplicated during the tracking duration of the conversion settings.

Examples of deduplication

*The value of "event_time" is actually in UNIX time. For explanation purposes, it is shown in the "yyyymmdd" format.

Example 1

Account ID	transaction_id	event_time
12345	0000112345	20250411
12345	0000112345	20250412

→Deduplicated because account ID and transaction_id are the same and the interval between event_time values is within 7 days.

Example 2

Account ID	transaction_id	event_time
12345	0000112345	20250411
12345	0000112345	20250420

→Not deduplicated because, although "Account ID" and "transaction_id" are the same, the interval between "event_time" values is 8 days or more.

Example 3

Account ID	transaction_id	event_time
12345	None	20250411
12345	None	20250412

→Not deduplicated because "transaction_id" is not set, and even though the interval between "event_time" values is within 7 days, "Account ID" and "event_time" don't match.

Developer Center

Related sites: